From: "taylor, david" <david.taylor@emc.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: "tromey@redhat.com" <tromey@redhat.com>,
"overseers@sourceware.org" <overseers@sourceware.org>
Subject: RE: access to binutils-gdb.git
Date: Wed, 20 Jan 2016 15:35:00 -0000 [thread overview]
Message-ID: <63F1AEE13FAE864586D589C671A6E18B0209D5@MX203CL03.corp.emc.com> (raw)
In-Reply-To: <20160120150737.GP51204@elastic.org>
Hello Frank.
[BTW, Tom's address bounced for me.]
Sadly, I do not know the outgoing address. My desktop has a private address.
I don't know what it shows up as externally. And the last machine shown by
traceroute before sourceware.org has a 10.x.y.z address with no name.
IT blocks git but not http. I first tried git and it failed. Then I tried http and it worked
-- for months. It was working when I left for vacation in December (use it or lose it
vacation policy). Now, January it doesn't work. At first I blamed EMC IT.
I can connect to http://sourceware.org just fine. And even http://sourceware.org/git/ .
But, when I try to connect to http://sourceware.org/git/binutils-gdb.git, I have problems.
Does the blacklist make the distinction? Does the git port not have a blacklist?
I have asked IT about the possibility of using the git port instead of the http port.
No answer as yet.
-----Original Message-----
From: Frank Ch. Eigler [mailto:fche@elastic.org]
Sent: Wednesday, January 20, 2016 10:08 AM
To: taylor, david
Cc: tromey@redhat.com; overseers@sourceware.org
Subject: Re: access to binutils-gdb.git
Hi, David -
> [...] For months I updated a local clone of the binutils-gdb
> repository using the http protocol. And it worked. Recently it
> stopped working. [...] Forbidden You don't have permission to access
> /git/binutils-gdb.git/ on this server. [...]
I guess you don't have access to git: or ssh: instead?
We blacklist some IP address ranges due to a history of abuse. Do you have any idea what the outgoing address of your connections might be?
- FChE
next prev parent reply other threads:[~2016-01-20 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 14:56 taylor, david
2016-01-20 15:07 ` Frank Ch. Eigler
2016-01-20 15:35 ` taylor, david [this message]
2016-04-11 15:43 Access " taylor, david
2016-04-11 15:51 ` Frank Ch. Eigler
2016-04-11 16:07 taylor, david
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=63F1AEE13FAE864586D589C671A6E18B0209D5@MX203CL03.corp.emc.com \
--to=david.taylor@emc.com \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=tromey@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).