| Summary: | arandom(4) as documented in sshd_config(5)'s ChrootDirectory option does not exist on all platforms | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Christoph Anton Mitterer <calestyo> |
| Component: | Documentation | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | enhancement | CC: | djm |
| Priority: | P5 | ||
| Version: | 6.7p1 | ||
| Hardware: | Other | ||
| OS: | All | ||
it's already gone in HEAD (will be openssh-6.8) Close all resolved bugs after 7.3p1 release 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? |
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.