Re: [PATCH] correcting in-sane ntpd.conf

lease correct me. g Stephan On Sun, Dec 08, 2019 at 10:36:18AM +0100, Otto Moerbeek wrote: > On Sun, Dec 08, 2019 at 11:15:55AM +0100, List wrote: > > > Please excuse that I wasted your time. You're absolutely right. > > > > The only thing that comes to my mind is that

Re: [PATCH] correcting in-sane ntpd.conf

ttps > because we added their ticker in the mix (though their anycast ticker > is a very weird thing) > > >g Stephan > > > >On Thu, Dec 05, 2019 at 03:03:43PM -0700, Theo de Raadt wrote: > >> I guess you don't understand what is going on there. > >>

[PATCH] correcting in-sane ntpd.conf

Hello, here a diff replacing www.google.com as a default time constraint by www.openbsd.org. It is claimed that OpenBSD would have sane and secure defaults. While www.google.com might be secure it ain't sane from a privacy concerned perspective. Therefore the diff. Regards, Stephan Index: etc/

Re: Keydisk encryption (sr_crypto_create_keys / sr_crypto_decrypt_key)

does. Maybe I'm too restricted in my view there. g On 2019-10-24 21:14, Sebastian Benoit wrote: > List(l...@md5collisions.eu) on 2019.10.24 21:06:27 +0200: >> Hi, >> >> in function sr_crypto_create_keys (sys/dev/softraid_crypto.c, 489): >> >> The keydisk

Keydisk encryption (sr_crypto_create_keys / sr_crypto_decrypt_key)

Hi, in function sr_crypto_create_keys (sys/dev/softraid_crypto.c, 489): The keydisk is masked by encrypting(1) a generated random buffer. This encrypted random buffer (keydisk) is afterwards used to encrypt(2) the harddisk itself. Why is it done that way ? Would it be ok to not store this (1)

Encrypted keydisk

Hi, I'm missing the ability to encrypt my keydisk with a passphrase. I'd try and implement it. Is there a suggested approach ? I'd just grab the buffer that is written to the keydisk before it's written down and encrypt it symmetrically. (using openssl?) And reverse the process for decrypting.

OpenBSD 5.6, syslog-ng, and sendsyslog(2)

Hello Folks, it seems syslog-ng (v3.4.7p3, from the OpenBSD package collection) is broken on OpenBSD 5.6, because it does not implement the new mechanism used by sendsyslog(2) and syslogd. Are there any plans to fix this? Does anyone care? What is the point of including a broken package for 5.6?

replace libc on running system?

Hello Folks, I've patched, recompiled and relinked libc. Are there any risks in installing it on a running production system? Do I need to reboot immediately after installation? cheers, Rob Urban

Re: problem with gethostbyaddr() on OBSD 5.4?

[I forgot to send this to the list] Hi Eric, On 02/01/2014 11:43 AM, Eric Faurot wrote: > The following diff fixes the problems with the example IPs you gave us. > - subsequent PTR records are now set as aliases in the hostent > - need to accept '/' in dname labels (maybe othe

problem with gethostbyaddr() on OBSD 5.4?

Hello Folks, I run a Postfix MTA on OpenBSD. Recently I migrated the server from OBSD v5.3 to v5.4. Soon afterwards I noticed postfix was falsely rejecting mails based on a FCrDNS (forward-confirmed reverse DNS) test. FCrDNS means the DNS configuration of a connecting client is tested for forward

any interest in old compaq/HP SCSI/FC disks?

Hello Misc & Tech, please forgive my cross-posting -- I wanted to be sure to reach people who might be interested. Some people I know are preparing to move out of an old machine-room, and will dispose of some old hard disks soon. The collection varies: Sizes: 4.3, 9.1, 18, 36 (and maybe 72)

Hostap issue with athn

Hi list, I have an issue making an access point with an Atheros Wistron DNMA92 (AR9280). The card works perfectly in infrastructure mode (54 Mbits), but in hostap most clients (Linux, Android, Windows) cannot associate themselves. When client succeed to associate themselves, they are limited to