On Tue, Feb 26, 2002 at 11:23:00AM -0500, Noah Meyerhans wrote:
> On Tue, Feb 26, 2002 at 10:45:56AM +0200, Danie Roux wrote:
> > This is what I've done:
> >
> > I've enabled ssh1 support by "dpkg-reconfigure ssh"
> > On my Debian machine I generated a ssh1 key without a passphrase.
> > I then cop
On Tue, Feb 26, 2002 at 05:46:32PM +0100, Ulf Rompe wrote:
> This works for interactive use. But it doesn't fit the needs of cron
> jobs. OK, you *can* use ssh-agent withing cron jobs, but you give up
> more security than you gain using such a hack.
>
> So if you need an ssh connection within a cr
Noah Meyerhans <[EMAIL PROTECTED]> writes:
> Creating an SSH key with a blank passphrase is *absolutely* the
> wrong way to go about this. Yes, it will work, but if anybody ever
> manages to get their hands on the private key, they've got access to
> your account on the remote machine.
>
> Passphr
On Tue, Feb 26, 2002 at 10:45:56AM +0200, Danie Roux wrote:
> This is what I've done:
>
> I've enabled ssh1 support by "dpkg-reconfigure ssh"
> On my Debian machine I generated a ssh1 key without a passphrase.
> I then copied the identity.pub to the RedHat machine and renamed it to
> ~/.ssh/au
On Tue, Feb 26, 2002 at 08:03:17AM -0600, Colin Watson wrote:
> The -v flag will give you some more verbose output (you can use that
> flag up to three times to increase the verbosity further). Does that
> help find the problem?
Yes, thank you very much!
debug1: Remote: Bad file modes for /opt/we
On Tue, Feb 26, 2002 at 06:30:53AM -0800, Jeremy T. Bouse wrote:
> Honestly SSH2's publickey or hostbased authentication might be an
> easier choice...
Would have upgraded in a blink of an eye ... but I'm not root on that
machine :-)
--
Danie Roux *shuffle* Adore Unix
t; I'm trying to do key authentication between the current unstable openssh
> and a remote box running RedHat and the following version of
> ssh-nonfree:
>
> SSH Version 1.2.27, protocol version 1.5
>
> Regular logins work. I want to login without using a password.
>
> This
On Tue, Feb 26, 2002 at 10:45:56AM +0200, Danie Roux wrote:
> This is what I've done:
>
> I've enabled ssh1 support by "dpkg-reconfigure ssh"
> On my Debian machine I generated a ssh1 key without a passphrase.
> I then copied the identity.pub to the RedHat machine and renamed it to
> ~/.ssh/au
I'm trying to do key authentication between the current unstable openssh
and a remote box running RedHat and the following version of
ssh-nonfree:
SSH Version 1.2.27, protocol version 1.5
Regular logins work. I want to login without using a password.
This is what I've done:
I'
Is the switch from ssh-nonfree to ssh (OpenSSH) seamless? Do they use the same
config files? If I
install ssh, ssh-nonfree will be removed and I'm wondering if doing this
remotely will result in me
being unable to connect to the machine remotely afterwards.
Thanks,
Liam
--
Liam Ward
On Sun, Nov 11, 2001 at 12:43:11PM -0500, Stuart Krivis wrote:
> But, it's been pretty obvious that non-free is provided for the user's
> convenience or to provide stepping stones to a completely free system
> over time. That leaves it up to the maintainer of an individual non-free
> package to
On Sunday, November 11, 2001, at 09:54 AM, Wichert Akkerman wrote:
Previously Bernd Eckenfels wrote:
just a small information, I have at least 2 confirmed reports about
Hacked
Debian Boxes. All of them are hacked by exploiting the old nonfree-ssh
and
installing a rootkit. Fortunatelly the roo
Immediately after installing ssh-nonfree, I get this error when trying
to start sshd:
Starting Secure Shell server: sshd/etc/ssh-nonfree/sshd_config line 26:
Bad configuration option: loglevel
.
This is being read from the default config file installed with the
package. Any ideas as to what the
Daishi Harada <[EMAIL PROTECTED]> writes:
DH> 2. If I use ssh-nonfree (1.2.27-5), I can use ssh, but I get the
DH> following warnings:
DH> % ssh
DH> Agent parent directory is not sticky, mode is 40777 it should be
041777
DH> [EMAIL PROT
controlling tty. Cannot read passphrase.
preventing me from accessing at all.
However, as root, I can use ssh normally without problems.
Using -v, the last debug message as a regular user is:
debug: Doing password authentication.
2. If I use ssh-nonfree (1.2.27-5), I can use ssh, but I get the
15 matches
Mail list logo