-
Updated
Nov 8, 2020 - Python
encrypted
Here are 149 public repositories matching this topic...
-
Updated
Nov 9, 2020 - TypeScript
-
Updated
Nov 4, 2020 - JavaScript
-
Updated
Nov 6, 2020 - Go
For the feature Private key transfer #1090 you use Barcodes for verification.
Would it be a good idea to use the same way to verify Public key of contacts and mark this verificated users in contactlist with a green Icon or somewhat (similar to Threema )?
Maybe:
-yellow for "I'm not sure but I trust the key anyway and will verify it by our next beer."
-green for "I have scanned the code of m
Blocked by #2
-
Updated
Apr 11, 2018 - JavaScript
-
Updated
Jun 13, 2020 - JavaScript
-
Updated
Jul 24, 2020 - JavaScript
-
Updated
Oct 8, 2020 - Python
-
Updated
Aug 9, 2020 - PHP
-
Updated
Oct 8, 2017 - JavaScript
-
Updated
Jun 7, 2020 - C
-
Updated
Jul 7, 2020 - JavaScript
-
Updated
Mar 11, 2018 - C#
-
Updated
Oct 24, 2020 - Dockerfile
-
Updated
Oct 15, 2020 - Dockerfile
-
Updated
Aug 4, 2020 - C
-
Updated
Oct 29, 2020 - TypeScript
-
Updated
Oct 1, 2020 - Java
-
Updated
Feb 10, 2018 - PHP
Improve this page
Add a description, image, and links to the encrypted topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the encrypted topic, visit your repo's landing page and select "manage topics."
https://scotthelme.co.uk/a-new-security-header-feature-policy/
I guess it will be easy to add, because we certainly don't use any of these features.
Or maybe "gyroscope" or so may be used by the random number generator in sjcl, but that's all.