Kris Kennaway([EMAIL PROTECTED])@Mon, Sep 04, 2000 at 08:09:59PM -0700:
On Mon, 4 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Jordan Hubbard writes:
: Well, it's at least one step closer - all they have to do now (the US
: people) is install the rsaref port to have the
How is this affected by RSA releasing their patent to the public domain
today? URL http://www.rsasecurity.com/news/pr/000906-1.html
-Charlie
On Mon, Sep 04, 2000 at 02:35:14PM -0700, Kris Kennaway wrote:
On Mon, 4 Sep 2000, Jordan K. Hubbard wrote:
jkh 2000/09/04 08:50:15 PDT
Jordan Hubbard wrote:
This will be semi-broken for the next 17 days for US people because sshd
won't work out of the box if you have "Protocol 1" defined, which is in
the default config (and removing it may surprise people upgrading)
Well, it's at least one step closer - all they have
On Mon, 4 Sep 2000, Jordan K. Hubbard wrote:
jkh 2000/09/04 08:50:15 PDT
Modified files:
release/sysinstall config.c
Log:
enable sshd by default. This only effects *new* installs, so
upgraders will not receive any unpleasant surprises.
This will be semi-broken
This will be semi-broken for the next 17 days for US people because sshd
won't work out of the box if you have "Protocol 1" defined, which is in
the default config (and removing it may surprise people upgrading)
Well, it's at least one step closer - all they have to do now (the US
people) is
On Mon, 4 Sep 2000, Jordan Hubbard wrote:
This will be semi-broken for the next 17 days for US people because sshd
won't work out of the box if you have "Protocol 1" defined, which is in
the default config (and removing it may surprise people upgrading)
Well, it's at least one step
On Mon, 4 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Jordan Hubbard writes:
: Well, it's at least one step closer - all they have to do now (the US
: people) is install the rsaref port to have the already-running sshd
: work correctly post-install, correct?
Unless they want
