Re: led: use timeout_add_msec(9)

2019-06-20 Thread Claudio Jeker
On Thu, Jun 20, 2019 at 11:24:15PM +0200, Klemens Nanni wrote: > The current code wants to wait 1/100 [s] = 10 [ms] but at least one > tick, that's exactly what the millisecond version provides. > > OK? > > Index: sys/arch/sparc64/dev/led.c >

OCSP Stapling with Nginx in LibreSSL 2.9.x

2019-06-20 Thread Brent Cook
Hi, I haven’t looked deeply into this, but there was a reported issue with OCSP stapling with Nginx between the LibreSSL portable releases 2.9.0 and 2.9.1 (which would have been between December 15th, 2018 and April 21st, 2019) Reposting here for visibility:

led: use timeout_add_msec(9)

2019-06-20 Thread Klemens Nanni
The current code wants to wait 1/100 [s] = 10 [ms] but at least one tick, that's exactly what the millisecond version provides. OK? Index: sys/arch/sparc64/dev/led.c === RCS file: /cvs/src/sys/arch/sparc64/dev/led.c,v retrieving

Re: bgpd minor optimization

2019-06-20 Thread Sebastian Benoit
ok Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.06.20 18:53:04 +0200: > prefix_add() is only called by path_update() and path_update already > knows if the prefix exists or not (by calling prefix_get()). So doing > the same check again in prefix_add() is silly and actually rather > expensive

Re: Qt5's libtool link scripts are unusable

2019-06-20 Thread Rafael Sadowski
On Thu Jun 20, 2019 at 04:46:59PM +0100, Stuart Henderson wrote: > Thanks for the report, > > On 2019/06/20 17:30, Vadim Penzin wrote: > > I admit that I am not familiar with the release process of pre-built binary > > packages; I might be writing to a wrong mailing list and I apologize in > >

doas environmental security

2019-06-20 Thread Ted Unangst
I've made some changes to how doas handles environment variables recently. The diffs were in previous emails, and have been committed. Thanks to Sander Bos for pointing out some particular edge cases with the old handling. There are two (or more) ways to run doas. In the first, you use it to run

Re: [patch] relayd OCSP stapling for TLS server

2019-06-20 Thread Reyk Floeter
Hi Bruno, thanks for your efforts. I‘ve already written an OCSP patch which was being delayed in review. I don’t have the patch at hand but you can see the branch at https://github.com/reyk/relayd/tree/ocsp Reyk > Am 20.06.2019 um 19:58 schrieb Bruno Flueckiger : > > Hi, > > The patch

mg(1): don't withold data indefinitely.

2019-06-20 Thread Mark Lumsden
Currently if you have a file 'test' and cat it: $ cat test abc def ghk $ Then open 'test' in mg and remove the newline at the end of the buffer and try to save it, mg will offer the opportunity to add a newline at the end of the buffer: "No newline at end of file, add one? (y or n)" Before

[patch] relayd OCSP stapling for TLS server

2019-06-20 Thread Bruno Flueckiger
Hi, The patch below adds OCSP stapling to the TLS server in relayd(8). The OCSP response is read from a binary encoded DER file that can be created using ocspcheck(8). If a file with the same name as the certificate and private key files is found, its content is loaded and OCSP stapling is

bgpd minor optimization

2019-06-20 Thread Claudio Jeker
prefix_add() is only called by path_update() and path_update already knows if the prefix exists or not (by calling prefix_get()). So doing the same check again in prefix_add() is silly and actually rather expensive with lots of peers. Just alloc and link the prefix instead. OK? -- :wq Claudio

Re: Qt5's libtool link scripts are unusable

2019-06-20 Thread Stuart Henderson
Thanks for the report, On 2019/06/20 17:30, Vadim Penzin wrote: > I admit that I am not familiar with the release process of pre-built binary > packages; I might be writing to a wrong mailing list and I apologize in > advance. ports@ is the better list for this, I've CC'd and set reply-to. >

Qt5's libtool link scripts are unusable

2019-06-20 Thread Vadim Penzin
I admit that I am not familiar with the release process of pre-built binary packages; I might be writing to a wrong mailing list and I apologize in advance. All libtool scripts from qt5 (/usr/local/lib/qt5/*.la) contain the following on their third line: LIBQt5XXX_VERSION=5.9# The name

Re: ntpd auto time setting

2019-06-20 Thread sven falempin
On Thu, Jun 20, 2019 at 6:46 AM Otto Moerbeek wrote: > Hi, > > I have been working on a nice feature that improves startup behaviour of > ntpd. > > Summary: make sure you have at least one constraint source configured > and use no options. ntpd will set the clock if needed, even if you >

Re: another go at bypass support for sparc64 iommu and BUS_DMA_64BIT

2019-06-20 Thread Klemens Nanni
Upgraded my T5240 using the latest bsd.rd, all is fine - no noticable regression in production.

Re: devel/cvsweb: README (patch)

2019-06-20 Thread Christian Weisgerber
w...@disroot.org: > after locate(1)'ing and adding those files i could happily run cvsweb on > openbsd 6.5-release > > i'm sending patch for README (2 lines) as suggested by \renaud on #openbsd > (freenode) Thanks, but this was already fixed in -current seven weeks ago. -- Christian "naddy"

ntpd auto time setting

2019-06-20 Thread Otto Moerbeek
Hi, I have been working on a nice feature that improves startup behaviour of ntpd. Summary: make sure you have at least one constraint source configured and use no options. ntpd will set the clock if needed, even if you machines has no battery backed up clock and is running a DNSSEC validating

Re: libcrypto: recognize HW acceleration support on arm64

2019-06-20 Thread Remco
On 19-06-19 07:13, Patrick Wildt wrote: Hi, this diff adds the necessary helpers to arm64 so that libcrypto knows which of the hardware crypto features are available on the machine. Those helpers are used by the existing and matching armv7 code. ok? Patrick Does it make sense to query the

devel/cvsweb: README (patch)

2019-06-20 Thread w17t
hello, after installing devel/cvsweb, doing `sh README`, and modifying cvsweb and cvsweb.conf files: i got 500 internal server error doing chroot /var/www /cgi-bin/cvsweb i noticed from the output that some files were missing: Can't locate parent.pm in @INC (you may need to install the