It's an excellent suggestion if the code you're trying to communicate with is not actually the kernel, but rather other code on the machine that the kernel is attempting to prevent you from communicating with. Except for the ASN.1 part. That's never a good idea.
Re:Ways of Implementing a System Call
by SAI_Peregrinus on Friday January 17, 2020 @09:24AM
(#22074802)
> Except for the ASN.1 part. That's never a good idea.
Don't kink-shame the ITU-T! They're just sadomasochistic, that's all...
Re:Ways of Implementing a System Call
by waterhouse on Friday January 17, 2020 @04:00AM
(#22073061)
Or code not on the machine. I remember: "PowerHammer: Exfiltrating Data from Air-Gapped Computers Through Power Lines" https://news.ycombinator.com/item?id=16821513
Nothing from that list is sane i386 syscall mechanism :).
(Which given the fact that the list contains undocumented and obscure 0xf1 icebp and not documented 0xcc int3 seems to be the intention)
I like how you mixed this in with real suggestions.