2015-08-08 19:14 GMT-03:00 Simon Hanna <simon.hanna@serve-me.info>:

...

I have 51 packages with the user Jristz but I decide change the .git/config and change sed "s|aur4.|aur.|g" but now I can't upload packages and fixes.

I attempt changing my ssh-key and I test everyone (ecdsa,ed25519,rsa1,dsa,rsa) but without succes, then I attempt to reclone a package for test but aur refuse to allow me to do it.

so far my .ssh/config is Host aur.archlinux.org aur4.archlinux.org Hostname aur.archlinux.org IdentityFile ~/.ssh/id_rsa.pub User aur Port 22 and I have aur.archlinux.org in the know hosts list, so What could happened that I cant even clone my packages?? -- *Pablo Lezaeta* AFAIK IdentityFile should be the private key not the public key. Regardless, it's hard to help when you don't provide exact commands and

On Sat, Aug 08, 2015 at 06:59:48PM -0300, Pablo Lezaeta Reyes wrote: their output. give us the clone command you use and the output you get. You can try "ssh aur.archlinux.org help" just to check if you can reach aur. next stop would be the urls you use for cloning/pulling/pushing

the aur article, the last time I check not have info about the config file, so is need add. but you are right the .pub was the problem. thanks and I hope this will be not repeat; but the lack of info about the propper config of the config file could has prevented this because I first check wiki/AUR -- *Pablo Lezaeta*

* Pablo Lezaeta Reyes <prflr88@gmail.com> (Sat, 8 Aug 2015 19:33:26 -0300):

thanks and I hope this will be not repeat; but the lack of info about the propper config of the config file could has prevented this because I first check wiki/AUR

FYI, it is in the Wiki, on the SSH page to which you are pointed at: https://wiki.archlinux.org/index.php/SSH_keys#Managing_multiple_keys

2015-08-08 19:51 GMT-03:00 Marcel Korpel <marcel.korpel@gmail.com>:

...

* Pablo Lezaeta Reyes <prflr88@gmail.com> (Sat, 8 Aug 2015 19:33:26 -0300):

...

thanks and I hope this will be not repeat; but the lack of info about the propper config of the config file could has prevented this because I first check wiki/AUR

FYI, it is in the Wiki, on the SSH page to which you are pointed at: https://wiki.archlinux.org/index.php/SSH_keys#Managing_multiple_keys

yes and not, who will know that the user of aur.archlinux.org need to be aur?

in the ssh they show how configure generically (and I admit aI missread the part of the publickey) but not how need to be for aur specifically.

but my main issue is solved so thanks y'all (?) -- *Pablo Lezaeta* Actually you do not have to configure your .ssh/config at all! If you are using a standard name for your ssh key (sticking to the defaults that ssh-keygen suggests), you are doing absolutely nothing special with your config. The things you set up in the .ssh/config are:

On Sat, Aug 08, 2015 at 08:03:02PM -0300, Pablo Lezaeta Reyes wrote: the wiki mentions the link to clone which is $ git clone ssh://aur@aur.archlinux.org/foobar.git with basic ssh knowledge, and EVERYONE using linux nowadays should now about ssh, it should be clear that the user is aur (aur@...) the user - which you used in the clone, so you don't need it the port - aur uses standard ports proxy - aur doesnt require a proxy, and you don't seem to need one either shortcut for the url - which you obviously didn't use either so you can just delete everything from your config file. In fact I couldn't find any mention of .ssh/config in the wiki article of the AUR... lastly I just tried your version of .ssh/config and the exact error message I got was: git clone ssh://aur@aur.archlinux.org/foobar.git Cloning into 'foobar'... The authenticity of host 'aur.archlinux.org (5.9.250.164)' can't be established. ECDSA key fingerprint is SHA256:L71Q91yHwmHPYYkJMDgj0xmUuw16qFOhJbBr1mzsiOI. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'aur.archlinux.org' (ECDSA) to the list of known hosts. Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. which clearly states you have an issue with your publickey which is an ssh-issue...