Is there any reason why there is no OpenSSH 3.1
package for debian available yet?
is the "OpenSSH_3.0.2p1" version avaiable in the
testing/unstable tree already patched
against the "March 7, 2002: Off-by-one error in the channel code" security
hole?
thanks
Peter
On Sun, 2002-04-07 at 14:34, Peter Lieven wrote:
Is there any reason why there is no OpenSSH 3.1 package for debian available yet?
is the OpenSSH_3.0.2p1 version avaiable in the testing/unstable tree already
patched
against the March 7, 2002: Off-by-one error in the channel code security hole
Peter Lieven [EMAIL PROTECTED] cum veritate scripsit:
is the OpenSSH_3.0.2p1 version avaiable in the testing/unstable tree already
patched
against the March 7, 2002: Off-by-one error in the channel code security hole?
yes.
--
[EMAIL PROTECTED] : Junichi Uekawa
On Sun, Apr 07, 2002 at 02:53:16PM +0200, Mark Janssen wrote:
Debian usually patches the (security) bug, without going straight to the
new upstream release, but only upgrading the package number
That's only the case with stable. In unstable, there is no reason not
to go straight to the new
Is there any reason why there is no OpenSSH 3.1
package for debian available yet?
is the "OpenSSH_3.0.2p1" version avaiable in the
testing/unstable tree already patched
against the "March 7, 2002: Off-by-one error in the channel code" security
hole?
thanks
Peter
On Sun, 2002-04-07 at 14:34, Peter Lieven wrote:
Is there any reason why there is no OpenSSH 3.1 package for debian available
yet?
is the OpenSSH_3.0.2p1 version avaiable in the testing/unstable tree
already patched
against the March 7, 2002: Off-by-one error in the channel code security
Peter Lieven [EMAIL PROTECTED] cum veritate scripsit:
is the OpenSSH_3.0.2p1 version avaiable in the testing/unstable tree
already patched
against the March 7, 2002: Off-by-one error in the channel code security
hole?
yes.
--
[EMAIL PROTECTED] : Junichi Uekawa
On Sun, Apr 07, 2002 at 02:53:16PM +0200, Mark Janssen wrote:
Debian usually patches the (security) bug, without going straight to the
new upstream release, but only upgrading the package number
That's only the case with stable. In unstable, there is no reason not
to go straight to the new
8 matches
Mail list logo