1. That's what strong pass-phrases are used for - to limit the access to
the
private key.
2. You could say "sure - so you replace the password by a pass-phrase" but
you'd still need the private key, which is never transferred over the net.
3. You can allow access for multiple keys into the same a
On 04/11/06, Adam Kennedy <[EMAIL PROTECTED]> wrote:
I always thought the problem with keys and passwordless login was that
you end up with cascading exploits.
If I login from box A --> box B with keys, and someone hacks box A, then
they automatically have access to box B, and C, and D and anyt
Passwdless login is infinitly better than passwd infact on my system:
PermitRootLogin without-password
with say 1024bit key and say 10^6 tries per second lets see ...
1024 log (2) / 10^6 is say 10^300 years to crack! Much better than any 10 char
passwd.
The weak link is storing YOUR private k
On 11/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
[..snip..]
Passwdless login is infinitly better than passwd infact on my system:
PermitRootLogin without-password
with say 1024bit key and say 10^6 tries per second lets see ...
1024 log (2) / 10^6 is say 10^300 years to crack! Much bett
On Friday 03 November 2006 20:14, [EMAIL PROTECTED] wrote:
> > Why Choose not to use ssh keys.
> > The default is to both allow passwords, and/or keys.
>
> I use SSH keys on many servers, but there are a bunch in this group
> where the admins have *blocked* use of SSH keys and thus I would like
> t
On 03/11/2006, at 4:15 PM, Gonzalo Servat wrote:
...
Since Expect needs to either spawn a program or access a FH,
Net::SSH::Perl no longer suited my needs. I started to look into
spawning SSH from Net::Telnet, then using Expect on the Net::Telnet
object.
After looking at the man page for Net::
On 03/11/06, Gonzalo Servat <[EMAIL PROTECTED]> wrote:
> You don't need root access to create a passwordless login (providing the
> admin's haven't explicitly changed the default).
I know, but imagine asking a server admin in a company where there are
lots of policies, bla bla, if I can have a
On 11/3/06, Scott Ragen <[EMAIL PROTECTED]> wrote:
Why Choose not to use ssh keys.
The default is to both allow passwords, and/or keys.
I use SSH keys on many servers, but there are a bunch in this group
where the admins have *blocked* use of SSH keys and thus I would like
to have a system that
Why Choose not to use ssh keys.
The default is to both allow passwords, and/or keys.
You don't need root access to create a passwordless login (providing the
admin's haven't explicitly changed the default).
All you do on your mail machine is use ssh-keygen to generate the key you
want, put the pr
Hi All,
Here's a tough one, at least it has been for me! As you can
see, I've almost given up.
Here's the situation: I manage a lot of servers at my work. They are
all *NIX and so I've decided to write a bunch of Perl scripts to
handle a lot of the repetitive tasks I have to do on said s
10 matches
Mail list logo
