vikarti.anatra/safing-web
1
0
Fork 0
mirror of https://github.com/safing/web synced 2025-09-01 10:39:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fix typos

Browse source
This commit is contained in:
davegson 2020-07-31 15:51:14 +02:00
parent 8043b057f2
commit 7b5a9a41f2
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
_posts/2020-07-31-progress-update-july.html
View file

@ -64,7 +64,7 @@ cards:
- type: 'h3'
text: Code Audit By Cure53
- type: p
text: "Back in January we paid some of the best in the field to audit our cryptographic library. Their insight and expertise challenged us, in a very good way. The foundation was solid, but it was clear we improve things here and there. During these months, we could progress our cryptography library into what it is now. This module is complete, but also added workload to the timeline."
text: "Back in January we paid some of the best in the field to audit our cryptographic library. Their insight and expertise challenged us, in a very good way. The foundation was solid, but it was clear we could improve things here and there. During these months, we could progress our cryptography library into what it is now. This module is complete, but also added workload to the timeline."
- type: a
text: View Cure53's audit report
- type: br
@ -73,9 +73,9 @@ cards:
- type: 'h3'
text: Refactoring The Gossiping
- type: p
text: "Instead of sending all data from servers to clients, we decided to split the messages into a \"big message\" and a \"small message\". The big message is sent on setup and contains the servers public key and lots of meta-data. The small message contains the servers active links to other nodes and its most current ephemeral keys (for 0-RTT perfect forward & backward secrecy connections). The small message will communicate with clients regularly while the big message will be sent less frequent to prevent unnecessary communication. Naturally, this provided a big refactor and a delay in timeline."
text: "Instead of sending all data from servers to clients, we decided to split the messages into a \"big message\" and a \"small message\". The big message is sent on setup and contains the servers public key and lots of meta-data. The small message contains the servers active links to other nodes and its most current ephemeral keys (for 0-RTT perfect forward & backward secrecy connections). The small message will communicate with clients regularly while the big message will be sent less frequent to prevent unnecessary communication. Naturally, this resulted in a big refactor and a delay in timeline."
- type: p
text: This module is nearly done as well, just a few polishes here and there as well as some more integrations are needed to wrap this up.
text: This module is nearly done as well, just a few polishes here and there as well as some more integration tests are needed to wrap this up.
- type: a
text: View the Pull Request of this refactor
- type: 'h3'