trouble pushing to a ticket

71 views
Skip to first unread message

Steven Trogdon

unread,
Jan 20, 2022, 12:04:34 AM1/20/22
to sage-devel
I'm having difficulty pushing to a ticket, which I've done many times previously. When I push, i.e.

git trac push ticket#

I get

    STDERR: g...@trac.sagemath.org: Permission denied (publickey).
    STDERR: fatal: Could not read from remote repository.
    STDERR:
    STDERR: Please make sure you have the correct access rights
    STDERR: and the repository exists

My ssh key is correct (I have not changed it) however


gives

g...@trac.sagemath.org: Permission denied (publickey)

Any ideas how to resolve this. I can login, create a ticket but unable to push to a ticket.

Michael Orlitzky

unread,
Jan 20, 2022, 12:09:42 AM1/20/22
to sage-...@googlegroups.com
On Wed, 2022-01-19 at 21:04 -0800, Steven Trogdon wrote:
> I'm having difficulty pushing to a ticket, which I've done many times
> previously. When I push, i.e.
>
>

OpenSSH 8.8 (recently stable on Gentoo) disables RSA with SHA-1. You
can work around it, but probably the best long-term solution is to
replace your RSA key with an ECDSA one (ssh-keygen -t ecdsa) and re-
upload it to trac.


Steven Trogdon

unread,
Jan 20, 2022, 12:25:03 AM1/20/22
to sage-devel
Didn't mean to send a private email. This worked, thanks. I was aware of the change but didn't realize the extent. Thanks again.

François Bissey

unread,
Jan 20, 2022, 1:16:22 AM1/20/22
to sage-...@googlegroups.com
Just so you don’t feel alone, it happened to me earlier this month. I almost posted before googling the error. I have now replaced my 11 years old ssh key by a shinny new one.
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2110484e-b8a4-4ceb-8311-e1b1c946331bn%40googlegroups.com.

Dima Pasechnik

unread,
Jan 20, 2022, 4:10:16 AM1/20/22
to sage-devel
I'd recommend ed25519. ecdsa is known to be weak.
https://nbeguier.medium.com/a-real-world-comparison-of-the-ssh-key-algorithms-b26b0b31bfd9

>
>
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/915eb42665d47aa449e863f1ca856aa847de7067.camel%40orlitzky.com.

Markus Wageringel

unread,
Jan 21, 2022, 4:05:38 AM1/21/22
to sage-devel
OpenSSH 8.8 (recently stable on Gentoo) disables RSA with SHA-1. You
can work around it, but probably the best long-term solution is to
replace your RSA key with an ECDSA one (ssh-keygen -t ecdsa) and re-
upload it to trac.

 By the way, the trac server seems to be using an old version of OpenSSH (OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.13) which does not support the rsa-sha2-256 signature type yet. With a newer version of OpenSSH (≥7.2) on the trac server, it would be possible to use RSA keys, I think.

Reply all
Reply to author
Forward
0 new messages