aboutsummaryrefslogtreecommitdiff
path: root/manual/crypt.texi
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@suse.de>2000-03-08 08:58:29 +0000
committerAndreas Jaeger <aj@suse.de>2000-03-08 08:58:29 +0000
commit93773779e35a9652bb7576db68b412ab14a8faa2 (patch)
tree471cc8663cd659abe499aafaac4d3c87848903e8 /manual/crypt.texi
parentd92c02e833a1cb8cb6b2506067ba5f3550a7de70 (diff)
downloadglibc-93773779e35a9652bb7576db68b412ab14a8faa2.tar
glibc-93773779e35a9652bb7576db68b412ab14a8faa2.tar.gz
glibc-93773779e35a9652bb7576db68b412ab14a8faa2.tar.bz2
glibc-93773779e35a9652bb7576db68b412ab14a8faa2.zip
Update.
2000-03-08 Andreas Jaeger <aj@suse.de> * manual/crypt.texi: Fix paths.
Diffstat (limited to 'manual/crypt.texi')
-rw-r--r--manual/crypt.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/manual/crypt.texi b/manual/crypt.texi
index f17fab9b59..60b065774f 100644
--- a/manual/crypt.texi
+++ b/manual/crypt.texi
@@ -118,7 +118,7 @@ this case, it is recommended that users write their own @code{getpass}
substitute. For instance, a very simple substitute is as follows:
@smallexample
-@include ../crypt/mygetpass.c.texi
+@include mygetpass.c.texi
@end smallexample
The substitute takes the same parameters as @code{getline}
@@ -180,7 +180,7 @@ machines, and in many applications it would not be acceptable to let an
attacker know what time the user's password was last set.
@smallexample
-@include ../crypt/genpass.c.texi
+@include genpass.c.texi
@end smallexample
The next program shows how to verify a password. It prompts the user
@@ -188,7 +188,7 @@ for a password and prints ``Access granted.'' if the user types
@code{GNU libc manual}.
@smallexample
-@include ../crypt/testpass.c.texi
+@include testpass.c.texi
@end smallexample
@comment crypt.h