[lkml]   [2000]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Fwd: NTFS repair tools]

"Michael H. Warfield" wrote:

> > Agree. We need to disable it, since folks do not read the docs
> > (obviously). Of course, we could leave it on, and I could start
> > charging money for these tools -- there's little doubt it would be a
> > lucrative business. Perhaps this is what I'll do if the numbers of
> > copies keeps growing. When it hits > 100 per week, it's taking a lot of
> > our time to support, so I will have to start charging for it.
> Huh?
> How disabled do you want it. It can't even be enabled unless
> you enabled experimental code options. Then, it's disabled by default
> and you first have to enable the R/O NTFS. Then you have to explicitly
> select the option to enable RW access that is clearly labeled DANGEROUS.
> This thing is not armed and dangerous due to an act of ommision. It's
> live and active only through three acts of commision.
> About the only thing left, short of removing it from the kernel
> entirely, is to make the option a hidden control option, like some of the
> debugging options, that requires editing a header file or a Makefile to
> enable. Is that what you are looking for?

Linux today monitors this list. Some public education may be the best
route. How do we post a security advisory warning people that will get
posted? I'm sure folks see the DANGEROUS comments, but they don't seem
to stick in their heads. Then they get themselves into trouble, and
fortunately for them, I'm around. I am just concerned about the scope
of the black eye that will just keep getting bigger and bigger for Linux


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:51    [W:0.105 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site