When I try to push or fetch to the ASDF repo, I get this error:
``` $ git fetch origin Received disconnect from 148.251.248.130 port 22:2: Too many authentication failures Disconnected from 148.251.248.130 port 22 fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists. ```
Not sure why that would have changed...
By the way, this is not my normal email, but emails from my work address (rpgoldman@sift.net) are being bounced because of the reverse lookup policy on common-lisp.net.
It seems to be puking on this:
``` Your IP address 50.249.120.161 is associated with the domain sift.net. Nevertheless your message appears to be sent from mail.sift.net. ```
On Jul 15, 2020, at 18:22, Robert Goldman rpgoldman@gmail.com wrote:
When I try to push or fetch to the ASDF repo, I get this error:
$ git fetch origin Received disconnect from 148.251.248.130 port 22:2: Too many authentication failures Disconnected from 148.251.248.130 port 22 fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
I couldn’t find any logs of the authentication failures, but perhaps I wasn’t looking in the right place as gitlab is rather baggy monster at this point.
Maybe we could spend time interactively debugging the problem, so I have a better chance of figuring out what the problem is?
Otherwise, perhaps use a new SSH key?
[…]
By the way, this is not my normal email, but emails from my work address (rpgoldman@sift.net) are being bounced because of the reverse lookup policy on common-lisp.net.
It seems to be puking on this:
Your IP address 50.249.120.161 is associated with the domain sift.net. Nevertheless your message appears to be sent from mail.sift.net.
Double-plus ungood! Could you forward me a copy of the bounced message?
—
I’ll keep taking a look at your problems as I have time, and try to mobilize more resources to figure out the problems: real bad for the maintainer of ASDF to not have basic access working…
On Jul 22, 2020, at 08:43, Mark Evenson evenson@panix.com wrote:
On Jul 15, 2020, at 18:22, Robert Goldman rpgoldman@gmail.com wrote:
When I try to push or fetch to the ASDF repo, I get this error:
$ git fetch origin Received disconnect from 148.251.248.130 port 22:2: Too many authentication failures Disconnected from 148.251.248.130 port 22 fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
I couldn’t find any logs of the authentication failures, but perhaps I wasn’t looking in the right place as gitlab is rather baggy monster at this point.
Maybe we could spend time interactively debugging the problem, so I have a better chance of figuring out what the problem is?
Otherwise, perhaps use a new SSH key?
[…]
You should be using an ssh-key listed in file://common-lisp.net/home/rpgoldman/.ssh/authorized_keys.
Can you do a naked SSH from that host?
—
As for interactively debugging this, if you stop by #common-lisp.net on FreeNode IRC, try to flag down an admin. Coverage is EU-centric, so earlier or extremely late in your day would be best.
Apologies for problems with common-lisp.net hosting: ASDF maintainance shouldn’t be broken, ever.
On Wed, 15 Jul 2020 11:22:51 -0500, Robert Goldman said:
By the way, this is not my normal email, but emails from my work address (rpgoldman@sift.net) are being bounced because of the reverse lookup policy on common-lisp.net.
It seems to be puking on this:
Your IP address 50.249.120.161 is associated with the domain sift.net. Nevertheless your message appears to be sent from mail.sift.net.
I think SIFT has misconfigured reverse DNS:
# host -t a mail.sift.net. mail.sift.net has address 50.249.120.161 # host -t a 50.249.120.161 161.120.249.50.in-addr.arpa domain name pointer sift.net. # host -t a sift.net. sift.net has address 50.249.120.162
The reverse DNS for 50.249.120.161 should be mail.sift.net. for best practice (see https://www.debouncer.com/reverse-dns-check?ip=50.249.120.161).
__Martin
Thanks, Martin. Yes, this seems to be a problem. Many places seem to be OK with just looking up `sift.net`, but cl.net is one of a handful that won't accept that and need the mail address to line up exactly with `mail.sift.net`.
I've reported this to our sysadmins and they are trying to figure out a solution.
On 22 Jul 2020, at 5:44, Martin Simmons wrote:
On Wed, 15 Jul 2020 11:22:51 -0500, Robert Goldman said:
By the way, this is not my normal email, but emails from my work address (rpgoldman@sift.net) are being bounced because of the reverse lookup policy on common-lisp.net.
It seems to be puking on this:
Your IP address 50.249.120.161 is associated with the domain sift.net. Nevertheless your message appears to be sent from mail.sift.net.
I think SIFT has misconfigured reverse DNS:
# host -t a mail.sift.net. mail.sift.net has address 50.249.120.161 # host -t a 50.249.120.161 161.120.249.50.in-addr.arpa domain name pointer sift.net. # host -t a sift.net. sift.net has address 50.249.120.162
The reverse DNS for 50.249.120.161 should be mail.sift.net. for best practice (see https://www.debouncer.com/reverse-dns-check?ip=50.249.120.161).
__Martin
-
Mark Evenson -
Martin Simmons -
Robert Goldman