[ home / board list / faq / random / create / bans / search / manage / irc ] [ ]

/netplus/ - Networks and Plus

Catalog

See 8chan's new software in development (discuss) (help out)
Infinity Next update (Jan 4 2016)
Name
Email
Subject
Comment *
File
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Oekaki
Show oekaki applet
(replaces files and can be used instead)
Options
dicesidesmodifier
Password (For file and post deletion.)

Allowed file types:jpg, jpeg, gif, png, webm, mp4, pdf, pdf
Max filesize is 8 MB.
Max image dimensions are 10000 x 10000.
You may upload 5 per post.


File: 1433427902891-0.png (9.62 KB, 280x280, 1:1, gnupg.png)

File: 1433427902892-1.png (36.67 KB, 500x521, 500:521, pgp1.png)

 No.24

OpenPGP (Pretty Good Privacy) is a set of standards and protocols for encrypting and signing messages using private and public keys. PGP is the most popular method of encrypting email messages. There are multiple PGP implementations both free and proprietary, I will be discussing GPG (GNU Privacy Guard).

PGP works by generating two associated keys, a private key that you keep to yourself, this is used to sign messages and to decrypt messages that other people have encrypted for you using your public key which you distribute, using your public key people can encrypt message that can then only be decrypted using your private key and they can also use your public key to verify messages that have been signed with your private key.

For more information about PGP, GPG and Public-key cryptography see the following links.

http://www.openpgp.org/about_openpgp/

https://www.gnupg.org/documentation/index.html

https://en.wikipedia.org/wiki/Pretty_Good_Privacy

https://en.wikipedia.org/wiki/Public-key_cryptography

The following guide is for people using GNU/Linux and I will be using the seahorse frontend, KDE users will prefer KGPG. Windows users can use gpg4win http://www.gpg4win.org/

Mac users can probably do something to but it would likely involves penises, and not in the good way.

Post last edited at

 No.34

File: 1433430919231.webm (2.73 MB, 1676x810, 838:405, 1.webm)

Install the seahorse package, for Debian/Trisquel/Ubuntu/Mint/etc. users

sudo apt-get install seahorse


 No.35

File: 1433430974890.webm (3.97 MB, 1676x810, 838:405, 2.webm)

