audio round_buffersize

2018-08-13 Thread Michael W. Bombardieri
Hello, Low level audio drivers using the upper layer audio driver's value for buffer size don't need to declare a round_buffersize method. The 3rd parameter of the method is the value provided by the upper layer driver which is used if round_buffersize isn't defined: https://github.com/openbsd/src

Re: xidle: launching program on timeout without active-area

2018-08-13 Thread Sebastien Marie
ping On Wed, Jul 25, 2018 at 02:13:49PM +0200, Sebastien Marie wrote: > On Wed, Jul 25, 2018 at 12:55:48PM +0200, Claudio Jeker wrote: > > On Wed, Jul 25, 2018 at 12:27:29PM +0200, Sebastien Marie wrote: > > > On Mon, Jul 16, 2018 at 11:37:41AM +0200, Sebastien Marie wrote: > > > > > > > xidle(1)

Re: openssl s_time: don't fail by default in -new case

2018-08-13 Thread Jeremie Courreges-Anglas
On Mon, Aug 13 2018, Scott Cheloha wrote: > This is a fun one. When you run > > openssl s_time -connect host:port -new > > it exits with status 1, even if nothing fails, because we 'goto end' > without setting ret = 0 in the -new case. > > Present since the SSLeay 0.8.1b import into the Ope

Re: Show -o and -a in ssh-keygen(1) synopsis

2018-08-13 Thread Jeremy Evans
On 08/14 04:05, Darren Tucker wrote: > On 4 August 2018 at 18:15, Jeremy Evans wrote: > > I think the documentation for -e should be updated to specify it only > > exports public keys (assuming I'm reading the code correctly), or > > ssh-keygen should be updated to write private keys for the RFC47

Re: Show -o and -a in ssh-keygen(1) synopsis

2018-08-13 Thread Darren Tucker
On 4 August 2018 at 18:15, Jeremy Evans wrote: [...] > I checked -A and that also respects -o, so I documented that. I'm > not sure how much it matters as the host keys -A generates are not > password protected, but maybe there are other reasons to use the > newer format. The host keys must be u

Re: openssl s_time: don't fail by default in -new case

2018-08-13 Thread Theo Buehler
On Mon, Aug 13, 2018 at 11:59:56AM -0500, Scott Cheloha wrote: > This is a fun one. When you run > > openssl s_time -connect host:port -new > > it exits with status 1, even if nothing fails, because we 'goto end' > without setting ret = 0 in the -new case. > > Present since the SSLeay 0.8

Re: openssl s_time: plug SSL leak in doConnection

2018-08-13 Thread Theo Buehler
On Mon, Aug 13, 2018 at 07:01:25PM +0200, Jeremie Courreges-Anglas wrote: > On Mon, Aug 13 2018, Scott Cheloha wrote: > > tb@ spotted this one. > > > > If BIO_new fails we leak scon, so SSL_free it in that case. > > > > ok? > > Alternative proposal: let doConnection() and benchmark() free the > r

drop to pledge("stdio") on apm(8)

2018-08-13 Thread Ricardo Mestre
Hi, After we successfully connect to the unix socket created by apmd(8) all actions occur over fds so we can drop only to pledge("stdio"). The code path in the case that the required action is GETSTATUS and we couldn't connect to the socket then after open(2)/ioctl(2) the device directly we can p

Re: openssl s_time: plug SSL leak in doConnection

2018-08-13 Thread Jeremie Courreges-Anglas
On Mon, Aug 13 2018, Scott Cheloha wrote: > tb@ spotted this one. > > If BIO_new fails we leak scon, so SSL_free it in that case. > > ok? Alternative proposal: let doConnection() and benchmark() free the resources they allocated respectively. Index: s_time.c

openssl s_time: don't fail by default in -new case

2018-08-13 Thread Scott Cheloha
This is a fun one. When you run openssl s_time -connect host:port -new it exits with status 1, even if nothing fails, because we 'goto end' without setting ret = 0 in the -new case. Present since the SSLeay 0.8.1b import into the OpenSSL tree [1]. A seasoned bug. :) ok? -- Scott Chelo

openssl s_time: plug SSL leak in doConnection

2018-08-13 Thread Scott Cheloha
tb@ spotted this one. If BIO_new fails we leak scon, so SSL_free it in that case. ok? -- Scott Cheloha Index: usr.bin/openssl/s_time.c === RCS file: /cvs/src/usr.bin/openssl/s_time.c,v retrieving revision 1.25 diff -u -p -r1.25 s_t