On Mon, Jun 30, 2008 at 02:54:57AM +0000, Pollywog wrote: > On Sunday 29 June 2008 23:55:25 Brandon S. Allbery KF8NH wrote: > > On 2008 Jun 29, at 19:22, Jeff Richards wrote: > > > After setting those options I kill -HUP the sshd process. > > > > I thought sshd ignored SIGHUP and you had to actually stop and restart > > it to pick up configuration changes. > > IIRC, I use SIGHUP in OpenBSD but in FreeBSD, I use /etc/rc.d/sshd restart
According to the OpenSSH sshd manpage, it handles SIGHUP, and re-reads the configuration file: sshd rereads its configuration file when it receives a hangup signal, SIGHUP, by executing itself with the name and options it was started with, e.g. /usr/sbin/sshd. > I also have > > PubkeyAuthentication yes > > in my sshd_config but perhaps this is the default, I am unsure. It is the default, in both sshd_config (server) and ssh_config (client). See the sshd_config(5) and ssh_config(5) manpages. > In some situations, I also need to edit ~/.ssh/config to allow the connection > and add 'PubkeyAuthentication yes' (on the host initiating the connection). Possibly you have to do this on machines with an older OpenSSH; I don't know if the default values were different then. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
