>>>4706

>>4706

Q

Please use a GPG "clearsign" signature. You can share your public key here and your private key on any devices you wish to post from. We can then verify your posts WITHOUT having to trust ANY board or board owner.

https:// www.gnupg.org/gph/en/manual/x135.html

>>4858

>>4857

Please draw attention to my post, 4856. We can always independently verify and trust Q's posts if [s]he sees this and starts using this method.

>>4856

>>4909

Why should anyone continue to trust the abilities of a group that have developed a shitty insecure algorithm? Something public and mathematically proven should be used.

>>4856

>>5000

I think Bannon is a patriot and this is a show.

>>5089

man, you don't know what you're talking about. devs work themselves to sickness. the issue is that when you're working on something that's a million lines of code, you HAVE to learn to reuse work.

>>5089

I should caveat though, I agree there are extreme dangers in reusing code in terms of security. These can be mitigated by having careful reviews of that code. "New" code on the other hand has dangers that can't be predicted. See http:// www.underhanded-c.org/

>>5145

kek.

>>5212

Who needs training & guidance? Search for GPG clearsign.

>>5026

>>4856

>>4859

>>4954

>>5219

FYI, Q.

Windoze instructions later. Hopefully we can bake all this in and subvert any sort of BO power.

>>5495

Gee, thanks, anon. You have no idea how much more I feel like we're lost as a species thanks to this post.

>>01:00:00 bd5d26 No.5499

FUCK YOU KEK. :(

>>5500

The public key block only needs to be posted once, and imported by anons once, so it should be OK. I'll test your output.

>>5500

The only trouble with this so far is the character encodings aren't the same as command line. Eg the lines before "BEGIN PGP" are not dashes —.

>>5516

>—

Fck. It's the board that does it.

>>5489

>>5500

>>5510

Here's what verification looks like.