On Mon, Feb 01, 1999 at 06:46:49PM +, Julian Gilbey wrote:
> > > > nonus.debian.org 23780 nonus.debian.org: libssl-dev is obsolete [220]
> > > > (Heiko Schlittermann <[EMAIL PROTECTED]>)
> > ...
> > > Will non-us ever be fixed?
> >
> > It is but I'm afraid the bugs have not been closed. Hei
> > > nonus.debian.org 23780 nonus.debian.org: libssl-dev is obsolete [220]
> > > (Heiko Schlittermann <[EMAIL PROTECTED]>)
> ...
> > Will non-us ever be fixed?
>
> It is but I'm afraid the bugs have not been closed. Heiko seems really
> overloaded (and does not reply a lot even on other subje
> > Hmmm... If things were installed by hand ("dpkg --install dpkglib...")
> > or if install were to fail between the two packages, then you could have
> > a problem where the install tool doesn't function, right?
>
> Right. But since libdpkg is still a part of the dpkg package we
> shouldn't nee
On Sunday 31 January 1999, at 0 h 48, the keyboard of Michael Stone
<[EMAIL PROTECTED]> wrote:
> > boot-floppies 32269 partion harddisk fails if WIN95_EXTENDED present
> > [0] (Enrique Zanardi )
>
> The report log is a little unclear. It looks like there is a version of cfdisk
> that work
Previously Brian White wrote:
> Hmmm... If things were installed by hand ("dpkg --install dpkglib...")
> or if install were to fail between the two packages, then you could have
> a problem where the install tool doesn't function, right?
Right. But since libdpkg is still a part of the dpkg packag
Previously Jonel Rienton wrote:
> Slink's latest lprng is broken, it's give me a problem about permission or
> something'.
Vincent already uploaded a fix for that.
Wichert.
--
==
This combination of bytes forms a messa
On Mon, Feb 01, 1999 at 12:05:27PM +0100, Richard Braakman wrote:
> Joey Hess wrote:
> > Wichert Akkerman wrote:
> > > > general 28850 gettext: security problem when used in setuid
> > > > programs [0] (debian-devel@lists.debian.org)
> > >
> > > Everyone who has a package with a setuid
Joey Hess wrote:
> Wichert Akkerman wrote:
> > > general 28850 gettext: security problem when used in setuid
> > > programs [0] (debian-devel@lists.debian.org)
> >
> > Everyone who has a package with a setuid program or something that runs
> > as root should check if it uses gettext,
Wichert Akkerman wrote:
> > general 28850 gettext: security problem when used in setuid
> > programs [0] (debian-devel@lists.debian.org)
>
> Everyone who has a package with a setuid program or something that runs
> as root should check if it uses gettext, and if so recompile it with
>
Slink's latest lprng is broken, it's give me a problem about permission or
something'.
On Sun, Jan 31, 1999 at 10:10:25PM -0500, Brian White wrote:
> I understand. My point, however, was that anyone who exports those things
> on purpose could just as easily copy the file, ftp it, email it, or
> whatever. Plugging a whole in the side of a boat doesn't help when the
> boat has no bot
> > > Previously Brian White wrote:
> > > > apache32204 user directories allow symlinks to other files
> > > > [0] (Johnie Ingram <[EMAIL PROTECTED]>)
> > >
> > > We should just force SymLinksIfOwnerMatch for /home to solve this.
> >
> > You know, I don't see this as "grave". It mea
> > You know, I don't see this as "grave". It means that a user can
> > effectively "export to the world" any file readable by www-data. In
> > general, this means only things that can be read by public. So,
> > the user can't intentionally export anything that he/she couldn't already
> > do by
On Sun, Jan 31, 1999 at 02:20:00PM -0500, Brian White wrote:
> > Previously Brian White wrote:
> > > apache32204 user directories allow symlinks to other files
> > > [0] (Johnie Ingram <[EMAIL PROTECTED]>)
> >
> > We should just force SymLinksIfOwnerMatch for /home to solve this.
>
>
14 matches
Mail list logo