Git-Mirrors/RetroShare
1
0
Fork 0
mirror of https://github.com/RetroShare/RetroShare.git synced 2025-01-13 16:39:43 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

more notes on gixs and things to clarify

Browse Source 
git-svn-id: http://svn.code.sf.net/p/retroshare/code/branches/v0.5-new_cache_system@4847 b45a01b8-16f6-495d-af2f-9b41ad6348cc
This commit is contained in:
chrisparker126 2012-01-26 16:51:01 +00:00
parent a89c6fd08a
commit efddc9afab
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
libretroshare/src/gxs/rsgixs.h
View File

@ -31,13 +31,20 @@
#include <openssl/ssl.h> #include <openssl/ssl.h>
#include <set> #include <set>
/* /*!
* GIXP: General Identity Exchange Protocol. * GIXP: General Identity Exchange Protocol.
* *
* As we're always running into troubles with GPG signatures... we are going to * As we're always running into troubles with GPG signatures... we are going to
* create a layer of RSA Keys for the following properties: * create a layer of RSA Keys for the following properties:
* *
* 1) RSA Keys can be Anonymous, Self-Signed with Pseudonym, Signed by GPG Key. * 1) RSA Keys can be Anonymous, Self-Signed with Pseudonym, Signed by GPG Key.
* To clarify:
* a. This forms a layer of keys stay between GPG and pub/priv publish key ?
* b. Difference between anonymous and pseudonym keys?
* - Anonymous cannot be signed?
* -
* c. To some extent this determines security model of RsGeneralExchangeService
* - Anonymous & Pseudonym Keys will be shared network-wide (Hop by Hop). * - Anonymous & Pseudonym Keys will be shared network-wide (Hop by Hop).
- GPG signed Keys will only be shared if we can validate the signature - GPG signed Keys will only be shared if we can validate the signature
(providing similar behaviour to existing GPG Keys). (providing similar behaviour to existing GPG Keys).
@ -45,6 +52,8 @@
* 2) These keys can be used anywhere, specifically in the protocols described below. * 2) These keys can be used anywhere, specifically in the protocols described below.
* 3) These keys can be used to sign, encrypt, verify & decrypt * 3) These keys can be used to sign, encrypt, verify & decrypt
* 4) Keys will never need to be directly accessed - stored in this class. * 4) Keys will never need to be directly accessed - stored in this class.
* a. I guess can work solely through Id
* b. Use Case: Receivve a message, has a key id, request
* 5) They will be cached locally and exchanged p2p, by pull request. * 5) They will be cached locally and exchanged p2p, by pull request.
* 6) This class will use the generalised packet storage for efficient caching & loading. * 6) This class will use the generalised packet storage for efficient caching & loading.
* 7) Data will be stored encrypted. * 7) Data will be stored encrypted.