lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Novice Problems


From: John aka DearOldDad
Subject: Re: LYNX-DEV Novice Problems
Date: Sun, 5 Jan 1997 23:30:01 -0500 (EST)

On Sun, 5 Jan 1997, Donald W. King wrote: ... in part ...
>      I am a member of the support group for the local freenet.  I have
> a good grasp of Unix but have little knowledge of the intricacies of the
> internet. ... ...
>      I have noticed that other servers have numbers before their links
> which can be used rather than incessant use of the up and down arrow keys.
> How does one configure lynx in this way.

lynx docs are simply html docs and the tag for numbering the links is
<ol> which means ordered link, end it with </ol>.

>      The final problem is with users reading local files which we would
> prefer they do not see (eg. /etc/passwd).  We are in the process of 
> installing shadow passwords but there are other files which are a
> security hazard.  Is there a way of allowing only .htm or .html files
> to be read by users (other than anonymous users).

This is a much bigger problem, but if you are familiar with unix as
you say, the solution is simple.  All files in a public directory
should be assigned the correct file permissions.  DOS calls that
attributes, unix calls it permissions.  They are 1 read, 2 write, 3
execute, and can be set for a owner, b group, c all ... so that's 9
combinations of permissions.  Typically public files should be set so
the owner (that's you) has read write execute permission, others have
only read permission (there are exceptions, ie counters need public
write and execute permissions).

If you are unix literate you should know how to do this, if not, it's
too lengthy to explain here, and is also off topic for this group
(list).  Hope this helps.  BYE.  Any ? I would be glad to reply by
private email.

John

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]