Bug 2289 - arandom(4) as documented in sshd_config(5)'s ChrootDirectory option does not exist on all platforms
Summary: arandom(4) as documented in sshd_config(5)'s ChrootDirectory option does not ...
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 6.7p1
Hardware: Other All
: P5 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-10 13:14 AEDT by Christoph Anton Mitterer
Modified: 2016-08-02 11:16 AEST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2014-10-10 13:14:20 AEDT
Hi.

This is just a cosmetic thingy and probably only affects certain platforms (e.g. Linux):

The ChrootDirectory directive in sshd_config(5) says this:
>For an interactive session this requires at least
>a shell, typically sh(1), and basic /dev nodes such
>as null(4), zero(4), stdin(4), stdout(4), stderr(4),
>arandom(4) and tty(4) devices

Well stdin(4), stdout(4), stderr(4) don't exist on e.g. Linux either (talking about the manpages themselves),... but I guess the arandom is something one could really correct (respectively name alternative names as well), since it's not only the manage the is missing, but the file as well (guess only BSDs have arandom?)


Cheers,
Chris.
Comment 1 Damien Miller 2014-12-22 19:51:04 AEDT
it's already gone in HEAD (will be openssh-6.8)
Comment 2 Damien Miller 2016-08-02 10:41:59 AEST
Close all resolved bugs after 7.3p1 release
Comment 3 Christoph Anton Mitterer 2016-08-02 11:16:00 AEST
just one thing:
on those platforms that don't have arandom(4), isn't something else needed instead (like urandom or so), that should be mentioned?