** Changed in: gnome-keyring
Importance: Unknown => High
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desk
** Changed in: gnome-keyring
Status: New => Fix Released
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
This bug was fixed in the package gnome-keyring - 2.26.3-0ubuntu1
---
gnome-keyring (2.26.3-0ubuntu1) karmic; urgency=low
* New upstream version:
- Fix problem with RSA key sizes that are not a multiple of 8.
This affected use of SSH keys in particular. (lp: #348126, #3478
** Changed in: gnome-keyring
Status: Unknown => New
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskt
sideshowmel: I'm not sure of the difference between your case and
Trifon's case. If it is different please generate keys and instructions
that reproduce it and post those to the upstream bug. Thanks.
** Changed in: gnome-keyring (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => Ubuntu Des
To recreate the problem that I am seeing, you MUST use a password-
protected private key. Mine is 4096-bit RSA, but I've done a bit of
searching and see this is happening for users with 1024 and 2048 bit RSA
keys as well.
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchp
** Changed in: gnome-keyring
Status: New => Unknown
** Changed in: gnome-keyring
Bugwatch: GNOME Bug Tracker #577842 => GNOME Bug Tracker #576700
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because yo
Jon, I agree the upstream bug is a duplicate and have now marked it as such.
The correct upstream bug is:
http://bugzilla.gnome.org/show_bug.cgi?id=576700
Trifon, thanks - the steps you have given reproduce it perfectly for me. I
have updated the upstream bug with this test case
sideshowmel, I
@ Robert Ancell :
Curious, was this RSA key you used password-protected? Because I see the same
results as you saw with a non-protected key, but this problem still persists
with all users on my 9.04 system with a protected key.
--
ssh are using ssh-userauth but ignores private key
https://bug
I copied my ~/.ssh/id_rsa to ~/.ssh/identity and this problem suddenly
disappeared. I upgraded from 8.04->8.10->9.04 recently.
I looked at the debug output and it was sending the key over, but for
some reason it wasn't working.
--
ssh are using ssh-userauth but ignores private key
https://bugs.l
** Tags added: jaunty regression-release
** Tags removed: regression-potential
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in u
Thank you Robert for taking the time to test this. The sequence you
described works correctly for me as well. However, I don't think this
goes through ssh-agent, I think ssh looks in ~/.ssh/id_rsa without using
the agent at all.
Here's the sequence that doesn't work for me (using your notation)
t
Trifon, thanks for the keys. I've tried the following:
1. Create two new user accounts on my machine (up-to-date Jaunty) for users
test1 and test2
2. Copy rsa1023.pub to /home/test1/.ssh/authorized_keys2
3. Copy rsa1023 to /home/test2/.ssh/id_rsa and set permissions to 600
4. Open GNOME session
Explicitly the commands I've used are:
te...@localhost$ mkdir ~/.ssh
te...@localhost$ cp rsa1023.pub ~/.ssh/authorized_keys2
te...@localhost$ mkdir ~/.ssh
te...@localhost$ cp rsa1023 ~/.ssh/id_rsa
te...@localhost$ chmod 600 ~/.ssh/id_rsa
te...@localhost$ ssh te...@localhost
--
ssh are using ssh-u
My experiences are as follows:
Ubuntu 9.04
Logged into GNOME as a user
copy existing id_rsa file to ~/.ssh/ and do a chmod 700 on it.
(Keyfile being used here is 4096 bit RSA)
open terminal and issue the following:
$ ssh-add
Returns: "Enter passphrase for /home//.ssh/id_rsa:" (or something to that
could you also comment on the GNOME bug?
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs mailing list
Attaching the public key corresponding to the private key above
** Attachment added: "rsa1023.pub"
http://launchpadlibrarian.net/26037930/rsa1023.pub
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are
I can reproduce the behavior reported by rancor, but using an RSA
1023-bit key. I have never had problems with ssh-agent before I upgraded
to Jaunty. I can still login using "ssh -i mykey", but never with ssh-
agent.
When I tried to generate a new RSA 2048-bit key, ssh-agent worked
without a probl
@Robert Ancell: I haven't tried SSH since the problem started, I must do
some test and return to you
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
The reported workaround by taking the ssh agent out of the loop by
putting this in your .bashrc :
export SSH_AUTH_SOCK=
at least makes my keys usable again. Still annoying that I have to type
my passphrase every time now, but at least I can access my machines
again.
--
ssh are using ssh-useraut
I have not read all post, but I think I have found the reason of this.
I have two keys. One works without problems, the other don't work.
The correct working key is a dsa key. The rsa key don't work.
I hope this will help a little bit.
--
ssh are using ssh-userauth but ignores private key
http
I think, but I am not sure, that this is reported upstream already at
http://bugzilla.gnome.org/show_bug.cgi?id=576700
** Bug watch added: GNOME Bug Tracker #576700
http://bugzilla.gnome.org/show_bug.cgi?id=576700
** Bug watch added: Debian Bug tracker #524018
http://bugs.debian.org/cgi-bin
Also (just for tracking) Debian bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=524018
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnom
rancor: Do you still have the same setup that you used to generate the
keys? If possible could you try and generate some new keys (ideally one
that fails and one that works) and attach them to this bug?
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
Seems this is not triaged at all, since there's no reproduction recipe
and it does not happen for a lot of people. Robert, could you please
have a look at this and try to find a reproducer/solution? Thanks!
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Confirmed
** Changed in: g
** Changed in: gnome-keyring
Status: Unknown => New
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskt
Thank you for sending the bug to GNOME
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Triaged
** Also affects: gnome-keyring via
http://bugzilla.gnome.org/show_bug.cgi?id=577842
Importance: Unknown
Status: Unknown
--
ssh are using ssh-userauth but ignores privat
Thank you for your sending the bug there
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Triaged
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Incomplete
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You receive
Posted a new bug: http://bugzilla.gnome.org/show_bug.cgi?id=577842
** Bug watch added: GNOME Bug Tracker #577842
http://bugzilla.gnome.org/show_bug.cgi?id=577842
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification bec
I will now open a new bug on bugzilla.gnome.org
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lis
the ssh agent is gnome-keyring
** Changed in: seahorse (Ubuntu)
Status: New => Invalid
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
it would be nice if somebody having the issue could open the bug on
bugzilla.gnome.org where the people writting the code will actually read
it, there is no ubuntu triager knowing that code well enough to debug
that easily
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchp
@Sebastien Bacher: I don't know how to create this issue. I just
upgraded 8.10 to 9.04 on three machines and two of them have this
problem, the other works fine. I haven't tweaked anything manually. The
only thing I can think of is that the machines has been upgraded several
times. 8.04 -> 8.10 ->
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-keyring (U
Not an ssh bug, but rather a seahorse or gnome-keyring regression,
opening related tasks and marking regression-potential.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
** Also affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-keyring (
35 matches
Mail list logo
