wrote:
> That doesn't seem right. Did you folks use the wrong key when signing
> the file, or is there a particular reason to do it this way that me's
> not aware of...?
These files have now been replaced. Does it look right?
On 2019-11-10, wrote:
> That doesn't seem right. Did you folks use the wrong key when signing
> the file, or is there a particular reason to do it this way that me's
> not aware of...?
Thanks for the report, yes i386 (and mips64) had the wrong key. I guess
not many people are doing fresh
That doesn't seem right. Did you folks use the wrong key when signing
the file, or is there a particular reason to do it this way that me's
not aware of...?
--zeur.
--
Friggin' Machines!
My new box has the same /etc/myname.
I copied:
/etc/iked/ca/ca.crt
/etc/iked/certs/1.2.3.4.crt
/etc/iked/crls/ca.crl
/etc/ssl/vpn/*
What did I do wrong/miss?
Windows shows error 13826: Failed to verify signature.
On Sun, 10 Nov 2019 13:30:24 - (UTC)
Stuart Henderson wrote:
> On
Theo de Raadt wrote:
>We are pleased to announce the official release of OpenBSD 6.6.
[...]
>o Made startx(1) and xinit(1) work again on modern systems using
> inteldrm(4), radeondrm(4) and amdgpu(4).
So what exactly is a "modern system"? Or, put another way, how does one
differenciate
On 2019-11-10, Radek wrote:
> Hi Stuart,
> I have played around with copying them across but no luck (I get error 13801
> in win7). I don't know what I'm doing wrong.
>
> Do I need to set the same hostname (/etc/myname) in new box to make old certs
> working?
>
> In my *old* box certs were
Hi Stuart,
I have played around with copying them across but no luck (I get error 13801 in
win7). I don't know what I'm doing wrong.
Do I need to set the same hostname (/etc/myname) in new box to make old certs
working?
In my *old* box certs were created as below:
[1]ikectl ca vpn create #(CN
7 matches
Mail list logo
