summaryrefslogtreecommitdiffstats
path: root/usr.bin/shar
diff options
context:
space:
mode:
authorwosch <wosch@FreeBSD.org>1997-03-31 17:58:27 +0000
committerwosch <wosch@FreeBSD.org>1997-03-31 17:58:27 +0000
commitb110e6a8c07898bbb79152909430bb4ea3a1c636 (patch)
treeee43e9060a525ba9bde880eb1a26a02f7aa30740 /usr.bin/shar
parent3e63a14f34ec33ecb046158328122a09db58c4d7 (diff)
downloadFreeBSD-src-b110e6a8c07898bbb79152909430bb4ea3a1c636.zip
FreeBSD-src-b110e6a8c07898bbb79152909430bb4ea3a1c636.tar.gz
Add a note in BUGS section that shar(1) cannot handle files
without a newline ('\n') as last character.
Diffstat (limited to 'usr.bin/shar')
-rw-r--r--usr.bin/shar/shar.13
1 files changed, 3 insertions, 0 deletions
diff --git a/usr.bin/shar/shar.1 b/usr.bin/shar/shar.1
index 9084a7e..9bf6d9e 100644
--- a/usr.bin/shar/shar.1
+++ b/usr.bin/shar/shar.1
@@ -64,6 +64,9 @@ or
.Nm Shar
makes no provisions for special types of files or files containing
magic characters.
+.Nm Shar
+cannot handle files without a newline ('\\n')
+as last character.
.Pp
It is easy to insert trojan horses into
.Nm shar
OpenPOWER on IntegriCloud