Peter Jeremy via freebsd-current (freebsd-curr...@freebsd.org) wrote:
> [Adding arm@ and making it clearer that this is armv8-only]
>
> On 2021-Mar-06 20:26:19 +1100, Peter Jeremy wrote:
> >On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
> > wrote:
> >>Somewhere between 13.0-ALPHA
On 2021-Mar-06 10:39:02 -0800, Oleksandr Tymoshenko wrote:
>Peter Jeremy via freebsd-current (freebsd-curr...@freebsd.org) wrote:
>> [Adding arm@ and making it clearer that this is armv8-only]
>>
>> On 2021-Mar-06 20:26:19 +1100, Peter Jeremy
>> wrote:
>> >On 2021-Mar-06 19:18:37 +1100, Peter J
[Adding arm@ and making it clearer that this is armv8-only]
On 2021-Mar-06 20:26:19 +1100, Peter Jeremy wrote:
>On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
> wrote:
>>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>>(releng/13.0-n244592-e32bc253629), geli
On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
wrote:
>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>RK3399, arm64) has changed so that a geli-encrypted partition (using
>AES-XTS 128) that
Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
RK3399, arm64) has changed so that a geli-encrypted partition (using
AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on
13.0-BETA4.
I've verified th