kev/Onionr
1
0
Fork 0
Code Issues 24 Pull Requests Projects Releases 2 Wiki Activity

Merge branch 'master' of github.com:beardog108/onionr into crypto

Browse Source
This commit is contained in:
Kevin Froman 2018-02-17 13:04:22 -06:00
commit 1ae570bd70
2 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
ISSUE_TEMPLATE.md Normal file
View File

@ -0,0 +1,12 @@
# Expected Behavior
# Actual Behavior
# Steps to Reproduce
# Version Information
Onionr:
OS:
Python:
Tor:
I2P:

7
docs/onionr-draft.md
View File

@ -4,9 +4,6 @@ A social network/microblogging platform for Tor & I2P
Draft Dec 25 2017 Draft Dec 25 2017
notes:
Use Blowfish in addition with AES?
# Overview # Overview
Onionr is an encrypted microblogging & mailing system designed in the spirit of Twitter. Onionr is an encrypted microblogging & mailing system designed in the spirit of Twitter.
@ -33,7 +30,7 @@ Clients MUST use HTTP(s) to communicate with one another to maintain compatibili
## Connections ## Connections
When a node first comes online, it attempts to bootstrap using a default list provided by a client. When a node first comes online, it attempts to bootstrap using a default list provided by a client.
When two peers connect, they exchange PGP public keys and then generate a shared AES-SHA3-512 HMAC token. These keys are stored in a peer database until expiry. When two peers connect, they exchange PGP public keys and then generate a shared AES-SHA3-512 HMAC token. These keys are stored in a peer database until expiry.
HMAC tokens are regenerated either every X many communications with a peer or every X minutes. Every 10 communications or every 24 hours is a recommended default. HMAC tokens are regenerated either every X many communications with a peer or every X minutes. Every 10MB or every 2 hours is a recommended default.
All valid requests with HMAC should be recorded until used HMAC's expiry to prevent replay attacks. All valid requests with HMAC should be recorded until used HMAC's expiry to prevent replay attacks.
Peer Types Peer Types
* Friends: * Friends:
@ -64,7 +61,7 @@ Clients MUST use HTTP(s) to communicate with one another to maintain compatibili
◦ Posts MUST be PGP signed, and MUST NOT use any encryption. ◦ Posts MUST be PGP signed, and MUST NOT use any encryption.
## Private Messages ## Private Messages
Private messages are messages that can have attached images. They MUST be encrypted via AES256-HMAC-SHA256 and PGP signed (signed before encryption) and time stamped to prevent replaying. A temporary RSA key for use in every message is exchanged every X many configured messages (or posts), for use in addition with PGP and the HMAC. Private messages are messages that can have attached images. They MUST be encrypted via AES256-HMAC-SHA256 and PGP signed (signed before encryption) and time stamped to prevent replaying. A temporary EdDSA key for use in every message is exchanged every X many configured messages (or posts), for use in addition with PGP and the HMAC.
When both peers are online messages SHOULD be dispatched directly between peers. When both peers are online messages SHOULD be dispatched directly between peers.
All messages must be verified prior to being displayed. All messages must be verified prior to being displayed.