similar to: [Bug 1175] ssh-keygen is generating 2048 bit keys by default

http://bugzilla.mindrot.org/show_bug.cgi?id=566 Summary: ssh-keygen -l does not print key comment for rsa/dsa keys Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: ssh-keygen AssignedTo:

I am using Rsync to mirror my primary drive to a mounted second drive. I am using a crontab to control it: 30 3 * * * /usr/bin/rsync -rpogl /* /mnt/backup2/systemBackup/ The first run seems fine. But the subsequent running seems to double the original directory size. I notice this by running df -k. The destination size increases two fold, as if each time Rsync runs, it repeats itself, rather

https://bugzilla.mindrot.org/show_bug.cgi?id=3746 Bug ID: 3746 Summary: ssh-keyscan output format is not compatible with ssh-keygen -s Product: Portable OpenSSH Version: 9.2p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh-keyscan

Denny: Thank you. Problem solved. I switched SHUTDOWNCMD back to the default and added nut.powerfail to the shutdown runlevel. Now the UPS turns off after the system shutdown, if the shutdown is caused by lack of power going to the UPS. I checked and found the file sys-power:nut-2.7.4-r1:2018...log in /var/log/portage/elog/*. It did contain the message you pointed out. I should have checked

Every post I do to this mailinglist is followed by a bounce message from "centos.5.warren at recursor.net". I have no clue why this is being send to me, afaics some IP address is being blacklisted but I am not related to it. Am I the only one who gets this and can we remove this person from the mailinglist ? Kind regards, -- dag wieers, dag at wieers.com, http://dag.wieers.com/

http://bugzilla.mindrot.org/show_bug.cgi?id=459 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From markus at openbsd.org 2003-01-01

http://bugzilla.mindrot.org/show_bug.cgi?id=818 Summary: ssh-keygen Bad passphrase error Product: Portable OpenSSH Version: 3.8p1 Platform: PPC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: ssh-keygen AssignedTo: openssh-bugs at mindrot.org ReportedBy: sandino at

I'm trying to move from SSH1 to OpenSSH 2.9.9p2, under Solaris 8. Initial setup and testing seems to work... including the generation of a new RSA key. The key was created with "ssh-keygen -t rsa" and a passphrase; nothing unusual. I can SSH between machines, both running 2.9.9p2, and debug messages show that this file is being correctly read (I think). It prompts me for the

Dear all, Ed25519 public keys being as small as they are is very convenient. There is an opportunity to nudge the world towards modern algorithms. I believe choices made in OpenSSH can positively impact the wider eco-system and industry. I'd like to suggest ssh-keygen to generate an Ed25519 keypair, if invoked without any arguments. OpenSSH has supported Ed25519 since version 6.5 (January

Hi, Why is there still a limit on the length of a DSA key generated by ssh-keygen? I mean that ssh-keygen only expects 1024 as key length, or fails. Here is the code excerpt that enforces the limitation: if (type == KEY_DSA && *bitsp != 1024) fatal("DSA keys must be 1024 bits"); Commenting these two lines allows the generation of, say, 2048 bit DSA keys that work just fine

Hi, ssh-keygen is unable to change version 2 keys' comments (this was true in 2.9p2, and the changelog doesn't make me think this has changed), so I think this should be documented. Here's a patch to ssh-keygen.1 (It's based on an ssh-keygen patched with my previous patch). Cheers, Matthew --- ssh-keygen.1.orig Thu Sep 27 20:31:48 2001 +++ ssh-keygen.1 Thu Sep 27 20:40:32 2001

http://bugzilla.mindrot.org/show_bug.cgi?id=459 Summary: ssh-keygen doesn't know how to export private keys Product: Portable OpenSSH Version: 3.5p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh-keygen AssignedTo: openssh-unix-dev at mindrot.org

ssh-keygen already supports importing and exporting ssh keys using various formats. The "-m PEM" which should have been the easiest to be used with various of external application expects PKCS#1 encoded key, while many applications use SubjectPublicKeyInfo encoded key. This change adds SubjectPublicKeyInfo support, to ease integration with applications. Examples: ## convert

https://bugzilla.mindrot.org/show_bug.cgi?id=2429 Bug ID: 2429 Summary: ssh-keygen ignores keys that have CKA_ID == 0 Product: Portable OpenSSH Version: 6.9p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Smartcard Assignee:

https://bugzilla.mindrot.org/show_bug.cgi?id=2157 Bug ID: 2157 Summary: [man] ssh-keygen page says ECDSA keys can be 521 bits Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: Documentation Assignee:

http://bugzilla.mindrot.org/show_bug.cgi?id=1123 Summary: Never Completes Generating Keygen Product: Portable OpenSSH Version: 4.2p1 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh-keygen AssignedTo: bitbucket at mindrot.org ReportedBy: giffordj at

https://bugzilla.mindrot.org/show_bug.cgi?id=2145 Bug ID: 2145 Summary: ssh-keygen -R doesn't work when there are entries for "proxycommand" keys Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: Linux Status: NEW Severity: trivial Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=1319 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|2451 | Blocks| |2451 --- Comment #20 from Damien Miller <djm at mindrot.org>

What I'm hearing in this thread is: "a minority of people on planet Earth have a problem with the open-source implementation of ED25519, but instead of letting that minority choose to re-implement it when/if they want to, the rest of the community needs to stall their progress in improving security." And isn't the ED25519 code is already there on their machine? So isn't

On 9/4/23 16:43, Joseph S. Testa II wrote: > I very often see IT personnel and developers simply use the default > options for ssh-keygen. They just don't care/don't know to care. > Switching the default to ED25519 would bring the equivalent security > up from 112-bits to 128-bits (as 2048-bit RSA is equivalent to 112-bits > of symmetric strength), which would be a nice