Hi,
$ nc -zvc openbsd.org 443 # works as expected
Connection to openbsd.org (129.128.5.194) 443 port [tcp/https] succeeded!
TLS handshake negotiated TLSv1.3/AEAD-AES256-GCM-SHA384 with host openbsd.org
[...]
$ nc -zvc openbsd.org. 443 # fails
Connection to openbsd.org. (129.128.5.194) 443 port [t
Heinrich Rebehn writes:
> I noticed that OpenBSD 6.8 switched to using less(1) for the
> manager. While this seems to offer many new useful options, I really
> dislike the clrscreen upon exit.
Have a look at -X argument to less(1):
-X | --no-init
Disables sending the termcap init
Heinrich Rebehn writes:
> Hi all,
>
> I noticed that OpenBSD 6.8 switched to using less(1) for the manager. While
> this seems to offer many new useful options, I really dislike the clrscreen
> upon exit.
> I browsed through the less(1) manage to find an option to disable this
> behavior, bu
Hi all,
I noticed that OpenBSD 6.8 switched to using less(1) for the manager. While
this seems to offer many new useful options, I really dislike the clrscreen
upon exit.
I browsed through the less(1) manage to find an option to disable this
behavior, but to no avail.
Can anyone tell me how to
parod...@gmail.com (Parodper), 2021.05.29 (Sat) 19:03 (CEST):
> # config -e -o bsd.new /bsd
> ukc> disable radeondrm
> ukc> quit
> # mv bsd.new /bsd
>
> But that only lasts for one reboot (I think on some cases not even
> that). After that the next reboots have the same problem. Any tips to
> make
So I've got an old single-core computer that can't boot with radeondrm
enabled. I checked and if I disable it from the boot prompt there are no
problems, but it doesn't persist between reboots.
After checking the man pages I found the config(8) tool, which seemed to
solve my problem. Using the ex
The hardware in question consists of a Supermicro H8SGL motherboard with an
AMD Opteron 6276 CPU and 64 GB of RAM. Outputs for dmesg and sysctl hw are
appended at the end of this message.
This is an OpenBSD 6.9 system (patched up to #005) which stalls indefinitely
at "syncing disks... done" re
Hi,
Kicking this as it first appeared in the 6.8 release.
I have upgraded a PC with a VIA VE-900 chipset (VIA Nano X2 CPU) from
6.8 to 6.9. The box hangs on reboot after upgrade. The last line shown
was for azalia. I disabled azalia which then allows 6.9 to boot to
completion.
Comparing
Ronan Viel writes:
>
>> Philip Kaludercic writes:
>> which would mean that the certificate should be called localhost:443 (or
>> 127.0.0.1:443)
>
> No, it means the certificate must be named /etc/ssl/localhost:443.crt
> or /etc/ssl/127.0.0.1:443.crt, and the matching key must be in file
> /etc
9 matches
Mail list logo