Unable to push to trac server

[Georgia Channing]

Hello!

I am having persistent issues checking out tickets and pushing back to tickets with trac (I am sometimes randomly able to checkout, but I can never seem to push). 

Basically, no matter what I do, I get an error saying:

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.

I attach a screenshot of the error and of my .git config. Below the last line of my git config, there is another line with my token because I authenticate through GitHub.

Sometimes I get a different error saying: urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)>

Any help is greatly appreciated!

[Dima Pasechnik]

Please specify your setup is some detail.

Are you using a GitHub account, or a "legacy" trac account?

Have you uploaded your ssh key to trac?

(Or/and to GitHub?)

Without this it would not work.

Type of ssh key matters too. You  need a sufficiently long RSA key, or an Ed25519 key

--
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/75a96a18-1197-4415-9775-584376626828n%40googlegroups.com.

[Sylvain Pelissier]

Maybe I can update the page https://doc.sagemath.org/html/en/developer/trac.html. It still shows a RSA-2048 example. I run into the same problem lately. What is the minimum size for RSA ?

[Dima Pasechnik]

On Wed, 3 Aug 2022, 10:05 Sylvain Pelissier, <sylvain....@gmail.com> wrote:

Maybe I can update the page https://doc.sagemath.org/html/en/developer/trac.html. It still shows a RSA-2048 example. I run into the same problem lately. What is the minimum size for RSA ?

4096 is certainly going to work, and considered reasonably secure. 

3072 should work too

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/48478f97-b03c-490a-8605-117a8a885e54n%40googlegroups.com.

[Georgia Channing]

Thanks! I am using a Github account to authenticate. I have uploaded my ssh-key to trac and GitHub. My key is RSA-4096. Any more ideas?

[Dima Pasechnik]

On Thu, 4 Aug 2022, 19:16 'Georgia Channing' via sage-devel, <sage-...@googlegroups.com> wrote:

Thanks! I am using a Github account to authenticate. I have uploaded my ssh-key to trac and GitHub. My key is RSA-4096. Any more ideas?

just to avoid any doubt, make sure you uploaded the public parts of keys, i.e. .pub files.

What is the output of

ssh -v g...@trac.sagemath.org info

- to be run in terminal?

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/d5e0ba98-5ca3-4c21-b0e0-04104a1afb94n%40googlegroups.com.

[Georgia Channing]

Yep! The public part of the key was uploaded. The attached image is the result of running the ssh command you suggested.

[Dima Pasechnik]

Another common pitfall are permissions on keys and ~/.ssh

The latter should only be readable/writable to your user, as well as private keys.

(but .pub keys should be readable to the world)

I.e. (my usename here is dimpase)

$ cd

$ ls -al | grep .ssh
drwx------ 1 dimpase dimpase             246 May 23 10:00 .ssh

$ ls -l .ssh/id_rsa*
-rw------- 1 dimpase dimpase 1766 Feb 18 14:04 .ssh/id_rsa
-rw-r--r-- 1 dimpase dimpase  391 Feb 18 14:04 .ssh/id_rsa.pub

Please check you have the same.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5400a680-5580-4433-bb53-d19f66dd5715n%40googlegroups.com.

[Georgia Channing]

Thanks for all your feedback! I double-checked and all my accessibility settings seem to match yours. I did mess around with creating a new RSA key and that generated a new, different, more promising error, though I am still struggling to decode it. See attached.

Best (and many many thanks),

Georgia

[Dima Pasechnik]

On Tue, Aug 9, 2022 at 5:39 AM 'Georgia Channing' via sage-devel <sage-...@googlegroups.com> wrote:

Thanks for all your feedback! I double-checked and all my accessibility settings seem to match yours. I did mess around with creating a new RSA key and that generated a new, different, more promising error, though I am still struggling to decode it. See attached.

It looks OK - did you try to use it with git (i.e. pulling/pushing)?

 

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/d7944493-100b-4444-a2ff-ead98560fdffn%40googlegroups.com.

[enriqu...@gmail.com]

My .ssh folder looks as yours but the ssh command ends with Permission denied (publickey).and I cannot push a commit to a ticket. I am in Fedora 36 if it gives a hint.

[enriqu...@gmail.com]

Actually, now I was able to push my commit even if ssh still gives an error

[Dima Pasechnik]

On Tue, Aug 23, 2022 at 4:02 PM enriqu...@gmail.com <enriqu...@gmail.com> wrote:

Actually, now I was able to push my commit even if ssh still gives an error

It might be that it gives errors on some keys, and on one of them it works.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/65553eec-8d67-45ff-8d7c-9934bb49274an%40googlegroups.com.