Re: CVS import: src/crypto/external/bsd/openssh/dist
In message <20141023010616.ecdc117f...@rebar.astron.com> on Wed, 22 Oct 2014 21:06:16 -0400, chris...@zoulas.com (Christos Zoulas) wrote: > On Oct 23, 9:41am, t...@netbsd.org (Takahiro Kambe) wrote: > -- Subject: Re: CVS import: src/crypto/external/bsd/openssh/dist > > | It is also good news for me, but where can I find out from commit > | messages?? > > The commit messages are the changes upstream. Most of the changes are > merged. This is an exception. IC and thanks for your quick clarification. -- Takahiro Kambe /
Re: CVS import: src/crypto/external/bsd/openssh/dist
On Oct 23, 9:41am, t...@netbsd.org (Takahiro Kambe) wrote: -- Subject: Re: CVS import: src/crypto/external/bsd/openssh/dist | It is also good news for me, but where can I find out from commit | messages?? The commit messages are the changes upstream. Most of the changes are merged. This is an exception. christos
Re: CVS import: src/crypto/external/bsd/openssh/dist
In message on Wed, 22 Oct 2014 13:03:11 + (UTC), chris...@astron.com (Christos Zoulas) wrote: > In article <20141022.125753.108286502...@uninett.no>, > Havard Eidnes wrote: Potentially-incompatible changes >>> [ ... ] * sshd(8): Support for tcpwrappers/libwrap has been removed. >>> [ ... ] >>> Are there any plans to re-introduce this support locally in the >>> NetBSD code base? "Permanently" or as part of a transition (to what?) >>> period? >> >>Wowza! If I understand correctly, this renders py-denyhosts >>ineffective, and is IMHO a step in the wrong direction. > > Well, they removed it but we did not. It is also good news for me, but where can I find out from commit messages?? -- Takahiro Kambe /
Re: CVS import: src/crypto/external/bsd/openssh/dist
> In article <20141022.125753.108286502...@uninett.no>, > Havard Eidnes wrote: Potentially-incompatible changes >>> [ ... ] * sshd(8): Support for tcpwrappers/libwrap has been removed. >>> [ ... ] >>> Are there any plans to re-introduce this support locally in the >>> NetBSD code base? "Permanently" or as part of a transition (to what?) >>> period? >> >>Wowza! If I understand correctly, this renders py-denyhosts >>ineffective, and is IMHO a step in the wrong direction. > > Well, they removed it but we did not. Good, thanks, that restores some peace of mind. Regards, - Håvard
Re: CVS import: src/crypto/external/bsd/openssh/dist
In article <20141022.125753.108286502...@uninett.no>, Havard Eidnes wrote: >>> Potentially-incompatible changes >> [ ... ] >>> * sshd(8): Support for tcpwrappers/libwrap has been removed. >> [ ... ] >> Are there any plans to re-introduce this support locally in the >> NetBSD code base? "Permanently" or as part of a transition (to what?) >> period? > >Wowza! If I understand correctly, this renders py-denyhosts >ineffective, and is IMHO a step in the wrong direction. Well, they removed it but we did not. christos
Re: CVS import: src/crypto/external/bsd/openssh/dist
>> Potentially-incompatible changes > [ ... ] >> * sshd(8): Support for tcpwrappers/libwrap has been removed. > [ ... ] > Are there any plans to re-introduce this support locally in the > NetBSD code base? "Permanently" or as part of a transition (to what?) > period? Wowza! If I understand correctly, this renders py-denyhosts ineffective, and is IMHO a step in the wrong direction. Regards, - Håvard
Re: CVS import: src/crypto/external/bsd/openssh/dist
"Christos Zoulas" writes: > Module Name: src > Committed By: christos > Date: Sun Oct 19 16:28:40 UTC 2014 > > Update of /cvsroot/src/crypto/external/bsd/openssh/dist > In directory ivanova.netbsd.org:/tmp/cvs-serv3513 > > Log Message: > Changes since OpenSSH 6.6 > = > > Potentially-incompatible changes [ ... ] > * sshd(8): Support for tcpwrappers/libwrap has been removed. [ ... ] Are there any plans to re-introduce this support locally in the NetBSD code base? "Permanently" or as part of a transition (to what?) period? -jarle -- There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-one errors.
