If we need to make an exception we can do it and properly document the
reason but by default we should just use the default login class.
rc.d uses daemon or the login class provided in login.conf.d so this has
no impact there.
discussed with sthen@, tb@ and robert@
praying that my grep/sed skills did not break anything and still
believing in portbump :-)
Significant changes since 1.6.0:
* A new -u option instructs spiped to run as a different uid/gid.
* RDRAND x86 CPU extensions (if available) are used as an additional source
of entropy. (Note that they are only used as a *supplemental* source, and
if the operating system provides strong entropy then it doesn't matter if
RDRAND works.)
* SHA x86 CPU extensions (if available) are used to speed up computations.
Few CPUs support these yet.
* spipe now prints a warning if it cannot connect to the target host.
spiped (pronounced "ess-pipe-dee") is a utility for creating
symmetrically encrypted and authenticated pipes between socket
addresses, so that one may connect to one address (e.g., a UNIX socket
on localhost) and transparently have a connection established to another
address (e.g., a UNIX socket on a different system). This is similar to
'ssh -L' functionality, but does not use SSH and requires a pre-shared
symmetric key.
spipe (pronounced "ess-pipe") is a utility which acts as an spiped
protocol client (i.e., connects to an spiped daemon), taking input from
the standard input and writing data read back to the standard output.