Re: Sshd fix
From: Scott Mitchell (scott.mitchell@mail.com)
Date: 06/30/02
- Next message: Brett Glass: "Re: named 8.3.2-T1B vulnerable?"
- Previous message: Mark.Andrews@isc.org: "Re: libc flaw: BIND 9 closes most holes but also opens one"
- In reply to: Jack L. Stone: "Re: Sshd fix"
- Next in thread: Peter C. Lai: "Re: Sshd fix"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 30 Jun 2002 01:45:13 +0100 From: Scott Mitchell <scott.mitchell@mail.com> To: "Jack L. Stone" <jackstone@sage-one.net>
On Sat, Jun 29, 2002 at 07:25:08PM -0500, Jack L. Stone wrote:
> At 07:47 PM 6.29.2002 -0500, Scott Robbins wrote:
> >On Sat, Jun 29, 2002 at 05:35:50PM -0500, Jack L. Stone wrote:
> >> At 07:07 PM 6.28.2002 -0600, FreeBSD user wrote:
> >> >cd /usr/ports/security/openssh-portable && make -DOPENSSH_OVERWRITE_BASE
> >> install distclean
> >> >
> >> I just ran this on a test box and the sshd version shows no change... I saw
> >> it compile and install, but #sshd -V gives old version #...
> >>
> >> What did I do wrong here...??
Don't know if this part has already been answered... anyway, you need to
kill the old sshd and start your new one:
# kill `cat /var/run/sshd.pid`
...compare the ssh_config and sshd_config files in /etc/ssh with the -dist
versions installed by the port...make any appropriate config changes
# /usr/sbin/sshd
If that whines about any problems with the config files, fix those and try
again. Repeat until it works.
'sshd -V' should tell you 3.4p1, provided /usr/sbin is on your path and you
don't have any other ssh installed... are you sure you don't have one
lurking in /usr/local?
> This is what worries me too. I deinstalled the ssh port right afterwards,
> but I'm wondering what else is changed. I noticed it updated the
> openssl-0.9.6a to 0.9.6d that I didn't expect. The /var/db/pkg shows that
> "d" version installed.
>
> I'm running SSL on that machine and it still says 0.9.6.a when I load
> Apache_modssl and OpenSSH, etc. But, NOW, I'm really worried that I shot
> myself in the foot and this is waiting to bite me later.
>
> If anyone knows the answer to what Scott said about the next make world
> clobbering things, please let me know....
Just set NO_OPENSSH=true in /etc/make.conf. Then buildworld/installworld
will just ignore OpenSSH entirely.
I actually also added OPENSSH_OVERWRITE_BASE=true to make.conf, since I'll
probably forget to use it if I need to update the port before OpenSSH 3
makes it into -STABLE.
HTH,
Scott (the other one :-)
-- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott.mitchell@mail.com | 0xAA775B8B | -- Anon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
- Next message: Brett Glass: "Re: named 8.3.2-T1B vulnerable?"
- Previous message: Mark.Andrews@isc.org: "Re: libc flaw: BIND 9 closes most holes but also opens one"
- In reply to: Jack L. Stone: "Re: Sshd fix"
- Next in thread: Peter C. Lai: "Re: Sshd fix"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|