Mike Silbersack wrote:
On Sun, 13 May 2001, Peter Wemm wrote:
Mike Silbersack wrote:
1. Is ssh working yet?
Yes, it is working perfectly. The only problem is that it now works
slightly differently to what people have expected. ie: it treats
sshv1 rsa keys as totally seperate to
Kris Kennaway wrote:
On Sat, May 12, 2001 at 04:24:48PM -0700, Terry Lambert wrote:
Jordan Hubbard wrote:
ssh works just fine for me in 4.3. You must be doing something
wrong.
I used that sysinstall thing Jordan wrote to upgrade
from a 4.2 to a 4.3 system.
Is that what I'm
Matthew Jacob [EMAIL PROTECTED] writes:
There's a very likely 3rd possibility:
ssh works fine, but the upgrade process has holes that even traps the
experienced.
I'll confirm this. I've done several upgrades and fresh installs in
the past 2 weeks, and sometimes the /etc/pam.conf
Hello there!
On Sat, 12 May 2001, Valentin Nechayev wrote:
On -current, I watched identical problem with mystical ssh brokenness,
with No RSA support in libcrypto and libssl message from ssh,
after when all possible underwater stones were verified (including
/dev/random and /dev/urandom,
David Taylor([EMAIL PROTECTED])@2001.05.13 21:16:33 +:
On Sun, 13 May 2001, Karsten W. Rohrbach wrote:
---
VERSION_NUMBER=`grep [$]FreeBSD: $0 | cut -d ' ' -f 4`
echo mergemaster version ${VERSION_NUMBER}
---
That would appear to be mergemaster grepping for the $FreeBSD$ line
On Sun, May 13, 2001 at 11:14:05AM -0700, Doug Barton wrote:
That said, I am working on some things to make mm handle cases where the
user has not modified the files easier to deal with.
We should have /etc/MD5SUM.install which contains the MD5 checksum of the
installed files. The
Kris Kennaway([EMAIL PROTECTED])@2001.05.12 19:33:54 +:
On Sat, May 12, 2001 at 04:24:48PM -0700, Terry Lambert wrote:
Jordan Hubbard wrote:
ssh works just fine for me in 4.3. You must be doing something
wrong.
I used that sysinstall thing Jordan wrote to upgrade
from a
Karsten W. Rohrbach wrote:
is there a way to make the upgrade process easier by doing the thing
mergemaster does but with an interface that does not kill the average
ordinary user with a simple prompt without really useful help
incantating strange phrases to summon the subprocesses that diff
On Sun, 13 May 2001, Karsten W. Rohrbach wrote:
btw, mergemaster's version number generation for the help/syntax page is
broken because it displays the number of the running kernel not the
version of mergemaster itself:
---
VERSION_NUMBER=`grep [$]FreeBSD: $0 | cut -d ' ' -f 4`
echo
On Sat, 12 May 2001, Terry Lambert wrote:
Erik Trulsson wrote:
Exactly how is rpping it out of FreeBSD supposed to make ssh work?
I don't necessarily want it to work or not work, I just
want it to quit being a pain in my backside.
If it can't be made to upgrade correctly, then ripping
Mike Silbersack wrote:
On Sat, 12 May 2001, Terry Lambert wrote:
Erik Trulsson wrote:
Exactly how is rpping it out of FreeBSD supposed to make ssh work?
I don't necessarily want it to work or not work, I just
want it to quit being a pain in my backside.
If it can't be made to
On Sun, 13 May 2001, Peter Wemm wrote:
Mike Silbersack wrote:
1. Is ssh working yet?
Yes, it is working perfectly. The only problem is that it now works
slightly differently to what people have expected. ie: it treats
sshv1 rsa keys as totally seperate to sshv2 rsa keys.
Let me
Le 2001-05-13, Peter Wemm écrivait :
The simplest thing is to do a ssh-keygen to generate a new RSA key and
update ~/.ssh/authorized_keys2 once per remote machine that you connect
to. Once that is done, it never bothers you again. You can change
/etc/ssh/ssh_config so that it says
Thomas Quinot wrote:
Le 2001-05-13, Peter Wemm écrivait :
The simplest thing is to do a ssh-keygen to generate a new RSA key and
update ~/.ssh/authorized_keys2 once per remote machine that you connect
to. Once that is done, it never bothers you again. You can change
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu option, SSH stops working, for no good reason
(_any_ reason is no good).
It complains about RSA not being in libcrypto, even though
nm shows that that claim is full of crap.
Yes, I have
On Sat 2001-05-12 (04:24), Terry Lambert wrote:
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu option, SSH stops working, for no good reason
(_any_ reason is no good).
It complains about RSA not being in libcrypto, even though
On Saturday 12 May 2001 06:24, Terry Lambert wrote:
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu option, SSH stops working, for no good reason
(_any_ reason is no good).
You did make the needed additions to /etc/pam.conf,
Sat, May 12, 2001 at 04:24:29, tlambert2 (Terry Lambert) wrote about SSH Must Die:
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu option, SSH stops working, for no good reason
(_any_ reason is no good).
It complains about RSA
ssh works just fine for me in 4.3. You must be doing something
wrong.
- Jordan
From: Terry Lambert [EMAIL PROTECTED]
Subject: SSH Must Die
Date: Sat, 12 May 2001 04:24:29 -0700
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu
On Sat, May 12, 2001 at 07:23:20AM -0700, Jordan Hubbard wrote:
ssh works just fine for me in 4.3. You must be doing something
wrong.
- Jordan
From: Terry Lambert [EMAIL PROTECTED]
Subject: SSH Must Die
Date: Sat, 12 May 2001 04:24:29 -0700
This whole ssh B.S. is very annoying
Jordan Hubbard wrote:
ssh works just fine for me in 4.3. You must be doing something
wrong.
I used that sysinstall thing Jordan wrote to upgrade
from a 4.2 to a 4.3 system.
Is that what I'm doing wrong? ;^).
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Erik Trulsson wrote:
Exactly how is rpping it out of FreeBSD supposed to make ssh work?
I don't necessarily want it to work or not work, I just
want it to quit being a pain in my backside.
If it can't be made to upgrade correctly, then ripping it
out also satisfies the criteria necessary to
j wrote:
On Saturday 12 May 2001 06:24, Terry Lambert wrote:
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu option, SSH stops working, for no good reason
(_any_ reason is no good).
You did make the needed additions to
On Saturday 12 May 2001 18:40, Terry Lambert wrote:
j wrote:
On Saturday 12 May 2001 06:24, Terry Lambert wrote:
This whole ssh B.S. is very annoying.
After an upgrade from 4.2 to 4.3 using a CDROM boot plus
upgrade menu option, SSH stops working, for no good reason
(_any_
On Sat, May 12, 2001 at 04:31:29PM -0700, Terry Lambert wrote:
Erik Trulsson wrote:
Exactly how is rpping it out of FreeBSD supposed to make ssh work?
I don't necessarily want it to work or not work, I just
want it to quit being a pain in my backside.
If it can't be made to upgrade
I used that sysinstall thing Jordan wrote to upgrade
from a 4.2 to a 4.3 system.
Is that what I'm doing wrong? ;^).
Probably! Anybody would be the first to tell you that sysinstall's
upgrade feature only gets you there unassisted maybe 3 times out of
5. The contents of /etc are
On Sat, May 12, 2001 at 04:24:48PM -0700, Terry Lambert wrote:
Jordan Hubbard wrote:
ssh works just fine for me in 4.3. You must be doing something
wrong.
I used that sysinstall thing Jordan wrote to upgrade
from a 4.2 to a 4.3 system.
Is that what I'm doing wrong? ;^).
27 matches
Mail list logo