After filling in your name and email and choosing you key length (you don't have to use 4096 but why not right) the program will appear to do nothing for a while, that's normal it's just working in the background to generate your key, depending on your key length and the processing power of your computer this can take a loooong time, 30m+ even so don't worry, it is working.


 No.36

File: 1433431033496.webm (4.32 MB, 1676x810, 838:405, 3.webm)

Distribute you public key so that people can use it to encrypt messages to you and verify things you sign using you new key. Additionally you may wish to upload you public key to public key server, this allows you to instead distribute the much shorter “fingerprint” or id of your public key and people can then search for your key on the public key server and verify the full key returned against the fingerprint you gave them.


 No.37

File: 1433431113754.webm (4.02 MB, 1676x810, 838:405, 4.webm)

Import someone else's public key so that you can verify their signed messages and send them encrypted messages.


 No.38

5. Working with GPG

To actually use the keys you have made and imported to sign, verify, encrypt and decrypt you can use the GPG cli

man gpg
or alternatively there are many applications available that have support for GPG some natively and some though the use of plugins. For this example I will use the Geany editor with the pgp plugin available for it and also the nautilus file manager plugin. Some other applications with GPG support include; vim, emacs, dolphin and of course the thunderbird mail client through the use of the enigmail addon.


 No.39

File: 1433431256265.webm (5.4 MB, 1676x810, 838:405, 6.webm)

Verify a message from someone who's key you have imported.


 No.40

File: 1433431324602.webm (2.93 MB, 1676x810, 838:405, 7.webm)

Sign a message so that other people can verify that you are the one who wrote it


 No.41

File: 1433431359391.webm (1.9 MB, 1676x810, 838:405, 8.webm)

Encrypt a message using someone's public key so that only that person can decrypt it


 No.42

File: 1433431409432.webm (2.97 MB, 1676x810, 838:405, 9.webm)

Encrypt a message for someone and sign it with your key so that they can verify it came from your


 No.43

File: 1433431500187.webm (4.28 MB, 1676x810, 838:405, 10.webm)

Encrypt and decrypt files from with nautilus


 No.44

For an integrated email solution checkout the enigmail addon for thunderbird.

https://www.enigmail.net

https://www.enigmail.net/documentation/quickstart.php


 No.46

BGB (Breddy Good Brivacy).


 No.216

File: 1437159204170.png (29.34 KB, 280x280, 1:1, sad truth.png)

I'd recommend against the use of PGP.

First of all, metadata and DPI:

>https://gist.github.com/grugq/03167bed45e774551155

>Unfortunately, even PGP encrypted email leaves comms metadata exposed, this includes: […]

>http://secushare.org/PGP

>Thanks to its easily detectable OpenPGP Message Format it is an easy exercise for any manufacturer of Deep Packet Inspection

>using the –hidden-recipient flag you can tell PGP to, at least, hide who you are talking to. Hardly anyone does that

Subject is never encrypted.

>https://gist.github.com/grugq/03167bed45e774551155

>For example, "Subject: Your cocaine has shipped!" is a total email security failure.

* No Forward Secrecy.

>https://en.wikipedia.org/wiki/Forward_secrecy

* In the worst case scenario, all your mail can be decrypted and anyone can fake your identity and you can't deny emails encrypted with the same key are yours.

>https://twitter.com/thegrugq/status/618106748147101696

>That PGP key. Fortunately it is protected by a pass phrase. Less fortunately, it is protected by Pozzi’s pass phrase

Anyone can revoke your key too.

>https://pgp.mit.edu/pks/lookup?op=vindex&search=0x775964D270C2F02F

*Mistakes are forever

Your mistake is stored forever on a keyserver, unless Hitler comes from hell riding a dinosaur and destroys the MIT (and any other keyserver)

Only PGP Global directory provides a remedy

>https://en.wikipedia.org/wiki/Key_server_%28cryptographic%29#Problems_with_keyservers

>accumulation of old fossil public keys that never go away, a form of "keyserver plaque". Another problem is that anyone can upload a bogus public key to the keyserver, bearing the name of a person who in fact does not own that key. The keyserver had no way to check to see if the key was legitimate.

>To solve these problems, PGP Corp developed a new generation of key server, called the PGP Global Directory. This keyserver sent an email confirmation request to the putative key owner, asking that person to confirm that the key in question is theirs. If they confirm it, the PGP Global Directory accepts the key. This can be renewed periodically, still anyone can download a public key from the PGP Global Directory and upload it to pgp.mit.edu or any other keyserver, thus defying any control of the owner on his/her own keys.

The "Web of trust" concept is bogus.

>https://lists.torproject.org/pipermail/tor-talk/2013-September/030235.html

>Why the Web of Trust Sucks


 No.217

>>216

*Again on the forward secrecy, and possible plausible deniability

There's a draft (check references too)

>https://tools.ietf.org/html/draft-brown-pgp-pfs-03

>Short-lifetime encryption keys

>Therefore when a public encryption key expires, an OpenPGP client MUST securely wipe the corresponding private key

>Deletion should take place once all messages that could have been sent before expiry have been received and decrypted.

Some users in OPSEC have a long term and a short/mid term keys

>http://www0.cs.ucl.ac.uk/staff/I.Brown/pfs2.html

>Using a series of encryption keys, each with a short lifetime, reduces the information revealed by the compromise of any one private key because each key protects less data.

Short-term keys is an attempt to minimize the "worst case scenario" (if short term private keys are periodically deleted) and gain some forward secrecy. Still, in this picture, the short term keys are signed with the long-term key, thus you have no plausible deniability.

>https://en.wikipedia.org/wiki/Plausible_deniability#Use_in_cryptography

There's some peculiar use of PGP keys in one-time-comms scenario where two or anyway few users exchange keys privately (maybe in person as well) for a one-time affair.

They could maybe exchange such a short-term encryption key (public key) attaching that to a message (and signing the message with the key). They keep it confidential and promise 1) not to upload the keys to a keyserver 2) not to associate themselves with the keys 3) delete the keys once done.

It's a totally different usage of the OpenPGP standard from what is was conceived. There's a lot of human error to deal with.

TBH, PGP nowadays is good just for signing F/LOSS newsletter (and only few do that anyway) or for an exceptional signing/seal of authenticity (of a package in your distro, of a binary file you download from the internet and so on).

The answer to all this is pond.

>Pond is forward secure, asynchronous messaging for the discerning. Pond messages are asynchronous, but are not a record; they expire automatically a week after they are received. Pond seeks to prevent leaking traffic information against everyone except a global passive attacker

>http://secushare.org/PGP

>Pond is currently among the most interesting projects for mail privacy, hiding its padded undetectable crypto in the general noise of Tor

Anyway

