Okay, this sounds like its headed to the right direction then, I agree this
seems like something where the kernel needs to deal with it because it's the
only thing that can.
I see block size is an argument passed to the ioctl() that enables this
fsverity for a file, but what does that actually mean? Can individual files
have different block size for their Merkle tree? In the current state of things
it seems more like a hardwired global'ish thing.
What I'm getting at is that if we make block size a configurable thing in rpm,
then the kernel will really need to support different block sizes for
individual files as rpms come from variety of sources and might be signed with
different options.
I'm tempted to say lets just go with a hardwired 4K size for now to keep things
simple, we can always add another tag for alternative block size if it becomes
necessary for one reason or another.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1203#issuecomment-638092594
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
