Revert "clean P2P protocol shutdown on EOF"

This reverts commit b18fb1e343.

That broke support for old git-annex-shell before p2pstdio was added.

The immediate problem is that postAuth had a fallthrough case
that sent an error back to the peer, but sending an error back when the
connection is closed is surely not going to work.

But thinking about it some more, making every function that uses receiveMessage
need to handle ProtocolEOF adds a lot of complication, so I don't want
to do that.

The commit only cleaned up the test suite output a tiny bit, so I'm just
gonna revert it for now.
This commit is contained in:
Joey Hess 2018-09-25 14:04:12 -04:00
parent 26a02cb386
commit 16cbecbd09
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
6 changed files with 24 additions and 17 deletions

View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-09-25T17:18:14Z"
content="""
Ok, reproduced by downgrading git-annex, so it is a reversion in the
fallback from p2pstdio.
"""]]

View file

@ -64,3 +64,5 @@ so ssh connection seems to be ok
what could it be?
[[!meta author=yoh]]
> [[fixed|done]] --[[Joey]]

View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-09-25T17:18:14Z"
content="""
Ok, reproduced by downgrading git-annex, so it is a reversion in the
fallback from p2pstdio.
It is indeed caused by [[!commit b18fb1e343e9654207fbebacf686659c75d0fb4c]],
because that adds a new ProtocolEOF value, and postAuth has a fallthrough
case that tries to then send a ERROR message back over the connection, but
by that time the pipe has closed.
So that was an easy fix. I do still wonder how a system that displays
/etc/issue or whatever to noninteractive logins could have ever worked with
rsync or git-annex. But if that system doesn't work after this fix, it's an
unrelated problem.
"""]]