Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a new section for operational security best practices. #113

Closed
maurelian opened this issue Nov 14, 2017 · 12 comments
Closed

Add a new section for operational security best practices. #113

maurelian opened this issue Nov 14, 2017 · 12 comments
Labels
help wanted opsec For Operation Security section To Do

Comments

@maurelian
Copy link
Contributor

ISSUE: There are many security consideration outside of programming and architecture, which are not covered here.

PR REQUEST: A new section should be created (including modifying the [yaml config(https://github.com/ConsenSys/smart-contract-best-practices/blob/master/mkdocs.yml)), which presents the various operational considerations necessary when deploying a contract system.

These include existing issues:

[] #92
[] #85
[] #79
[] #97

As well as:
[] proper cold storage for critical private keys
[] possible recommendations for M and N on a multisig wallet
[] other

@gitcoinbot
Copy link

This issue now has a funding of 0.3 ETH (98.15 USDT) attached to it. To view or claim this funding, click here.

@owocki
Copy link

owocki commented Dec 4, 2017

hey @maurelian did you want me trying to source this still? i see the bounty has expired.. so you now has the option to clawback the funds or to just keep it open (and ill continue looking for someone to help)

@maurelian
Copy link
Contributor Author

I'd like to claw it back. This task was too open ended.

Unfortunately, I can't see how to do that.

@owocki
Copy link

owocki commented Dec 20, 2017

@maurelian no problem. just sent you the clawback link on slack.

@owocki
Copy link

owocki commented Jan 2, 2018

hey @maurelian happy new years :) let me know if you got that clawback link and if you need any help :)

@KevinSmall
Copy link

is this one still available? It says status = active, but expired = 1 month ago (and from comments above it looks closed)

@maurelian
Copy link
Contributor Author

It's available on a voluntary basis only now.

@gitcoinbot
Copy link

The funding of 0.3 ETH (291.99 USD) attached to this issue has been approved & issued .

@owocki
Copy link

owocki commented Jan 17, 2018

Please disregard the message from Gitcoinbot above.. The bounty was killled, not approved.

@mimoo
Copy link

mimoo commented Mar 13, 2018

It should probably have a mention about contract audits.

@shayanb shayanb added the To Do label Jan 24, 2019
@shayanb
Copy link
Contributor

shayanb commented Jan 24, 2019

Also:

@shayanb shayanb added the opsec For Operation Security section label Jan 24, 2019
@maurelian
Copy link
Contributor Author

Current Modus Operandi is to reduce scope and improve the core content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted opsec For Operation Security section To Do
Projects
None yet
Development

No branches or pull requests

6 participants