From: "Frank Ch. Eigler" <fche@elastic.org>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Cc: Overseers mailing list <overseers@sourceware.org>, hjl.tools@gmail.com
Subject: Re: Request from Vladimir Mezentsev
Date: Thu, 7 Apr 2022 20:24:34 -0400 [thread overview]
Message-ID: <Yk+AwkbVg0jPIGXo@elastic.org> (raw)
In-Reply-To: <4e82eea2-8714-5563-e394-86d46bd31cc7@oracle.com>
Hi -
> 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
Wild.
> Now:
> % git push sourceware vmezents/zlib:master
> vmezentsev@sourceware.org: Permission denied (publickey).
> fatal: Could not read from remote repository.
Your userid at sourceware is: vmezents .
> Maybe my publickey doesn't match.
Yes, that needs to match. And according to this:
> > Try % traceroute sourceware.org
> > Try % ssh -v vmezents@sourceware.org
> [...]
> 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.
> [...]
... it does now, so that's fine.
- FChE
next prev parent reply other threads:[~2022-04-08 0:24 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
2022-04-08 0:24 ` Frank Ch. Eigler [this message]
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=Yk+AwkbVg0jPIGXo@elastic.org \
--to=fche@elastic.org \
--cc=hjl.tools@gmail.com \
--cc=overseers@sourceware.org \
--cc=vladimir.mezentsev@oracle.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).