if you don't think having a key isolated in a separate process without networking is much better than having it floating around in the safari's memory space, I can't help you. ideally key stored in: hw device > sandboxed process > browser plugin > webpage saying I'm misrepresenting the problem is just not true, this is an obvious improvement short of hw device signing. I guess it just comes down to how much you trust browser engineers to not fuck things up.

Replies (1)

it is objectively an improvement, but for most users it doesn’t matter that much we should probably also focus on other attack vectors: decryption permission is all-or-nothing, the user can be fatigued into granting unprompted sign permissions to an app etc