RageLtMan

@moznion - is there a way to enforce the _order_ of attribute fields? Not a problem for RFC-compliant packet-parsers, but not great for the HMAC piece when messing with attributes...

@moznion: i'm dealing with the field ordering mess by way of byte-slice replacement for the 16B of the Message-Authenticator for the time being, but i think that this concern is...

When a struct such as [field1,field2,field3] is hashed and then field2 is removed and a replacement appended after field3, the struct containing the same fields in a different order will...

Thanks a ton - i've a live test-case to work through debugging if that would be handy. Getting my head around how you have dictionaries working here. Takes a little...

Looks like the term "string" is a bit loose in the spec ``` 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3...

Getting the hang of this more or less - dictionary data feeds into code-gen, that produces the Rust `rfcX` files, and EAP-handling logic actually needs to go in there.

This is worse than i thought: `zpool import -F -n` - a _dry run_ of a forced import _still_ produces the same exact crash.

Same deal with `-m` passed, even though it never had a SLOG, figured it might discard the on-disk SLOG. No dice. @behlendorf - from a forensics standpoint, this might be...

Of note: the ZFS pool which went sour here was created in December of 2019 with whatever the last tag was at that time. The pool itself had never been...

I've crossed into some twilight zone nightmare apparently. The pool in question had been backed up - rather the underlying block media had been backed up some time ago. Having...