Hi,
I have strange setup on some of my machines, when I want to encrypt disk
where OpenBSD is installed, but still be able to boot them up without
any user interaction, like passphrase entry for CRYPTO softraid(4). I
have this so I can with little time spent lock out access to the disk,
by wiping
On Sun, Sep 04, 2022 at 07:08:51PM +, Mikolaj Kucharski wrote:
> I have strange setup on some of my machines, when I want to encrypt disk
> where OpenBSD is installed, but still be able to boot them up without
> any user interaction, like passphrase entry for CRYPTO softraid(4). I
> have this
On Sun, Sep 04, 2022 at 06:53:00AM +0100, Jason McIntyre wrote:
> On Sat, Sep 03, 2022 at 06:12:16PM +, Klemens Nanni wrote:
> > The current text is badly formatted and incomplete as to which optional
> > parts can be omitted in which way
> >
> > The file specification used is of the
On Sat, Sep 03, 2022 at 11:51:41PM +, Lucas wrote:
> Hello tech@,
>
> commit r1.9 removed the rc_exec call in iked's rc_pre. Because of that,
> the exit code of rc_pre is that of the && list. In the case of
> sasyncd_flags=NO, this means that rc_pre fails and triggers the break
> in the while
On Sun, Sep 04, 2022 at 07:08:51PM +, Mikolaj Kucharski wrote:
> Hi,
>
> I have strange setup on some of my machines, when I want to encrypt disk
> where OpenBSD is installed, but still be able to boot them up without
> any user interaction, like passphrase entry for CRYPTO softraid(4). I
>
On Sun, Sep 04, 2022 at 10:21:24PM +, Klemens Nanni wrote:
...
> > Booting from Hard Disk...
> > Using drive 0, partition 3.
> > Loading..
> > ERR M
> >
> >
> > To keep it short, it is because of installboot(8) installs boot blocks
> > on both wd0a and wd0d:
> >
> > ramdisk# bioctl sd0
On Sun, Sep 04, 2022 at 11:25:08PM +, Mikolaj Kucharski wrote:
> # bioctl sd0
> Volume Status Size Device
> softraid0 0 Online 268426960384 sd0 CRYPTO
> 0 Online 268426960384 0:0.0 noencl
> 1 Online key disk 0:1.0 noencl
