Re: LYNX-DEV X-URL header field

[Larry W. Virden, x2487]

Foteos Macrides <address@hidden> wrote:
>Uzi Paz <address@hidden> wrote:
>>I'm not sure that if you post a local (non-public) file, then giving its
>>local location is not a privacy problem.

> if it weren't included in the mailing.  It's only a potential problem
> when you access local files directly, via the command line startfile,
> a 'g'oto entry, or the DIRED_SUPPORT.  Otherwise, it was an HREF in
> a text/html document, and is not likely be a "secret".

Actually, my company in the name of security considers the paths of
all the files on it's intranet, whether HTML linked or not, a part of
the info they do not want out.  Yes, lynx has had this for a long time.
Not a lot of folk here use lynx, and even fewer email internal files 
outside.  However, it would be considerate for lynx to eventually,
in the name of security, at least an option not to generate the
URL name for machines 'inside' the intranet.  How to determine that
something is 'inside' the intranet may be the difficulty.  Perhaps if
the local network's IPs could in some way be specified?

In many cases, commercial companies are just now getting their
'intranet' going in an organized way.  Security/privacy issues are going
to rear their ugly heads in another wave when this happens.  It would be
nice to address as many as possible as early as possible.
-- 
Larry W. Virden                 INET: address@hidden
<URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.