mcb@lll-tis-gw (Michael C. Berch) (04/22/85)
> From: mfe@leadsv.UUCP (Mark Ellson) > In his article, ucscc!argv (Dan Heller) argues that the appropriate error > message when you try to change directory into a directory for which you don't > have permissions is "Permission denied" instead of "no such file or > directory". In fact, while this may be clearer to the user, it falls in the > same general category as not using "Incorrect password" or "Incorrect > username" for failed logins. You never want to tell a potential intruder or > unauthorized user any information which can be used to infer the existence > or nonexistence of a protected object. Yes, but if you have read & execute permission on the "mystery" directory's parent (which is likely if you are in the position to issue the command "cd foo") you can obviously do a long listing of the parent and see the whole scoop on the mystery directory and its mode, etc. To put an error message here that is at best disingenuous and at worst WRONG, for the mere purpose of stonewalling the enemy is like printing up incorrect street maps of Washington to confuse the Ruskies. Michael C. Berch mcb@lll-tis.ARPA {akgua,allegra,cbosgd,decwrl,dual,ihnp4,sun}!idi!styx!mcb
PALLAS@SU-SCORE.ARPA (Joseph I. Pallas) (04/23/85)
To put an error message here that is at best disingenuous and at
worst WRONG, for the mere purpose of stonewalling the enemy is like
printing up incorrect street maps of Washington to confuse the Ruskies.
You've obviously never been to Washington. It's not necessary to make
the maps wrong to confuse anyone :-)
joe
-------