Conversation
|
@EnriqueL8 minor update |
|
@alex-semenyuk this is good but let's use this file https://github.com/LF-Decentralized-Trust/governance/blob/f0c1a4a6dfbef360ec92627d7e5003480b199195/tac/governing-documents/SAMPLE-SECURITY.md please |
SECURITY.md
Outdated
| The current Hyperledger Firefly security team is: | ||
|
|
||
| | Name | Email ID | Discord ID | Area/Specialty | | ||
| | ---------------- | ------------------ | ---------- | --------------- | |
There was a problem hiding this comment.
@EnriqueL8 Could you please help with filling this
There was a problem hiding this comment.
ah yeah okay, will raise at the community call to see who wants to be part of it. You can at least put my name down
There was a problem hiding this comment.
Maintainers please nominate yourselves to this!
@peterbroadhurst @awrichar @matthew1001 @Chengxuan
@alex-semenyuk - on the community call @SupernaviX volunteered for the Cardano connector
There was a problem hiding this comment.
Thanks for following up, @EnriqueL8
I can be for Tezos
EnriqueL8
left a comment
EnriqueL8
left a comment
There was a problem hiding this comment.
We discussed it in the community call that we should specify that if raised through GitHub it should be raised in the specific repository of the component where the vulnerability was found
Correct spelling to Hyperledger FireFly
| - Email the [LF Decentralized Trust Foundation security | ||
| list](mailto:security@lists.lfdecentralizedtrust.org): To report a security issue, please | ||
| send an email with the name of the project/repository, a description of the issue, the | ||
| steps you took to create the issue, affected versions, and if known, | ||
| mitigations. If in triaging the email, the security team determines the issue may be | ||
| a security vulnerability, a [GitHub security vulnerability report] will be | ||
| opened. |
There was a problem hiding this comment.
FYI @ryjones is this is still the correct process?
alex-semenyuk
force-pushed
the
update_security_md
branch
4 times, most recently
from
4fe1150 to
9884595
Compare
Signed-off-by: alexey semenyuk <alexsemenyuk88@gmail.com>
Signed-off-by: alexey semenyuk <alexsemenyuk88@gmail.com>
Signed-off-by: alexey semenyuk <alexsemenyuk88@gmail.com>
alex-semenyuk
force-pushed
the
update_security_md
branch
from
9884595 to
542158e
Compare
2 participants
Proposed changes
Update outdated SECURITY.md to sync with other LF repos, since some of links outdated. Also it helps to fix Security-Policy issue slightly improving score openssf scorecard
Types of changes
Please make sure to follow these points
Screenshots (If Applicable)
Other Information