mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Kai Makisara <Kai.Makisara@kolumbus.fi>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make st seekable again
Date: Thu, 10 Mar 2005 18:13:53 +0100	[thread overview]
Message-ID: <1110474834.6291.114.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1050310114027.11549B-100000@gatekeeper.tmr.com>

On Thu, 2005-03-10 at 11:56 -0500, Bill Davidsen wrote:
> On Thu, 10 Mar 2005, Arjan van de Ven wrote:
> 
> > >  critical user data.
> > > 
> > > In other words, it should work correctly or not at all. At the least this
> > > should be a config option, like UNSAFE_TAPE_POSITIONING or some such.
> > > And show the option if the build includes BROKEN features. That should put
> > > the decision where it belongs and clarify the possible failures.
> > 
> > CONFIG_SECURITY_HOLES doesn't make sense.
> > Better to just fix the security holes instead.
> 
> I think you're an idealist. If this were something other than tar it would
> be simple, and you would be right. Well, you ARE right, but a change which
> breaks tar, which many sites use for backups, is really not practical,
> without a loophole until tar gets fixed. And as Alan noted, keeping track
> of the physical position is very hard, and getting a tar fix might take a
> while.
> 

No the problem is that the *st* code has a security hole. THAT is the
problem. Not that it would be seekable. But how it implements the seeks.
THAT part is the problem. And THAT can be fixed. 


  reply	other threads:[~2005-03-10 17:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200503081911.j28JBlxi016013@hera.kernel.org>
2005-03-09 20:51 ` Alan Cox
2005-03-09 21:58   ` Kai Makisara
2005-03-09 22:27     ` Alan Cox
2005-03-10 11:49       ` Bill Davidsen
2005-03-10 12:10         ` Arjan van de Ven
2005-03-10 16:43           ` Alan Cox
2005-03-10 16:56           ` Bill Davidsen
2005-03-10 17:13             ` Arjan van de Ven [this message]
2005-03-10 17:58             ` Alan Cox
     [not found] <fa.i3f7d9s.30m8rg@ifi.uio.no>
     [not found] ` <fa.l4kuq52.e6001g@ifi.uio.no>
2005-03-10  0:43   ` Bodo Eggert
2005-03-10 20:01     ` Willy Tarreau

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=1110474834.6291.114.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®