From 2af23c908054db678dddf67928a74038849d2baf Mon Sep 17 00:00:00 2001
From: Eivind Eklund <eivind@FreeBSD.org>
Date: Sun, 9 Feb 1997 18:03:41 +0000
Subject: [PATCH] Remove suid bit from binary, and update manpage to reflect
 this.

---
 sbin/restore/Makefile  | 2 +-
 sbin/restore/restore.8 | 5 +++++
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/sbin/restore/Makefile b/sbin/restore/Makefile
index 5d49d0041b5a..916e6f009490 100644
--- a/sbin/restore/Makefile
+++ b/sbin/restore/Makefile
@@ -7,7 +7,7 @@ SRCS=	main.c interactive.c restore.c dirs.c symtab.c tape.c utilities.c \
 	dumprmt.c
 BINOWN=	root
 BINGRP=	tty
-BINMODE=6555
+BINMODE=2555
 MAN8=	restore.8
 MLINKS+=restore.8 rrestore.8
 .PATH:	${.CURDIR}/../dump
diff --git a/sbin/restore/restore.8 b/sbin/restore/restore.8
index 13a5583f0034..0c4938a7e150 100644
--- a/sbin/restore/restore.8
+++ b/sbin/restore/restore.8
@@ -399,6 +399,11 @@ it has no control over inode allocation;
 thus a full dump must be done to get a new set of directories
 reflecting the new inode numbering,
 even though the contents of the files is unchanged.
+.Pp
+To do a network restore, you have to run restore as root.  This is due
+to the previous security history of dump and restore.  (restore is
+written to be setuid root, but we are not certain all bugs are gone
+from the restore code - run setuid at your own risk.)
 .Sh HISTORY
 The
 .Nm restore