From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>, hjl.tools@gmail.com
Subject: Re: Request from Vladimir Mezentsev
Date: Thu, 7 Apr 2022 14:31:19 -0700 [thread overview]
Message-ID: <4e82eea2-8714-5563-e394-86d46bd31cc7@oracle.com> (raw)
In-Reply-To: <Yk85xSBNPdEno3CC@elastic.org>
On 4/7/22 12:21, Frank Ch. Eigler wrote:
> Hi -
>
>>> Your machine may have triggered some temporary auto-blocking.
> (I can find no indication of this in the logs.)
>
>>> What's your external IP address?
>> I am inside Oracle.
>> I think 206.223.27.1 is my external IP address :
> Try https://whatismyipaddress.com/
My external IP is:
IPv4: 148.87.23.10
>
>> % git push sourceware vmezents/zlib:master
>> ssh: connect to host sourceware.org port 22: Network is unreachable
>> fatal: Could not read from remote repository.
I probably solved one problem by adding to .ssh/config:
Host sourceware.org
HostName sourceware.org
User vmezents
ProxyCommand=/usr/bin/socat -
PROXY:www-proxy.us.oracle.com:%h:%p,proxyport=80
Now:
% git push sourceware vmezents/zlib:master
vmezentsev@sourceware.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Maybe my publickey doesn't match.
> Try % traceroute sourceware.org
% traceroute sourceware.org
traceroute to sourceware.org (8.43.85.97), 30 hops max, 60 byte packets
1 sca-c1-303.us.oracle.com (10.133.144.1) 0.423 ms 0.481 ms 0.608 ms
2 santaclara12-syslab-rtr-te5-5.us.oracle.com (10.134.254.129) 0.572
ms 0.623 ms 0.745 ms
3 sca15-core-rtr-1-t1-17.us.oracle.com (10.132.6.81) 0.937 ms
sca12-core-rtr-1-t1-17.us.oracle.com (10.132.6.65) 1.067 ms 1.281 ms
4 * * *
5 * * *
6 * * *
7 sca15-core-rtr-1-t1-17.us.oracle.com (10.132.6.81) 2.939 ms !H * *
> Try % ssh -v vmezents@sourceware.org
% ssh -v vmezents@sourceware.org
OpenSSH_8.0p1, OpenSSL 1.1.1g FIPS 21 Apr 2020
debug1: Reading configuration data /home/vmezents/.ssh/config
debug1: /home/vmezents/.ssh/config line 14: Applying options for
sourceware.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data
/etc/crypto-policies/back-ends/openssh.config
debug1: configuration requests final Match pass
debug1: re-parsing configuration
debug1: Reading configuration data /home/vmezents/.ssh/config
debug1: /home/vmezents/.ssh/config line 14: Applying options for
sourceware.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf
debug1: Reading configuration data
/etc/crypto-policies/back-ends/openssh.config
debug1: Executing proxy command: exec /usr/bin/socat -
PROXY:www-proxy.us.oracle.com:sourceware.org:22,proxyport=80
debug1: identity file /home/vmezents/.ssh/id_rsa type 0
debug1: identity file /home/vmezents/.ssh/id_rsa-cert type -1
debug1: identity file /home/vmezents/.ssh/id_dsa type 1
debug1: identity file /home/vmezents/.ssh/id_dsa-cert type -1
debug1: identity file /home/vmezents/.ssh/id_ecdsa type -1
debug1: identity file /home/vmezents/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/vmezents/.ssh/id_ed25519 type -1
debug1: identity file /home/vmezents/.ssh/id_ed25519-cert type -1
debug1: identity file /home/vmezents/.ssh/id_xmss type -1
debug1: identity file /home/vmezents/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.0
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0
debug1: match: OpenSSH_8.0 pat OpenSSH* compat 0x04000000
debug1: Authenticating to sourceware.org:22 as 'vmezents'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: aes256-gcm@openssh.com MAC:
<implicit> compression: none
debug1: kex: client->server cipher: aes256-gcm@openssh.com MAC:
<implicit> compression: none
debug1: kex: curve25519-sha256 need=32 dh_need=32
debug1: kex: curve25519-sha256 need=32 dh_need=32
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:4bqfulMjMg7/L/38MJBw7mVMMu6EH+3MgMitrCRdFho
debug1: Host 'sourceware.org' is known and matches the ECDSA host key.
debug1: Found key in /home/vmezents/.ssh/known_hosts:208
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: Skipping ssh-dss key /home/vmezents/.ssh/id_dsa - not in
PubkeyAcceptedKeyTypes
debug1: Will attempt key: /home/vmezents/.ssh/id_rsa RSA
SHA256:bw6vxQiV7MXSyPhNnS1PuKZERTjYjYpVZUX/PLwENaE agent
debug1: Will attempt key: /home/vmezents/.ssh/id_ecdsa
debug1: Will attempt key: /home/vmezents/.ssh/id_ed25519
debug1: Will attempt key: /home/vmezents/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info:
server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/vmezents/.ssh/id_rsa RSA
SHA256:bw6vxQiV7MXSyPhNnS1PuKZERTjYjYpVZUX/PLwENaE agent
debug1: Server accepts key: /home/vmezents/.ssh/id_rsa RSA
SHA256:bw6vxQiV7MXSyPhNnS1PuKZERTjYjYpVZUX/PLwENaE agent
debug1: Authentication succeeded (publickey).
Authenticated to sourceware.org (via proxy).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: proc
debug1: client_input_global_request: rtype hostkeys-00@openssh.com
want_reply 0
debug1: Remote: /home/vmezents/.ssh/authorized_keys:1: key options: user-rc
debug1: Remote: /home/vmezents/.ssh/authorized_keys:1: key options: user-rc
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending env XMODIFIERS = @im=ibus
PTY allocation request failed on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to sourceware.org closed.
Transferred: sent 3160, received 2648 bytes, in 10.4 seconds
Bytes per second: sent 304.5, received 255.2
debug1: Exit status 1
>
> Can you ssh to other external sites directly from your workstation?
I did this long time ago to gcc116.fsffrance.org
Thank you,
-Vladimir
>
> - FChE
next prev parent reply other threads:[~2022-04-07 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 18:58 vladimir.mezentsev
2022-03-22 19:18 ` H.J. Lu
2022-03-23 0:38 ` Christopher Faylor
2022-04-05 21:03 ` Vladimir Mezentsev
2022-04-05 23:00 ` Christopher Faylor
2022-04-05 23:22 ` Vladimir Mezentsev
2022-04-06 19:37 ` Frank Ch. Eigler
2022-04-07 17:59 ` Vladimir Mezentsev
2022-04-07 18:02 ` Frank Ch. Eigler
2022-04-07 19:13 ` Vladimir Mezentsev
2022-04-07 19:21 ` Frank Ch. Eigler
2022-04-07 21:31 ` Vladimir Mezentsev [this message]
2022-04-08 0:24 ` Frank Ch. Eigler
2022-04-08 16:17 ` Vladimir Mezentsev
-- strict thread matches above, loose matches on Subject: below --
2018-05-23 21:44 vladimir.mezentsev
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=4e82eea2-8714-5563-e394-86d46bd31cc7@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=fche@elastic.org \
--cc=hjl.tools@gmail.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).