Hi,
I created a patch for CVE-2014-4330 in Data::Dumper, Version 2.145.
Derived from
http://perl5.git.perl.org/perl.git/commitdiff/19be3be6968e2337bcdfe480693fff795ecd1304
See below.
Regards,
Max Pascher
--- gnu/usr.bin/perl/MANIFEST.orig Tue Sep 30 08:51:52 2014
+++
Hi everyone,
This is my attempt to add libc wrappers for mkfifo() and
mkfifoat() using mknodat().
Do I need to do anything else? Should the manpage for mkfifo(2)
and mkfifoat(2) be moved to section 3?
Cheers,
Dimitris
===
RCS
On Thu, Oct 23, 2014 at 15:16, Dimitris Papastamos wrote:
Hi everyone,
This is my attempt to add libc wrappers for mkfifo() and
mkfifoat() using mknodat().
Is there a reason? This would seem to do nothing except complicate the
interpretation of ktrace.
[What I'm pointing out below looks like a mistake regardless of the
variables in scope.]
On Wed, Oct 22, 2014 at 1:40 AM, Henning Brauer
hb-openbsdt...@ml.bsws.de wrote:
* Chris Cappuccio ch...@nmedia.net [2014-10-22 01:11]:
Stuart Henderson [st...@openbsd.org] wrote:
Any comments on the diff
* Andres Perera andre...@zoho.com [2014-10-23 17:14]:
[What I'm pointing out below looks like a mistake regardless of the
variables in scope.]
void
+addaf(const char *vname, int value)
+{
^ *v*name
+ struct if_afreq ifar;
+
+ strlcpy(ifar.ifar_name, name,
I'm not convinced we actually want to do this, but your wrapper is
missing something like this:
mode = ~ACCESSPERMS;
- todd
On Thu, Oct 23, 2014 at 11:12:02AM -0400, Ted Unangst wrote:
On Thu, Oct 23, 2014 at 15:16, Dimitris Papastamos wrote:
Hi everyone,
This is my attempt to add libc wrappers for mkfifo() and
mkfifoat() using mknodat().
Is there a reason? This would seem to do nothing except complicate
On Wed, Oct 22, 2014 at 07:28:40PM -0500, Brent Cook wrote:
On Wed, Oct 22, 2014 at 4:02 PM, Ted Unangst t...@tedunangst.com wrote:
On Wed, Oct 22, 2014 at 16:07, Michael B. Trausch wrote:
[snip]
I think the first piece is of course the necessary build files. Access
to Windows
Hi,
I hope this is the right list. If it is the wrong list I'd welcome a
hint to the correct list.
Some suggestions for the ressl API:
* Please consider making ressl_config_set_protocols accepting a string
as option instead.
Using constants for protocols like OpenSSL does make it much harder
with SUDO set in /etc/mk.conf:
if make release is run as root it will not proceed.
if run as a regular user it gets further, but fails on permissions.
without SUDO in /etc/mk.conf (and i presume the environment) it works fine.
is there any way around this allowing /etc/mk.conf (which is
10 matches
Mail list logo