Re: sbin/iked fallout after OpenSSL valahalla slashing

those should all be fixed now. On Wed, Apr 16, 2014 at 04:19:09PM +1000, Ian McWilliam wrote: > ?? > > Sorry, it's a poor choice of MS outlook or Web email client here at > work. > > /usr/src/usr.bin/gzsig suffers similar fallout it looks a little bit > tricker to fix. > > cc -O2

Re: sbin/iked fallout after OpenSSL valahalla slashing

  Sorry, it's a poor choice of MS outlook or Web email client here at work. /usr/src/usr.bin/gzsig suffers similar fallout it looks a little bit tricker to fix. cc -O2 -pipe    -c /usr/src/usr.bin/gzsig/ssh.c /usr/src/usr.bin/gzsig/ssh.c:59: error: expected specifier-qua

Re: sbin/iked fallout after OpenSSL valahalla slashing

not quite, because your diff was mangled, but I think you had it right anyway.. fix committed by miod, thanks for telling us. On Wed, Apr 16, 2014 at 03:39:03PM +1000, Ian McWilliam wrote: > Hoope the attached diff is a correct fix. Hit me with the cluebat if > not. > > cc -O2 -pipe ??-Wall -I

sbin/iked fallout after OpenSSL valahalla slashing

Hoope the attached diff is a correct fix. Hit me with the cluebat if not. cc -O2 -pipe  -Wall -I/usr/src/sbin/iked -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wsign-compare -fno-pie   -c /usr/src/sbin/iked/chap_ms.c/usr/src/sbin/iked/chap_m

Re: libexec/login_tis fallout after OpenSSL Valhalla rampage

Fixed. Thanks for reporting. Miod

libexec/login_tis fallout after OpenSSL Valhalla rampage

ianm-openbsd:login_tis {123} make cc -O2 -pipe  -Wall   -c /usr/src/libexec/login_tis/login_tis.c In file included from /usr/src/libexec/login_tis/login_tis.c:43: /usr/src/libexec/login_tis/login_tis.h:36: error: expected specifier-qualifier-list before 'des_

Re: GOST was removed

Hi, On Tue, Apr 15, 2014 at 09:24:48PM +, �?�?�?�?�? �?�?�?омин wrote: > Log message: > Remove the GOST engine: It is not compiled or used and depends on the > "dynamic engine" feature that is not enabled in our build. People who > need it can still pull it out of the Attic; if it is to have

Re: GOST was removed

> In the interests of full disclosure, do you work for the government or > sell to the government? And in the interests of full disclosure, please note, It's absolutely not political. We just deleted all the FIPS junk too. the right way to add GOST if you need it is not as an engine, but as a wor

Re: GOST was removed

>Log message: >Remove the GOST engine: It is not compiled or used and depends on the >"dynamic engine" feature that is not enabled in our build. People who >need it can still pull it out of the Attic; if it is to have a Russian >engine just because it's a Russian engine. >-

GOST was removed

Log message: Remove the GOST engine: It is not compiled or used and depends on the "dynamic engine" feature that is not enabled in our build. People who need it can still pull it out of the Attic; if it is to have a Russian engine just because it's a Russian engine. ---

Re: re-introducing ssl_privsep.c

> > > The code I'm referring to is src/usr.sbin/relayd/ssl_privsep.c which is > > also present in ldapd and smtpd. > > There's a lot more code to remove first. > > That should be first order of action, so come back in a few weeks. > Makes perfect sense, I'll wait a bit

Re: re-introducing ssl_privsep.c

> Long-time no see :-) > Now that there will be more limited interaction between upstream and the > in-tree libssl, would it make sense for me to prep up a diff which would > integrate ssl_privsep.c in libssl directly (I initially sent out a diff > upstream which was never looked at and we decided

re-introducing ssl_privsep.c

Hi gang, Long-time no see :-) Now that there will be more limited interaction between upstream and the in-tree libssl, would it make sense for me to prep up a diff which would integrate ssl_privsep.c in libssl directly (I initially sent out a diff upstream which was never looked at and we decided

Re: segfault in dhclient 5.4 please help

On Tue, Apr 15, 2014 at 7:13 AM, Kenneth Westerback wrote: > On 15 April 2014 08:34, Otto Moerbeek wrote: >> On Mon, Apr 14, 2014 at 09:32:43PM -0400, sven falempin wrote: >> >>> so i got gdb back to the machine because i cannot reproduce outside of the >>> box. >>> gdb too old cannot gcore. >>>

Re: segfault in dhclient 5.4 please help

> Op 15 apr. 2014 om 13:13 heeft Kenneth Westerback het > volgende geschreven: > >> On 15 April 2014 08:34, Otto Moerbeek wrote: >>> On Mon, Apr 14, 2014 at 09:32:43PM -0400, sven falempin wrote: >>> >>> so i got gdb back to the machine because i cannot reproduce outside of the >>> box. >>>

Re: segfault in dhclient 5.4 please help

On 15 April 2014 08:34, Otto Moerbeek wrote: > On Mon, Apr 14, 2014 at 09:32:43PM -0400, sven falempin wrote: > >> so i got gdb back to the machine because i cannot reproduce outside of the >> box. >> gdb too old cannot gcore. >> >> The state is nasty, but i do get the trace of the dhcp transacti

Re: xcb-util-cursor broken

On Tue, Apr 15, 2014 at 10:52:25AM +0200, David Coppa wrote: > > Hi! > > x11/i3 (and x11/awesome too) wants to use libxcb-cursor. > Back in the days I patched upstream code and reverted it to use libXcursor. > Now that we have xcb-util-cursor I want to remove those patches. > However, xcb-util-cu

xcb-util-cursor broken

Hi! x11/i3 (and x11/awesome too) wants to use libxcb-cursor. Back in the days I patched upstream code and reverted it to use libXcursor. Now that we have xcb-util-cursor I want to remove those patches. However, xcb-util-cursor is currently broken: [i3] CC src/config_parser.c cc -DI3_VERSION=\"'4

Re: print time_t with %lld in last(1)

ping On Sun, Mar 23, 2014 at 07:31:11PM +0200, Arto Jonsson wrote: > Index: last.c > === > RCS file: /cvs/src/usr.bin/last/last.c,v > retrieving revision 1.39 > diff -u -p -r1.39 last.c > --- last.c22 Aug 2013 04:43:40 -