From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Cannot assign requested address
Date: Sat, 30 Jan 2021 12:15:14 +0000 [thread overview]
Message-ID: <56B261B4-18CD-448F-9D0D-7707189A8DA4@ipfire.org> (raw)
In-Reply-To: <9375720c-917c-d846-220e-cf703cc7718b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
Hi,
Can we fix this though? This seems to happen on a regular basis and it is slightly annoying :)
-Michael
> On 30 Jan 2021, at 12:06, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello Matthias,
>
> thanks for your reply.
>
> Since I just happened to be around here due to various things (fixing ghostscript, binutils and hyperscan,
> plus doing some research on outdated TLS connections from and to our mail systems for good measure), I unblocked
> your IP address again.
>
> It seems as your logins trigger a lot of authentication failures - perhaps because your SSH client has
> multiple keys present and tries to log into people.ipfire.org with each of them, thus causing several
> failed attempts at once?
>
> Either way: Sorry for the inconvenience. :-/
>
> Thanks, and best regards,
> Peter Müller
>
>
>> Hi,
>> once again - all of a sudden - while working at it...:
>> ...
>> root(a)Devel32: /home/matz/ipfire-2.x # git pull origin next
>> ssh: connect to host git.ipfire.org port 22: Cannot assign requested address
>> fatal: Could not read from remote repository.
>> Please make sure you have the correct access rights
>> and the repository exists.
>> ...
>> Could someone please give the "security system" a kick from me?
>> Best,
>> Matthias
next prev parent reply other threads:[~2021-01-30 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 11:58 Matthias Fischer
2021-01-30 12:06 ` Peter Müller
2021-01-30 12:15 ` Michael Tremer [this message]
2021-01-30 12:36 ` Matthias Fischer
2021-01-30 12:39 ` Matthias Fischer
2021-01-30 12:22 ` Matthias Fischer
2021-01-30 17:15 ` Matthias Fischer
2021-01-30 17:37 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B261B4-18CD-448F-9D0D-7707189A8DA4@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox