Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

✨ Feature Suggestion | Link independent security audits to tools #1071

Open
3 of 6 tasks
nitrohorse opened this issue Aug 1, 2019 · 6 comments
Open
3 of 6 tasks

Comments

@nitrohorse
Copy link
Contributor

nitrohorse commented Aug 1, 2019

Description:

From @Mikaela on Wire's PTIO group:

Should we list independent security audits either in a separate file like source_code.md or together with the tools?

Related to: https://github.com/privacytoolsIO/privacytools.io/issues/753

From the comments:

@Mikaela
Copy link
Contributor

Mikaela commented Aug 1, 2019

IPFS mirror of the Keybase audit https://ipfs.privacytools.io/ipfs/QmSuz9YGsCuAvFzsqFZoRaQ9ejtgojrmbq7RtQN27qHCu8/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf

@Mikaela
Copy link
Contributor

Mikaela commented Aug 1, 2019

@nitrohorse
Copy link
Contributor Author

@Mikaela
Copy link
Contributor

Mikaela commented Aug 11, 2019

Maybe some of them can be put into related information in the IM page?

@Mikaela
Copy link
Contributor

Mikaela commented Aug 12, 2019

I am going to take part of this as per my previous comment, together with #1137 and #967.

@nitrohorse
Copy link
Contributor Author

Maybe some of them can be put into related information in the IM page?

Yeah I’m wondering how we should link to these from their listings... as a badge?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants