Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Jan 26, 2014, 1:51:15 AM (10 years ago)
- Author:
-
elb
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v4
|
v5
|
|
| 20 | 20 | * '''Strong authentication.''' All data exchanged via the protocol should have strong authentication. Not all data may be encrypted, but all data should be authenticated. |
| 21 | 21 | * '''Perfect forward secrecy.''' Whether this is for all messages, each session, or exactly what level of granularity needs to be determined. |
| | 22 | * '''Algorithmic flexibility.''' Cryptographic techniques evolve, computing power increases, and needs change. Some sort of algorithm naming protocol (such as used by TLS or PGP) is necessary for future-proofing and tailoring protection to the data being protected. |
| 22 | 23 | * '''XMPP Presence integration.''' This means that XMPP presence stanzas for a client supporting the protocol should provide, at a minimum: |
| 23 | 24 | * Notification that the client supports e2e encryption |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!
