On 12/05/2023 09:36, Vincent Lefevre wrote:
On 2023-05-12 18:23:41 +0800, jeremy ardley wrote:
cd
mkdir .ssh
chmod 700 .ssh
ssh-keygen
Is there any reason why ssh-keygen doesn't create a .ssh directory
(with the right permissions) if it doesn't exist yet?
It does, and even let&
On 2023-05-12 18:23:41 +0800, jeremy ardley wrote:
> cd
>
> mkdir .ssh
>
> chmod 700 .ssh
>
> ssh-keygen
Is there any reason why ssh-keygen doesn't create a .ssh directory
(with the right permissions) if it doesn't exist yet?
--
Vincent Lefèvre - Web
On 12/5/23 13:50, Jeremy Ardley wrote:
ode[
ssh-keygen usually works better than ssh-keygem
try
cd
mkdir .ssh
ssh-keygen
I now remember some ssh functions check file and directory permissions
and will fail if not correct
Improved procedure:
cd
mkdir .ssh
chmod 700 .ssh
ssh
information... Done
openssh-client is already the newest version (1:7.9p1-10+deb10u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@wxTest:/home/igor/wxwidgets# ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): ^C
root@wxTest
Hi,
On Fri, May 12, 2023 at 12:19 AM Geert Stappers wrote:
>
> On Fri, May 12, 2023 at 12:07:00AM -0500, Igor Korot wrote:
> > Hi, ALL,
> > Is there a reason I can't run "ssh-keygen" as a regular user?
>
> Several :-)
>
>
> > I am able to do i
On Fri, May 12, 2023 at 12:07:00AM -0500, Igor Korot wrote:
> Hi, ALL,
> Is there a reason I can't run "ssh-keygen" as a regular user?
Several :-)
> I am able to do it as "root" though, but I think it shouldn't happen.
>
> Can someone shed some li
On 12/5/23 13:07, Igor Korot wrote:
Hi, ALL,
Is there a reason I can't run "ssh-keygen" as a regular user?
I am able to do it as "root" though, but I think it shouldn't happen.
Check the file permissions and ownership of ~/.ssh files ?
--
Jeremy
(Lists)
Hi, ALL,
Is there a reason I can't run "ssh-keygen" as a regular user?
I am able to do it as "root" though, but I think it shouldn't happen.
Can someone shed some light?
Thank you.
On 09/27/2016 12:19 AM, Martin McCormick wrote:
>...
> The short story is that the Mac now uses openssh-7
> instead of open-ssh-6. Dsa encryption keys have been declared
> obsolete for some time now and openssh-7 defaults to ignoring
> any id_dsa.pub keys you might have been using.
>...
That
After upgrading a Mac to sierra which is their newest
version of macosx, I discovered that I could no longer ssh
without a password in either direction from the Mac to a debian
system or vice versa. I first thought the system key had changed
but it hadn't.
The short story is that t
On Tuesday 19 August 2008 15:22:37 Jeff Soules wrote:
> On Tue, Aug 19, 2008 at 6:12 AM, Chris Davies <[EMAIL PROTECTED]>
wrote:
> > ssh-keygen -t rsa # Does anyone know whether dsa or rsa is better?
>
> I had understood that RSA is cryptographically superior to DSA,
On Tue, Aug 19, 2008 at 6:12 AM, Chris Davies <[EMAIL PROTECTED]> wrote:
> ssh-keygen -t rsa # Does anyone know whether dsa or rsa is better?
I had understood that RSA is cryptographically superior to DSA, at
least unless the DSA implementation is done very carefully (or so says
David Watson wrote:
On Tue, 19 Aug 2008 09:29:26 +0100
Bob Cox <[EMAIL PROTECTED]> wrote:
This is how I do it when setting up a new machine:
ssh-keygen -t dsa
cat ~/.ssh/id_dsa.pub | ssh [EMAIL PROTECTED] 'cat
.ssh/authorized_keys2'
Then:
ssh [EMAIL PROTECTED] (should work
Yes I updated the libssl to 0.9.8c-4ethc3 from 0.9.8c. Thanks for info! :)
Johannes Wiedersich wrote:
On 08/19/2008 01:28 PM, Rod James Bio wrote:
It seems that the difference in package really did matter.
apt-cache policy libssl0.9.8
libssl0.9.8:
Installed: 0.9.8c-4
Candidate: 0.9.8c-4et
On 08/19/2008 01:28 PM, Rod James Bio wrote:
> It seems that the difference in package really did matter.
>
> apt-cache policy libssl0.9.8
> libssl0.9.8:
> Installed: 0.9.8c-4
> Candidate: 0.9.8c-4etch3
> Version table:
> 0.9.8c-4etch3 0
>500 http://debian.savoirfairelinux.net stabl
/updates/main Packages
*** 0.9.8c-4 0
100 /var/lib/dpkg/status
Does anyone knows how to explain this. I'm pretty new to debian and
particulary linux. Thanks!
Chris Davies wrote:
Bob Cox <[EMAIL PROTECTED]> wrote:
This is how I do it when setting up a new machine:
ssh-ke
Thanks... but I still have the problem. I wonder if it concerns
upgrading any packages in Debian
Chris Davies wrote:
Bob Cox <[EMAIL PROTECTED]> wrote:
This is how I do it when setting up a new machine:
ssh-keygen -t dsa
cat ~/.ssh/id_dsa.pub | ssh [EMAIL PROTECTED] '
Bob Cox <[EMAIL PROTECTED]> wrote:
> This is how I do it when setting up a new machine:
> ssh-keygen -t dsa
>
> cat ~/.ssh/id_dsa.pub | ssh [EMAIL PROTECTED] 'cat >> .ssh/authorized_keys2'
>
Mmm. Interesting as I find authorized_keys works for me (none of m
On Tue, Aug 19, 2008 at 10:05:00 +0100, David Watson ([EMAIL PROTECTED]) wrote:
> To copy the key to the remote host you may can also use the following
> command:
>
> ssh-copy-id [EMAIL PROTECTED]
>
> which takes care of copying to the right location and ensuring the
> permissions are set corre
On Tue, 19 Aug 2008 09:29:26 +0100
Bob Cox <[EMAIL PROTECTED]> wrote:
> This is how I do it when setting up a new machine:
>
> ssh-keygen -t dsa
>
> cat ~/.ssh/id_dsa.pub | ssh [EMAIL PROTECTED] 'cat
> >> .ssh/authorized_keys2'
>
> Then:
> ss
On Tue, Aug 19, 2008 at 16:23:20 +0800, Rod James Bio ([EMAIL PROTECTED])
wrote:
> -- Forwarded message --
> From: Rod James Bio <[EMAIL PROTECTED]>
> Date: Tue, Aug 19, 2008 at 4:20 PM
> Subject: ssh-keygen
> To: debian-user@lists.debian.org, "Phi
-- Forwarded message --
From: Rod James Bio <[EMAIL PROTECTED]>
Date: Tue, Aug 19, 2008 at 4:20 PM
Subject: ssh-keygen
To: debian-user@lists.debian.org, "Philippine Linux Users' Group (PLUG)
Technical Discussion List" <[EMAIL PROTECTED]>
I am testing l
[EMAIL PROTECTED] wrote:
Tzafrir Cohen wrote:
On Tue, Jun 10, 2008 at 11:30:40AM +0200, Jochen Schulz wrote:
Nathaniel Homier:
Sudev Barar wrote:
Yes, but if you are carrying private key in your pen drive and you
loose it or some one copies it your total security is compromised
howsoever stro
> Tzafrir Cohen wrote:
>> On Tue, Jun 10, 2008 at 11:30:40AM +0200, Jochen Schulz wrote:
>>> Nathaniel Homier:
Sudev Barar wrote:
> Yes, but if you are carrying private key in your pen drive and you
> loose it or some one copies it your total security is compromised
> howsoever str
Tzafrir Cohen wrote:
On Tue, Jun 10, 2008 at 11:30:40AM +0200, Jochen Schulz wrote:
Nathaniel Homier:
Sudev Barar wrote:
Yes, but if you are carrying private key in your pen drive and you
loose it or some one copies it your total security is compromised
howsoever strong encryption algorithm wa
On Tue, Jun 10, 2008 at 11:30:40AM +0200, Jochen Schulz wrote:
> Nathaniel Homier:
> > Sudev Barar wrote:
> >>
> >> Yes, but if you are carrying private key in your pen drive and you
> >> loose it or some one copies it your total security is compromised
> >> howsoever strong encryption algorithm w
Jochen Schulz wrote:
Nathaniel Homier:
Sudev Barar wrote:
Yes, but if you are carrying private key in your pen drive and you
loose it or some one copies it your total security is compromised
howsoever strong encryption algorithm was used to generate the key
pair.
I was under the impression that
Tzafrir Cohen wrote:
On Tue, Jun 10, 2008 at 02:00:49AM -0600, Nathaniel Homier wrote:
I have the private key backed up on a desktop computer. The pass phrase
was generated with a high quality pseudo-random number generator using
20 characters consisting of letters, numbers and symbols. The
Nathaniel Homier:
> Sudev Barar wrote:
>>
>> Yes, but if you are carrying private key in your pen drive and you
>> loose it or some one copies it your total security is compromised
>> howsoever strong encryption algorithm was used to generate the key
>> pair.
>
> I was under the impression that th
On Tue, Jun 10, 2008 at 02:00:49AM -0600, Nathaniel Homier wrote:
> I have the private key backed up on a desktop computer. The pass phrase
> was generated with a high quality pseudo-random number generator using
> 20 characters consisting of letters, numbers and symbols. The key
> strength i
Sudev Barar wrote:
2008/6/10 Nathaniel Homier <[EMAIL PROTECTED]>:
all is well. I carry my public and private key on my thumb drive and the
private key is protected with a passphrase.
Whoops .. do not carry your private key around. No. Keep it somewhere
only you can access and rsik of loosing
Sudev Barar wrote:
2008/6/10 Nathaniel Homier <[EMAIL PROTECTED]>:
Yep, I got my key based auth working great now. I also took the time to
disable all other auth. Did "/etc/init.d/ssh restart" and checked again and
all is well. I carry my public and private key on my thumb drive and the
priva
Sudev Barar wrote:
2008/6/10 Nathaniel Homier <[EMAIL PROTECTED]>:
The nicknames are a good idea. I can pretend that I am on the Nostromo when
I am using mother. :)
;-)
It would be good idea to re-jig configuration file at son to allow
only key based authentication. This way even ssh log in
access my univ lab machines from
home):
1. Generate a key pair on mom (rsa is the newer algo)
$> ssh-keygen -t rsa
2. Copy the public key to the machine you want to log in to
$> ssh-copy-id -i ~/.ssh/id_rsa.pub [EMAIL PROTECTED]
3. Then try logging in from mom machine to son machine and ver
lab machines from
home):
1. Generate a key pair on mom (rsa is the newer algo)
$> ssh-keygen -t rsa
2. Copy the public key to the machine you want to log in to
$> ssh-copy-id -i ~/.ssh/id_rsa.pub [EMAIL PROTECTED]
3. Then try logging in from mom machine to son machine and verify it wor
use key based authentication. Now the question
is, do I run ssh-keygen on (son) or on (mom)? What I have done is, on
(son) is to:
$ssh-keygen -t dsa
$cd .ssh
$cat id_dsa.pub >> ~/.ssh/authorized_keys
This only allows you to run 'ssh localhost' on son. You could use the
t; ssh server on (son) to use key based authentication. Now the question
>> is, do I run ssh-keygen on (son) or on (mom)? What I have done is, on
>> (son) is to:
>> $ssh-keygen -t dsa
>> $cd .ssh
>> $cat id_dsa.pub >> ~/.ssh/authorized_keys
>
> This
authentication. Now the question
> is, do I run ssh-keygen on (son) or on (mom)? What I have done is, on
> (son) is to:
> $ssh-keygen -t dsa
> $cd .ssh
> $cat id_dsa.pub >> ~/.ssh/authorized_keys
This only allows you to run 'ssh localhost' on son. You could u
ssh-keygen on (son) or on (mom)? What I have done is, on
(son) is to:
$ssh-keygen -t dsa
$cd .ssh
$cat id_dsa.pub >> ~/.ssh/authorized_keys
I assume I take my id_dsa.pub to (mom) and hook it up with the latest
Filezilla version and Putty? Or do I do the ssh-keygen on (mom) and ad
d correct host key in /home/foobar/.ssh/known_hosts to get rid of this
>>>> message.
>>>> Offending key in /home/foobar/.ssh/known_hosts:3
>>> Line number 3.
>>>
>>> Remove that current line and you should be good.
>>>
>> Thanks. But I
osts to get rid of this
> >> message.
> >> Offending key in /home/foobar/.ssh/known_hosts:3
> >
> > Line number 3.
> >
> > Remove that current line and you should be good.
> >
> Thanks. But I think ssh-keygen method is more elegant even though bot
osts to get rid of this
> >> message.
> >> Offending key in /home/foobar/.ssh/known_hosts:3
> >
> > Line number 3.
> >
> > Remove that current line and you should be good.
> >
> > Cheers.
>
> Thanks. But I think ssh-keygen method is more elega
obar/.ssh/known_hosts:3
>
> Line number 3.
>
> Remove that current line and you should be good.
>
> Cheers.
Thanks. But I think ssh-keygen method is more elegant even though both
routes end up at the same place.
/KS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, 2007-05-03 at 00:40 -0400, KS wrote:
> Sudev Barar wrote:
> > On 03/05/07, KS <[EMAIL PROTECTED]> wrote:
> >> Allan Wind wrote:
> >> > On 2007-05-02T23:10:07-0400, KS wrote:
> >> >> However, ssh-keygen gives me the exact same output if I t
Sudev Barar wrote:
> On 03/05/07, KS <[EMAIL PROTECTED]> wrote:
>> Allan Wind wrote:
>> > On 2007-05-02T23:10:07-0400, KS wrote:
>> >> However, ssh-keygen gives me the exact same output if I try to do it
>> >> again even though the host does not exis
Allan Wind wrote:
> On 2007-05-02T23:10:07-0400, KS wrote:
>> However, ssh-keygen gives me the exact same output if I try to do it
>> again even though the host does not exist in the file (same output with
>> -v flag). Shouldn't it give a more informative output like:
On 2007-05-02T23:10:07-0400, KS wrote:
> However, ssh-keygen gives me the exact same output if I try to do it
> again even though the host does not exist in the file (same output with
> -v flag). Shouldn't it give a more informative output like: host entry
> not found in known_ho
Hi,
I was trying login to a remote host via ssh and due to a known change it
gave me the usual error that the host key had changed and text about
spoofing and MITM attack. After some man-page reading I found ssh-keygen
and it had options to remove a host from the known hosts file.
I was able to
p ssh ( 3.8.1p1-8.sarge.4)
Creating SSH2 RSA Key: this may take some time ...
/var/lib/dpk/info/ssh.postinst: line 387: 25078 invalid machine command
ssh-keygen -q -f "$file" -N '' "$@"
dpkg: Error ... ssh (--configure)
Subprocess post-installation script returned e
Þann 2006-04-13, 15:13:09 (+0200) skrifaði Jörg Herzinger:
> I installed Debain Sarge on an old Pentium II machine. No I got the problem
> that these 2 packages (ssh and pidentd) return an "invalid machine command"
> (translated from german so the exact english error may differ a bit).
> I alrea
Title: Nachricht
I installed Debain
Sarge on an old Pentium II machine. No I got the problem that these 2 packages
(ssh and pidentd) return an "invalid machine command" (translated from german so
the exact english error may differ a bit).
I already searched a
lot for a solution but couldn't
Yes, there's a distinction. DSA keys are for ssh2, RSA keys are for
ssh1. There's some amount of debate as to which is more secure: ssh2
encrypts more of the data, but always uses the same Diffie-Hellman
group (which means it's more likely somebody has sat down and cracked it).
In addition, I s
* Britton ([EMAIL PROTECTED]) [010802 14:08]:
>
> I can use passworless ssh login just fine by copying the public key to the
> ~/.ssh/authorized_keys2 of the machine I want to ssh to, without any
> modification to /etc/ssh/ssh_config, provided the public key was generated
> with ss
I can use passworless ssh login just fine by copying the public key to the
~/.ssh/authorized_keys2 of the machine I want to ssh to, without any
modification to /etc/ssh/ssh_config, provided the public key was generated
with ssh-keygen -t dsa and the passphrase left empty. When I try exactly
the
54 matches
Mail list logo
