unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan <monnier@iro.umontreal.ca>
Cc: nickrob@snap.net.nz, spiegel@gnu.org, emacs-devel@gnu.org
Subject: Re: vc-version-other-window
Date: Sun, 10 Oct 2004 15:38:11 -0400	[thread overview]
Message-ID: <m1hdp2l6jq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1CGV4N-0003wa-W8@fencepost.gnu.org> (Richard Stallman's message of "Sun, 10 Oct 2004 00:12:27 -0400")

>> Would it be useful to release a patched version of OpenSSH?
>     And what happens when they release a newer (unpatched) version one month
>     later with some security fix?  Forking like that is not really an option
>     I think.

> We can certainly handle that.  We need someone reliable to do a small
> amount of work occasionally when needed.

But to be useful, we need to convince distributions to that fork
of OpenSSH.  That just doesn't seem practical.

>     What is needed is for the glibc, cvs, and openssh people to stop
>     finger-pointing and to work together at coming up with a fix.

> However, if someone send them a fix, and it has no practical costs, they
> might install it.  Are you in touch with the relevant people; could you
> ask them to try to do this?  Have they already done this?

As far as I know, the problem can be fixed at various places.  Within CVS
it's inconvenient because it requires something similar to the cvs-ssh
wrapper (but there were noises on the info-cvs list that they were maybe
going to implement such a workaround anyway).  IIRC it can be fixed in the
libc as well (IIRC the problem there is to make sure that `fwrite' on
a non-blocking file descriptor works reliably).


        Stefan

  reply	other threads:[~2004-10-10 19:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 11:21 vc-version-other-window Nick Roberts
2004-10-06 13:05 ` vc-version-other-window Stefan Monnier
2004-10-07 16:44   ` vc-version-other-window Richard Stallman
2004-10-07 17:25     ` vc-version-other-window Stefan Monnier
2004-10-07 22:51       ` vc-version-other-window Kim F. Storm
2004-10-09  1:25       ` vc-version-other-window Richard Stallman
2004-10-09  1:25       ` vc-version-other-window Richard Stallman
2004-10-09  4:20         ` vc-version-other-window Stefan
2004-10-10  4:12           ` vc-version-other-window Richard Stallman
2004-10-10 19:38             ` Stefan [this message]
2004-10-11 16:45               ` vc-version-other-window Richard Stallman
2004-10-11 17:38               ` vc-version-other-window Simon Josefsson
2004-10-12  2:16                 ` vc-version-other-window Miles Bader
2004-10-12  8:57                 ` vc-version-other-window Richard Stallman

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=m1hdp2l6jq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=spiegel@gnu.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).