Note: I don't read -user, just -devel, so I just saw this thread. I
apologize for duplication, if someone already said things I'm going to say
in my message.
Kurt Seifried wrote:
> >Basically, you are forking development. There is now a version to be
> >found in all the standard places where you
[Sorry for the late jump in, I found this thread because of Seth's X-Post]
Hi Oliver!
On Thu, 31 Aug 2000, Oliver Elphick wrote:
> "Kurt Seifried" wrote:
> ...
> >Problem: user can enter Lilo commands at the Lilo prompt
> ...
> >Additional solution: remove/replace password in lilo.conf after
Please follow up to Debian-devel, since this isn't really a user issue.
[please ignore the long quoted sections. I decided it ws better to quote
in full, since I was crossposting this]
At 04:34 PM 09/15/2000 -0700, David Benfell wrote:
On Thu, Aug 31, 2000 at 10:20:44AM -0400, Paul D. Smith w
On Thu, Aug 31, 2000 at 10:20:44AM -0400, Paul D. Smith wrote:
>
> %% Kurt Seifried <[EMAIL PROTECTED]> writes:
>
> ks> One question: where is it explicitly stated that Debian backports
> ks> fixes and that one needs to read /usr/doc/*/changelog?
>
> I'll answer this on two levels:
>
> Firs
John Hasler wrote:
> Paul D. Smith writes:
> > For the second, it's fine for me for small editing jobs;
>
> I find it frustrating for anything.
>
> > I do the work in my editor and paste the results into the window.
>
> I hadn't tried that. I'd rather just download the file, edit it, and then
>
Paul D. Smith writes:
> For the second, it's fine for me for small editing jobs;
I find it frustrating for anything.
> I do the work in my editor and paste the results into the window.
I hadn't tried that. I'd rather just download the file, edit it, and then
upload it.
--
John Hasler
[EMAIL PR
%% John Hasler <[EMAIL PROTECTED]> writes:
jh> Paul D. Smith writes:
>> What kinds of problems are you seeing?
jh> I find the Web interface (the only one available to me as a section
jh> adminstrator) just about completely unusable for editing.
You mean the page with all the buttons for
On Thu, 31 Aug 2000, Kurt Seifried wrote:
> [snip] ... people view security as a number of small unrelated
> problems, when in fact you have to treat it as an entire, complex,
> system.
I agree. I also think that good security needs to involve research. I
think it's Debian's responsibility to p
"Kurt Seifried" wrote:
...
>Problem: user can enter Lilo commands at the Lilo prompt
...
>Additional solution: remove/replace password in lilo.conf after setting it
>(i.e. set password, run lilo, remove password).
You may not have noticed mbr:
bash-2.04$ dpkg --status mbr
Package: mbr
Status
On Thu, Aug 31, 2000 at 10:03:59AM -0600, Kurt Seifried wrote:
> So did you fix the root hack in pre10, the DOS in rc1, or the typo in the
> install script? Oh yeah, I gotta read the changelog to find out,
> wheep.
Well, you're going to have to read it somewhere, yes? And now you know where!
> A
Paul D. Smith writes:
> What kinds of problems are you seeing?
I find the Web interface (the only one available to me as a section
adminstrator) just about completely unusable for editing.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
> OK, 2 to 5 minutes downtime to disable. Big Whoop. Maybe should be
> done. But, have you ever tried to administer 200 computers? How many
> people know the BIOS password? Do the primary users know it? Can they
> reboot their own machine? Does an administrator have to visit every
> machine
On Thu, Aug 31, 2000 at 10:26:20AM -0600, Kurt Seifried wrote:
> BTW Idon't know if anyone actually "got it" but the point of my article was
> more that Debian is trying to improve security, but seems to be missing
> major things. I suppose I should have stated this more obviously (like in H1
> at
BTW Idon't know if anyone actually "got it" but the point of my article was
more that Debian is trying to improve security, but seems to be missing
major things. I suppose I should have stated this more obviously (like in H1
at the top). Sigh, anyways for next time I will be less subtle. Bruce
Schn
On Thu, Aug 31, 2000 at 10:03:59AM -0600, Kurt Seifried wrote:
> > Personally, when I see "1.2.0pre10-4", I think, "This is not the same as
> the
> > original/base 1.2.0pre10." Depending on how the numbering is implemented,
> it
> > has been updated 3 or 4 times since the original 1.2.0pre10. So
> Personally, when I see "1.2.0pre10-4", I think, "This is not the same as
the
> original/base 1.2.0pre10." Depending on how the numbering is implemented,
it
> has been updated 3 or 4 times since the original 1.2.0pre10. So I would
not
> expect it to have the same bugs.
So did you fix the root h
Kurt Seifried said:
> Debian ProFTPD 1.2.0pre10 revision 3 has the root hack mentioned above
> however fixed in 1.2.0pre10revision 4, revision 5 also fixes some of the
> problems that were possible in rc1
Personally, when I see "1.2.0pre10-4", I think, "This is not the same as the
original/base 1.
%% John Hasler <[EMAIL PROTECTED]> writes:
jh> Paul D. Smith writes:
>> IMHO, FAQ-O-Matic is a _very cool_ tool...
jh> But a real PITA to administer.
Hmm. Well, we use a pretty large FOM internally at work here, and I
haven't noticed that it's a _huge_ PITA :). Mostly seems pretty
self-
On Thu, Aug 31, 2000 at 07:18:18AM -0600, Kurt Seifried wrote:
> > Yes I read the update. I'd be happy to review your articles for you, but I
> > don't think you should stop at one reviewer. Debian is a very big project
> and I'm
> > still finding my way around parts of it. You may have been in con
Paul D. Smith writes:
> IMHO, FAQ-O-Matic is a _very cool_ tool...
But a real PITA to administer.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
%% Kurt Seifried <[EMAIL PROTECTED]> writes:
ks> One question: where is it explicitly stated that Debian backports
ks> fixes and that one needs to read /usr/doc/*/changelog?
I'll answer this on two levels:
First, if you're writing an article on a subject for publication it
behooves you to fi
> Yes I read the update. I'd be happy to review your articles for you, but I
> don't think you should stop at one reviewer. Debian is a very big project
and I'm
> still finding my way around parts of it. You may have been in contact with
Ben
> Collins. If so I suggest you ask him too.
Yeah, he did
22 matches
Mail list logo
