Guest
Login
Register
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email
?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Menu
Home
Help
Login
Register
BitShares Forum
/
Main
/
General Discussion
/
Critical Issues Report Procedure
« previous
next »
Print
Pages: [
1
]
Go Down
Author
Topic: Critical Issues Report Procedure (Read 1212 times)
0 Members and 1 Guest are viewing this topic.
August 22, 2014, 03:48:47 pm
Reply
#3
bytemaster
Hero Member
Posts: 9840
BitShares:
bytemaster
GitHub:
http://www.github.com/bytemaster
Re: Critical Issues Report Procedure
For now you can just email us directly. If it is severe enough that you think someone scanning our email will pick up on the attack and execute it, then let us know and we will figure out a secure channel.
Logged
For the latest updates checkout my blog:
http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else. These are merely my opinions and I reserve the right to change them at any time.
August 22, 2014, 02:53:17 pm
Reply
#2
xeroc
Board Moderator
Hero Member
Posts: 12922
ChainSquad GmbH
BitShares:
xeroc
GitHub:
xeroc
Re: Critical Issues Report Procedure
publishing a PGP key would be nice ...
non registered yet for bitshares.org
http://pgp.mit.edu/pks/lookup?search=bitshares.org&op=index
Logged
August 22, 2014, 02:50:06 pm
Reply
#1
emski
Hero Member
Posts: 1282
Critical Issues Report Procedure
Now that a lot of stake depends on bitshares toolkit what if someone finds a critical issue that shouldn't be discussed in the forum.
Should some of developers provide keys in order to receive encrypted high-severity issues?
Is there an alternative plan?
Logged
https://bitsharestalk.org/index.php/topic,9857.0.html
Print
Pages: [
1
]
Go Up
« previous
next »
BitShares Forum
/
Main
/
General Discussion
/
Critical Issues Report Procedure