News for hackers. Stuff that matters.
Re:Ways of Implementing a System Call by etaioinshrdlu on Friday January 17, 2020 @02:51AM (#22072715)
> Modulate the CPU temperature by running code. The OS decodes the signal. Use message passing that involves OFDM, LDPC, ASN.1, and digital signatures.

I like how you mixed this in with real suggestions.

Re:Ways of Implementing a System Call by kragen on Friday January 17, 2020 @02:56AM (#22072733)
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
Re:Ways of Implementing a System Call by EGreg on Friday January 17, 2020 @04:17AM (#22073149)
Re:Ways of Implementing a System Call by dfox on Friday January 17, 2020 @08:01AM (#22074211)
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)

Re:Ways of Implementing a System Call by int_19h on Friday January 17, 2020 @04:01AM (#22073068)
Finally, a perfect application for INTERCAL.