Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Revise text about filenames as suggested by Geoff Wing in PR#6366. 

Add reference in SEE ALSO to RFC 1350
This commit is contained in:
fair 1999-01-13 11:16:57 +00:00
parent 2e6f16f3b8
commit 59e43c6946
1 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
libexec/tftpd/tftpd.8
View File

@ -1,4 +1,4 @@
.\" $NetBSD: tftpd.8,v 1.8 1998/07/29 11:31:22 lukem Exp $
.\" $NetBSD: tftpd.8,v 1.9 1999/01/13 11:16:57 fair Exp $
.\"
.\" Copyright (c) 1983, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -53,15 +53,12 @@ Internet Trivial File Transfer Protocol server
.Nm
is a server which supports the
.Tn DARPA
Trivial File Transfer
Protocol.
Trivial File Transfer Protocol.
The
.Tn TFTP
server operates
at the port indicated in the
server operates at the port indicated in the
.Ql tftp
service description;
see
service description; see
.Xr services 5 .
The server is normally started by
.Xr inetd 8 .
@ -71,12 +68,13 @@ The use of
does not require an account or password on the remote system.
Due to the lack of authentication information,
.Nm
will allow only publicly readable files to be
accessed.
Files containing the string ``/\|\fB.\|.\fP\|/'' are not allowed.
Files may be written only if they already exist and are publicly writable.
will allow only publicly readable files to be accessed.
Filenames beginning in ``\|\fB.\|.\fP\|/'' or
containing ``/\|\fB.\|.\fP\|/'' are not allowed.
Files may be written to only if they already exist and are publicly writable.
.Pp
Note that this extends the concept of
.Dq public
.Qq public
to include
all users on all hosts that can be reached through the network;
this may not be appropriate on all systems, and its implications
@ -117,7 +115,7 @@ to
.Ar directory
on startup.
This is recommended for security reasons (so that files other than
those in the
those in the
.Pa /tftpboot
directory aren't accessable).
If the remote host passes the directory name as part of the
@ -148,6 +146,12 @@ as well.
.Sh SEE ALSO
.Xr tftp 1 ,
.Xr inetd 8
.Rs
.%R RFC
.%N 1350
.%D July 1992
.%T "The TFTP Protocol (Revision 2)"
.Re
.Sh HISTORY
The
.Nm
@ -184,6 +188,6 @@ Because there is no user-login or validation within
the
.Tn TFTP
protocol, the remote site will probably have some
sort of file-access restrictions in place. The
exact methods are specific to each site and therefore
sort of file-access restrictions in place.
The exact methods are specific to each site and therefore
difficult to document here.