unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Roy <yeupou@gnu.org>
Cc: gnu-arch-users@gnu.org, savannah-hackers@gnu.org,
	xouvert-general@nongnu.org, emacs-devel@gnu.org
Subject: Re: possible fix for sftp on Savannah; please try
Date: 14 Oct 2003 12:06:53 +0200	[thread overview]
Message-ID: <m3brsk9lqa.fsf@dionysos.nib> (raw)
In-Reply-To: <20031013224138.GA21254@reactor-core.org>

Jonathan Walther <krooger@debian.org> said:

> On Mon, Oct 06, 2003 at 10:38:37PM +0200, Mathieu Roy wrote:
> >> The errors always mention premature EOF on file descriptor 4.
> >> If you could install chroot-sftp.c, that would be a tremendous help
> >> in
> >> tracking down the problem.
> >
> >Firstly, I would to know why the current thing does not work for you
> >while it works for me and while I was told by several others persons,
> >including arch users, that it works ok.
> 
> When did you last test it?

The last time its configuration was changed.

> I finally got a regular Savannah user account, and talked to other
> regular Savannah users, and unless they use ssh protocol 1, which
> you CANNOT chroot,

We chroot it and it works chrooted.


Since you apparently do not believe me when I say that, please look at
the following:


moa@dionysos:~$ sftp -1 svtest@sv.gnu.org:/
Connecting to sv.gnu.org...
Enter passphrase for RSA key '/home/moa/.ssh/id_rsa1': 
Changing to: /
sftp> ls
.
..
123tkshop
7pages
9box
Andrew-Toolkit.README
Flush
FreelyAvailableTexts
Only
README
README.obst
Socket
[...]
sftp> ls /usr/bin
/usr/bin/.
/usr/bin/..
/usr/bin/sftp

It definitely works.



> The shell closes all file descriptors except 0, 1, and 2 before passing
> them on to programs.  The sftp server expects to by invoked by sshd, not
> by a shell script, and so it is waiting for incoming data on file
> descriptor 4.

This account is an usual account.

You requested a special account in order to help us but apparently you
always refers to specific issues related to this non-usual account.

The last time I was on IRC for almost one hour with people from your
project and I left only when it was said it was working. The
configuration did not changed. 

So please, can we have the error messages you get, with an usual
account?
(didn't asked for that information before?)
We are not about to fix something unless we have some clue about
reproducibility of the problem, unless we are able to confirm that
there is really a problem on the server side.






-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english

  reply	other threads:[~2003-10-14 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031006112435.GA11164@reactor-core.org>
     [not found] ` <m3u16mv9dn.fsf@dionysos.nib>
     [not found]   ` <20031006193845.GA20395@reactor-core.org>
     [not found]     ` <m365j2t836.fsf@dionysos.nib>
2003-10-13 22:41       ` possible fix for sftp on Savannah; please try Jonathan Walther
2003-10-14 10:06         ` Mathieu Roy [this message]
2003-10-14 11:14         ` Andreas Schwab

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3brsk9lqa.fsf@dionysos.nib \
    --to=yeupou@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gnu-arch-users@gnu.org \
    --cc=savannah-hackers@gnu.org \
    --cc=xouvert-general@nongnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).