upstream commit
/dev/random has created the same effect as /dev/arandom (and /dev/urandom) for quite some time. Mop up the last few, by using /dev/random where we actually want it, or not even mentioning arandom where it is irrelevant.
This commit is contained in:
parent
b6de5ac9ed
commit
a1418a0033
|
@ -33,8 +33,8 @@
|
|||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $OpenBSD: sshd_config.5,v 1.178 2014/09/09 09:45:36 djm Exp $
|
||||
.Dd $Mdocdate: September 9 2014 $
|
||||
.\" $OpenBSD: sshd_config.5,v 1.179 2014/11/22 18:15:41 deraadt Exp $
|
||||
.Dd $Mdocdate: November 22 2014 $
|
||||
.Dt SSHD_CONFIG 5
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -336,8 +336,6 @@ nodes such as
|
|||
.Xr stdin 4 ,
|
||||
.Xr stdout 4 ,
|
||||
.Xr stderr 4 ,
|
||||
.Xr arandom 4
|
||||
and
|
||||
.Xr tty 4
|
||||
devices.
|
||||
For file transfer sessions using
|
||||
|
|
Loading…
Reference in New Issue