On 2010/10/01 22:50, Jakob Schlyter wrote:
> The following patches makes establish the following default NSD
> permissions/locations:
>
> - /var/nsd/db for stuff that nsd(8) may write to (as user/group _nsd)
> - /var/nsd/nsd.db for the read-only database.
> - /var/nsd/zones default zone directory.
On 2 okt 2010, at 13.48, Stuart Henderson wrote:
> I think it makes sense to do have a separate user for these, that's how
> I've been running nsd in the past.
did you make nsd-{patch,zonec} drop privs to that user, or did you start them
as the user?
where did you put nsd.db? I guess a subdir of
On 2010/10/02 15:06, Jakob Schlyter wrote:
> On 2 okt 2010, at 13.48, Stuart Henderson wrote:
>
> > I think it makes sense to do have a separate user for these, that's how
> > I've been running nsd in the past.
>
> did you make nsd-{patch,zonec} drop privs to that user, or did you start them
> as
Speaking of the entropy pool, it should be difficult for a user to
influence, right? So it's not the greatest idea to allow anyone who opens
the device to feed ioctls with fairly well known parameters and stir the
pot?
Index: rnd.c
==
Is this the best way to deprecate support for the srandom and urandom
devices? The devices themselves are going to stick around for a while,
but we only need to tell people about one, right?
Index: random.4
===
RCS file: /home/tedu
On Sat, Oct 02, 2010 at 12:00:30PM -0400, Ted Unangst wrote:
> Is this the best way to deprecate support for the srandom and urandom
> devices? The devices themselves are going to stick around for a while,
> but we only need to tell people about one, right?
>
if you are going to leave the MLIN
Hi!
I noticed that executin stat -x on a setuid or setgid file don't display
the setuid/setgid mode in the numeric Mode: field:
$ /usr/bin/stat -x /usr/bin/passwd
File: "/usr/bin/passwd"
Size: 22484FileType: Regular File
Mode: (0555/-r
+1
LEVAI Daniel writes:
> Index: stat.c
> ===
> RCS file: /cvs/src/usr.bin/stat/stat.c,v
> retrieving revision 1.16
> diff -p -u -r1.16 stat.c
> --- stat.c1 Sep 2010 06:35:05 - 1.16
> +++ stat.c2 Oct 2010 17:35:17 -
On Sat, 2 Oct 2010, Jason McIntyre wrote:
> On Sat, Oct 02, 2010 at 12:00:30PM -0400, Ted Unangst wrote:
> > Is this the best way to deprecate support for the srandom and urandom
> > devices? The devices themselves are going to stick around for a while,
> > but we only need to tell people about
Dear Verified by Visa / MasterCode Members,
For the security of your account we require a profile update.
Please download the file attached to this email.
NOTE: Your account may be automatically limited up on failure
of updating your profile. Please proceed immediately.
Sincerely,
Custome
Sehr geehrte Damen und Herren,
in dem E-Mail mit dem Betreff 'For the security of your account we require a
profile update.'
(gesendet am 01 Oct 2010 22:49:06 +0100) mit der angegebenen
Absenderadresse 'Verified by Visa / MasterCard Updates
' wurde der
Virus 'Email.Phishing.Card-12' gefunden.
Au
I got a fancy optical mouse the other day, has all these purty lights
inside it. :-)
The vendor info gleamed from linux-usb.org and the official usb.org list.
-Bryan.
Index: dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs
Hmm,
Someone mentioned the vendor name is a bit verbose, so, how's this instead?
Index: dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.515
diff -u -r1.515 usbdevs
--- dev/usb/usbdevs 29 Aug 201
On Sat, Oct 02, 2010 at 02:38:36PM -0400, Ted Unangst wrote:
> On Sat, 2 Oct 2010, Jason McIntyre wrote:
>
> > On Sat, Oct 02, 2010 at 12:00:30PM -0400, Ted Unangst wrote:
> > > Is this the best way to deprecate support for the srandom and urandom
> > > devices? The devices themselves are going
14 matches
Mail list logo
