While trying to implement bcrypt based on the USENIX 99 paper alone, a
tiny difference between the paper and src/lib/libc/crypt/bcrypt.c left
me scratching my head until I finally gave in and had a peek.
Since it was first checked in, bcrypt.c has passed the key to the odd
Blowfish_expand0state in
At 06:40, Ted Unangst wrote:
> A simple mistake not easily corrected, but of no consequence.
Thanks — this is what I was hoping would be the case.
I've written a patch to make the ip-transparent option in nsd.conf(5)
work on OpenBSD, by trying SO_BINDANY in addition to IP_TRANSPARENT.
This fixes an issue I've had with running nsd(8) and unbound(8) at the
same time, with nsd(8) on the host's public addresses, and unbound(8)
on the host's loca
:: doesn't work either unless the -inet6 option
is specified, because incompatible address families arise.
Cheers,
Delan Azabani
Index: share/man/man4/pppoe.4
===
RCS file: /cvs/src/share/man/man4/pppoe.4,v
retrieving revision
I've written a patch to ensure that /etc/netstart executes ifconfig
inet6 autoconf, even when interfaces are specified as arguments.
I've updated my patch for revision 1.153 of /etc/netstart from the
revision 1.144 that my original patch was based on.
To the best of my judgement, this patch will
On Fri, Sep 11, 2015 at 7:43 PM, Stuart Henderson wrote:
> I've tried various combinations with the current code and haven't run
> into a case where it fails. Can you show an example of how to trigger a
> failure?
The first /etc/netstart invocation below shows how specifying interface
names on th
When deciding whether and how to reply to this thread, perhaps take a
look at the previous posts that this person has made to misc@.
u.sh/hzAdF/d13b9f4a1a.png
Cheers,
Delan Azabani
Index: etc/netstart
===
RCS file: /cvs/src/etc/netstart,v
retrieving revision 1.144
diff -u -p -r1.144 netstart
--- etc/netstart3 Dec 2014 19:55:49 - 1.144
+++ et
(ping in case anyone pertinent may have missed this)
Permanent links to screenshots:
https://www.azabani.com/patch/1/before.png
https://www.azabani.com/patch/1/after.png
On 5 February, Jeremie Courreges-Anglas wrote:
> -x ::1 is ambiguous, -x 127.0.0.1 isn't. It's just a fact.
Nit: “::1” isn’t ambiguous, because if we were to treat :1 like a port
number, “:” is all we would have left. “::1:8080” is ambiguous, so you
would need* to type “::1:8080:8080” to reach “
10 matches
Mail list logo
