* "svn up" over ssh does not work
@ 2018-01-27 12:11 Thomas Koenig
2018-01-28 10:58 ` Andreas Schwab
2018-01-28 12:43 ` Jonathan Wakely
0 siblings, 2 replies; 7+ messages in thread
From: Thomas Koenig @ 2018-01-27 12:11 UTC (permalink / raw)
To: fortran, gcc mailing list
Hi,
I am getting
$ LANG=C svn up
Updating '.':
svn: E170013: Unable to connect to a repository at URL
'svn+ssh://tkoenig@gcc.gnu.org/svn/gcc/trunk'
svn: E210002: To better debug SSH connection problems, remove the -q
option from 'ssh' in the [tunnels] section of your Subversion
configuration file.
svn: E210002: Network connection closed unexpectedly
read-only svn (without ssh) works.
Anything wrong with the servers?
Regards
Thomas
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "svn up" over ssh does not work
2018-01-27 12:11 "svn up" over ssh does not work Thomas Koenig
@ 2018-01-28 10:58 ` Andreas Schwab
2018-01-28 11:00 ` Thomas Koenig
2018-01-28 12:43 ` Jonathan Wakely
1 sibling, 1 reply; 7+ messages in thread
From: Andreas Schwab @ 2018-01-28 10:58 UTC (permalink / raw)
To: Thomas Koenig; +Cc: fortran, gcc mailing list
On Jan 27 2018, Thomas Koenig <tkoenig@netcologne.de> wrote:
> svn: E210002: To better debug SSH connection problems, remove the -q
> option from 'ssh' in the [tunnels] section of your Subversion
> configuration file.
And what does it say?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "svn up" over ssh does not work
2018-01-28 10:58 ` Andreas Schwab
@ 2018-01-28 11:00 ` Thomas Koenig
2018-01-28 11:26 ` Andreas Schwab
0 siblings, 1 reply; 7+ messages in thread
From: Thomas Koenig @ 2018-01-28 11:00 UTC (permalink / raw)
To: Andreas Schwab; +Cc: fortran, gcc mailing list
Am 28.01.2018 um 11:58 schrieb Andreas Schwab:
> On Jan 27 2018, Thomas Koenig <tkoenig@netcologne.de> wrote:
>
>> svn: E210002: To better debug SSH connection problems, remove the -q
>> option from 'ssh' in the [tunnels] section of your Subversion
>> configuration file.
>
> And what does it say?
>
> Andreas.
Nothing, but replacing it with "-v" yielded
OpenSSH_7.6p1, OpenSSL 1.0.2n-fips 7 Dec 2017
debug1: Reading configuration data /home/ig25/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 25: Applying options for *
debug1: Connecting to gcc.gnu.org [209.132.180.131] port 22.
debug1: Connection established.
debug1: identity file /home/ig25/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/ig25/.ssh/id_rsa-cert type -1
debug1: identity file /home/ig25/.ssh/id_dsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ig25/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ig25/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ig25/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ig25/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ig25/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000
debug1: Authenticating to gcc.gnu.org:22 as 'tkoenig'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: umac-64@openssh.com
compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: umac-64@openssh.com
compression: none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<3072<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa
SHA256:MFNiczzfX8/nvLSRZwR3CxMyycKtMan64Zm4C373FeM
debug1: Host 'gcc.gnu.org' is known and matches the RSA host key.
debug1: Found key in /home/ig25/.ssh/known_hosts:12
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 4294967296 blocks
debug1: Skipping ssh-dss key /home/ig25/.ssh/id_dsa - not in
PubkeyAcceptedKeyTypes
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: RSA
SHA256:wxYM1dVeitcO4H9nq0GL/nIHnlVerL/znSPjkapg9/s /home/ig25/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/ig25/.ssh/id_ecdsa
debug1: Trying private key: /home/ig25/.ssh/id_ed25519
debug1: No more authentication methods to try.
tkoenig@gcc.gnu.org: Permission denied (publickey).
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "svn up" over ssh does not work
2018-01-28 11:00 ` Thomas Koenig
@ 2018-01-28 11:26 ` Andreas Schwab
0 siblings, 0 replies; 7+ messages in thread
From: Andreas Schwab @ 2018-01-28 11:26 UTC (permalink / raw)
To: Thomas Koenig; +Cc: fortran, gcc mailing list
On Jan 28 2018, Thomas Koenig <tkoenig@netcologne.de> wrote:
> debug1: Offering public key: RSA
> SHA256:wxYM1dVeitcO4H9nq0GL/nIHnlVerL/znSPjkapg9/s /home/ig25/.ssh/id_rsa
That's your new key, of course it won't work. What does it say if you
use your old new?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "svn up" over ssh does not work
2018-01-27 12:11 "svn up" over ssh does not work Thomas Koenig
2018-01-28 10:58 ` Andreas Schwab
@ 2018-01-28 12:43 ` Jonathan Wakely
2018-01-28 13:01 ` Andreas Schwab
2018-01-28 13:04 ` Thomas Koenig
1 sibling, 2 replies; 7+ messages in thread
From: Jonathan Wakely @ 2018-01-28 12:43 UTC (permalink / raw)
To: Thomas Koenig; +Cc: fortran, gcc mailing list
On 27 January 2018 at 12:11, Thomas Koenig wrote:
> Hi,
>
> I am getting
>
> $ LANG=C svn up
> Updating '.':
> svn: E170013: Unable to connect to a repository at URL
> 'svn+ssh://tkoenig@gcc.gnu.org/svn/gcc/trunk'
> svn: E210002: To better debug SSH connection problems, remove the -q option
> from 'ssh' in the [tunnels] section of your Subversion configuration file.
> svn: E210002: Network connection closed unexpectedly
>
> read-only svn (without ssh) works.
>
> Anything wrong with the servers?
No, the problem must be at your end. Did you recently update your
OpenSSH version?
Does your local config now disable DSA keys by default, and your key
on gcc.gnu.org is a DSA key?
i.e. does this work?
SVN_SSH="ssh -o PubkeyAcceptedKeyTypes=ssh-dss" svn up
If it does then edit your ~/.ssh/config to add that option for Host gcc.gnu.org
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2018-01-28 13:04 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-27 12:11 "svn up" over ssh does not work Thomas Koenig
2018-01-28 10:58 ` Andreas Schwab
2018-01-28 11:00 ` Thomas Koenig
2018-01-28 11:26 ` Andreas Schwab
2018-01-28 12:43 ` Jonathan Wakely
2018-01-28 13:01 ` Andreas Schwab
2018-01-28 13:04 ` Thomas Koenig
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).