yves/meowlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

request jobs generation
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
ycc
2024-01-12 23:17:34 +01:00
parent a9f3b548e5
commit 48b2e78b41
5 changed files with 442 additions and 285 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/meow.tex
View File

@ -46,7 +46,13 @@ Some of them might be marked as trusted.
Random delays and random payload padding might be set for each forwarding step, making the overall message tracking much more difficult, even for organizations having capabilities of global network surveillance.
It is strongly advised to use trusted servers as your first node and message server (the one that holds your incoming messages).
\subsubsection{Presence protocol for direct messaging}
\subsubsection{Message lookup obfuscation}
Your device will request for messages using conversation keys on a very regular basis to youy messaging(s) server(s).
The device will check for conversation keys for all your contacts. If you check that option, it will also check for hidden contact keys.
In case of data interception on your device link, in order to prevent statistical analysis, every request might be answered with random data.
Moreover, some random keys will be added to your requests list.
\subsubsection{Presence protocol for direct messaging TBC}
A presence service associating your conversation keys to your IP address for direct peer to peer connection is also provided.
The presence protocol is simply activated by setting a flag in the message poll requests.
If that flag is set, your encrypted IP will be published on the server, allowing your only your peer(s) to decrypt it and directly communicate with your terminal.