[prev] [thread] [next] [lurker] [Date index for 2006/05/26]
--imjhCm/Pyz7Rq5F2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 26, 2006 at 05:50:05AM -0700, jrodman@xxxx.xxxxxxxxxx.xxx wrote: > On Fri, May 26, 2006 at 02:04:53PM +0200, H.Merijn Brand wrote: > > On Fri, 26 May 2006 03:35:44 -0700, jrodman@xxxx.xxxxxxxxxx.xxx wrote: > >=20 > > > On Thu, May 25, 2006 at 09:46:46PM +0200, H.Merijn Brand wrote: > > > > On Thu, 25 May 2006 21:37:55 +0200, Juerd <juerd@xxxxxxxxxxx.xx> wr= ote: > > > >=20 > > > > > Chris Devers skribis 2006-05-25 15:28 (-0400): > > > > > > There's a simple solution to this, of course. > > > > > > For all defined single-letter options, handle them appropriatel= y. > > > > > > For all undefined single-letter options, return with help detai= ls. > > > > >=20 > > > > > -? is still dangerous: > > > > >=20 > > > > > touch -- -r > > > > > foo -? > > > >=20 > > > > Your fault, core dumped. > > >=20 > > > Here, let me plant a bomb on our shared computer: > > >=20 > > > touch /tmp/-r > > >=20 > > > It may take a long time to go off, but if it does, I guess that's your > > > fault too? > >=20 > > No it's yours. *YOU* planted the bomb. >=20 > Thanks for connecting the dots. The user gets screwed and it's not > their fault, and they are exposed by this dumb -? pattern. I disagree. If you use 'rm', you ought to be aware of the '-r' option. If you've=20 choosen to use a shell that expands '-?' for you, and you choose to use '-?' unquoted, and get bitten, well, boohoo. I don't find that hateful. Abigail --imjhCm/Pyz7Rq5F2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFEd1S8BOh7Ggo6rasRAoV6AJ92Hzo3ERwZ3ZxHCmLqJE2ocHDanACeM4fK 8Ji1lGjKeu8t3wmslkQRpbg= =pLxK -----END PGP SIGNATURE----- --imjhCm/Pyz7Rq5F2--
Generated at 09:00 on 29 May 2006 by mariachi 0.52