Actually, now I was able to push my commit even if ssh still gives an error
El martes, 23 de agosto de 2022 a las 16:44:41 UTC+2, enriqu...@gmail.com escribió: > 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. > El viernes, 5 de agosto de 2022 a las 21:40:26 UTC+2, dim...@gmail.com > escribió: > >> 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. >> >> >> >> On Fri, Aug 5, 2022 at 5:52 PM 'Georgia Channing' via sage-devel < >> sage-...@googlegroups.com> wrote: >> >>> Yep! The public part of the key was uploaded. The attached image is the >>> result of running the ssh command you suggested. >>> >>> [image: Screen Shot 2022-08-05 at 12.50.16 PM.png] >>> On Thursday, August 4, 2022 at 2:53:04 PM UTC-4 dim...@gmail.com wrote: >>> >>>> >>>> >>>> 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? >>>> >>>> >>>>> On Tuesday, August 2, 2022 at 9:52:30 AM UTC-4 dim...@gmail.com wrote: >>>>> >>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> On Tue, 2 Aug 2022, 14:29 'Georgia Channing' via sage-devel, < >>>>>> sage-...@googlegroups.com> wrote: >>>>>> >>>>>>> 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! >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/sage-devel/75a96a18-1197-4415-9775-584376626828n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- >>>>> 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/d5e0ba98-5ca3-4c21-b0e0-04104a1afb94n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/sage-devel/d5e0ba98-5ca3-4c21-b0e0-04104a1afb94n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> 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/5400a680-5580-4433-bb53-d19f66dd5715n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/sage-devel/5400a680-5580-4433-bb53-d19f66dd5715n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/65553eec-8d67-45ff-8d7c-9934bb49274an%40googlegroups.com.