>https://pond.imperialviolet.org/

>Dear God, please don't use Pond for anything real yet. I've hammered out nearly 20K lines of code that have never been reviewed. Unless you're looking to experiment you should go use something that actually works [gnupg]

Pond is experimental/not audited, but

>Jacob Appelbaum recommends to use PGP over Pond instead of over E-Mail.

Possibly without personal details in your PGP key.

Regardless of your usage case, you should anyway use - at least - Appelbaum's duraconf

>https://raw.githubusercontent.com/ioerror/duraconf/master/configs/gnupg/gpg.conf


 No.218

>>217

>Some users in OPSEC have a long term and a short/mid term keys

Also, relevant:

>https://wiki.debian.org/Subkeys


 No.220

thank you for these informative posts.


 No.239

>>218

using subkeys in pgp is an ugly mess.

pgp is a fucking piece of shit with an awful user interface but it does work and you can write scripts to hide the ugliness but i don't think there exists something to properly handle subkeys yet.

but until something better comes along we're stuck with it, and these days it seems that 99% of new crypto applications are just scams targeted at hipsters.


 No.333

I have a couple of questions:

It seems you don't really need a valid e-mail address to generate a new pair of keys, right? You can make a new pair without linking it to any address?

And when I make a new pair of keys the process is completely local by default? Nothing related to PGP goes through my connection?


 No.338

How do I save a pair of keys, in order to transfer it to an external device? I mean, where do I find the secret key?


 No.339


 No.358

File: 1440948543470.gif (7.75 KB, 181x146, 181:146, ONMP.gif)

>>217

>Pond

>>>Pond is forward secure, asynchronous messaging for the discerning. Pond messages are asynchronous, but are not a record; they expire automatically a week after they are received.

May I suggest to give a look at onionmail

Clearnet site: onionmail.info

Hidden site: louhlbgyupgktsw7.onion

It's free software and you can download it from their site. It's a federation of servers. Like XMPP, each one can talk to each other, and the whole subnet can talk to other Tor or clearnet email providers.

Note that the site hosts just a list of public hidden node, that are running the real servers

>https://archive.is/http://www.hacker10.com/internet-anonymity/onionmail-an-anonymous-mail-server-running-on-tor/

May I underline something in "Rulez" page you can look at browsing one of the actual servers i.e.

>http://wc2eyfmw7wrwomf4.onion/rulez.html

or

>http://ndo2plzaruzxk6sb.onion/rulez.html

or

>http://ridotnp5m5lp22gw.onion/rulez.html

and so on, pick one

>

>[2.0] Sending emails

>

>(1) Mail messages are saved only in the recipient's server and encrypted

>with multiple asymmetric keys.

>

>Communicating with the server

>

>To communicate with the server it's sufficient to send a message to

>server@<xyz>.onion (Where <xyz> is identical to your address after "@").

(then there's a list of IRC-alike commands to create your own spam list and so on)

>[5.0] Create your OnionMail address

>

>1) Get your public PGP key and copy the ASCII armor.

>2) Send a message to the server (server@address.onion) with subject:

> NEWUSER username

> Where username is your user name and the address part before "@".

> Paste the public key into the body of the message.

>[9.0] User configuration.

>

>To read and configure the parameters of your account, send a message to the

>server with subject the word "SETTINGS".

but what sounds very close to Pond and seems interesting to me is

>(3) Messages, either read or not, are deleted automatically from the

>server after a few days of their reception.

Also, in the article cited above

>OnionMail server saves messages and it automatically erases them after reading or if they have not been picked up by the user in a period of days, using the wipe command (Linux) to make forensic recovery impossible.

So, as far as I've understood, it's a Pond-ish service that forces users to issue their intra-service PGP keys (in order to store your mail asymmetrically encrypted and regardless of the fact that you're using OpenPGP in your mails) and it deletes periodically scrubs your mail folders.

>An OnionMail email inbox is encrypted with RSA/AES asymmetric encryption keys and user passwords, data is then hashed and scattered around multiple OnionMail servers in the network, if a server is seized no meaningful information or metadata can be obtained. Another security feature is the ability to remotely nuke a server’s digital certificate, this is useful if an administrator loses physical access to the server, OnionMail checks the legitimacy of digital certificates in the network and servers not using a valid one will be disconnected.

Is this perfection? Why I don't see this service advertised everywhere?




[Return][Go to top][Catalog][Post a Reply]
Delete Post [ ]
[]
[ home / board list / faq / random / create / bans / search / manage / irc ] [ ]