Displaying 20 results from an estimated 10000 matches similar to: "[PATCH] remove /etc/rc references from ssh-keygen.1"
2001 Sep 27
0
[PATCH] document inability to change v2 keys' comments with ssh-keygen
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
2001 Jul 21
1
Defaults for protocol and ssh-keygen (and an introduction)
Hi,
I have recently taken over as Debian maintainer for ssh. This
means you're going to be getting lots of mail from me in the near
future :-) I'm aiming to be a little more active than the last
maintainer, but the Debian packages were really out of date, so I've
quite a lot of work (and probably some old bugs) to deal with.
Anyhow, onto the first question. ssh these days uses
2012 Jul 28
1
[PATCH] ssh-keygen: support public key import/export using SubjectPublicKeyInfo
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
2015 Mar 24
3
[Debian bug 781107] ssh-keygen -F return code has changed and is not documented
Hi,
I tripped over the effects of commit 660854 [0] when moving some
infrastructure from Debian 7 to 8 (openssh 6.0 to 6.7); our ansible
module used "return 0, but no output" for 'host not found in known_hosts
file', and now complains that ssh-keygen is returning an error status. I
don't think this change in API was announced in the release notes?
i.e. ssh-keygen -F
2010 Jun 19
3
[Bug 1784] New: ssh-keygen fails when filename of key file contains multiple slashes
https://bugzilla.mindrot.org/show_bug.cgi?id=1784
Summary: ssh-keygen fails when filename of key file contains
multiple slashes
Product: Portable OpenSSH
Version: 5.2p1
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh-keygen
AssignedTo:
2010 Apr 02
3
[Bug 1749] New: ssh-keygen cant "import" a generic x509 rsa public key
https://bugzilla.mindrot.org/show_bug.cgi?id=1749
Summary: ssh-keygen cant "import" a generic x509 rsa public key
Product: Portable OpenSSH
Version: 5.4p1
Platform: Other
OS/Version: Other
Status: NEW
Severity: normal
Priority: P2
Component: ssh-keygen
AssignedTo: unassigned-bugs at
2001 Oct 22
1
ssh-keygen can't recognize its own keys?
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
2002 Mar 26
0
[Bug 187] New: ssh-keygen not converting from and to SECSH standard correctly
http://bugzilla.mindrot.org/show_bug.cgi?id=187
Summary: ssh-keygen not converting from and to SECSH standard
correctly
Product: Portable OpenSSH
Version: 3.1p1
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: ssh-keygen
AssignedTo:
2002 Dec 29
0
[Bug 459] New: ssh-keygen doesn't know how to export private keys
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
2003 Aug 09
2
[Bug 623] ssh, ssh-keygen and possibly others do not honour $HOME
http://bugzilla.mindrot.org/show_bug.cgi?id=623
Summary: ssh, ssh-keygen and possibly others do not honour $HOME
Product: Portable OpenSSH
Version: 3.6.1p2
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-bugs at mindrot.org
2010 Sep 25
1
ssh-keygen with libpkcs11.so can't work
Hi,
I'm trying the new feature "ssh-keygen(1) now supports signing certificate
using a CA key that has been stored in a PKCS#11 token".
According to the manpage, I should use "-D" option. And I had a problem
with this option.
root at ubuntu-desktop[/home/adam/temp7]#ssh-keygen -s ca_key.pub -D
libpkcs11.so -I key_id id_rsa.pub
dlopen libpkcs11.so failed: libpkcs11.so:
2001 Sep 27
1
[PATCH] document scp -r better
Hi,
Patch from Adam McKenna (via Debian BTS) to improve how we document
scp -r:
--- scp.1.orig Thu Sep 27 21:28:12 2001
+++ scp.1 Thu Sep 27 21:29:22 2001
@@ -72,7 +72,9 @@
Preserves modification times, access times, and modes from the
original file.
.It Fl r
-Recursively copy entire directories.
+Recursively copy entire directories. A trailing slash (/) on a
source file
+name means
2007 Oct 03
4
[Bug 1372] New: sshd(8) and ssh-keygen(1) refer to non-existent moduli(5)
http://bugzilla.mindrot.org/show_bug.cgi?id=1372
Summary: sshd(8) and ssh-keygen(1) refer to non-existent
moduli(5)
Product: Portable OpenSSH
Version: 4.7p1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
AssignedTo: bitbucket at
2023 Mar 02
0
[Bug 3545] New: Output from ssh-keygen -e, which should always be a public-key, is not accepted by ssh-keygen -l
https://bugzilla.mindrot.org/show_bug.cgi?id=3545
Bug ID: 3545
Summary: Output from ssh-keygen -e, which should always be a
public-key, is not accepted by ssh-keygen -l
Product: Portable OpenSSH
Version: 8.9p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: minor
Priority: P5
2014 Apr 01
4
How can I have the same ssh key for dual boot (ssh-keygen)
I use:
ssh-keygen -t rsa
to generate a key file (id_rsa.pub) which I copy into authorized_keys2 on
other machines in order to permit ssh to these machines without being
asked for a password.
The thing is that I have dual boot on this machine: one for fedora and
one for ubuntu. The two key files which were generated on these machine
are different.
Is there a way so that I will have the same key
2023 Sep 03
1
[patch] ssh-keygen(1): generate Ed25519 keys when invoked without arguments
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
2020 Apr 25
2
[PATCH 1/3] Add private key protection information extraction to ssh-keygen
Add private key protection information extraction to shh-keygen using -v
option on top of -y option which is already parsing the private key.
Technically, the passphrase isn't necessary to do this, but it is the
most logical thing to do for me.
Adding this to -l option is not appropriate because fingerprinting is
using the .pub file when available.
An other idea is to add a new option, I
2011 Sep 02
4
[Bug 1929] New: ssh-keygen fails to build because PKCS11 is not available
https://bugzilla.mindrot.org/show_bug.cgi?id=1929
Bug #: 1929
Summary: ssh-keygen fails to build because PKCS11 is not
available
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.8p2
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
2003 Oct 08
2
[Bug 735] ssh-keygen, SunOS 4.1.4, Undefined symbol _strtoul
http://bugzilla.mindrot.org/show_bug.cgi?id=735
Summary: ssh-keygen, SunOS 4.1.4, Undefined symbol _strtoul
Product: Portable OpenSSH
Version: -current
Platform: Sparc
OS/Version: SunOS
Status: NEW
Severity: major
Priority: P2
Component: ssh-keygen
AssignedTo: openssh-bugs at mindrot.org
2001 Jan 29
1
I: [PATCH] ssh-keygen
Greetings!
According to documentation, "-x" and "-X" options of ssh-keygen designed
to work only with DSA keys. It means that key_type_name variable have to
be initialized to "dsa" if any of these options were specified.
Regards,
Dmitry
+-------------------------------------------------------------------------+
Dmitry V. Levin mailto://ldv at fandra.org