Viewing a response to: @stoodkev/re-fr3eze-re-yabapmatt-steemits-security-values--how-steem-keychain-can-help-20190123t105051321z
Active key transaction is exactly what I meant actually. What was the concern not to allow whitelisting transaction that requires actuve permission? I understand user's fund maybe at stake and that might sounds like posting a risk to the real money. But at least provide an option for those who would like to whitelist that kind of operation? That would really helps the mass adoption of Steem especially in the DAPP like dice game. And that to me is the final form how Keychain should be like. Users get to customize it to their most convenience. Posted using [Partiko Android](https://steemit.com/@partiko-android)
| author | fr3eze |
|---|---|
| permlink | fr3eze-re-stoodkev-re-fr3eze-re-yabapmatt-steemits-security-values--how-steem-keychain-can-help-20190123t150827024z |
| category | steemit |
| json_metadata | {"app":"partiko","client":"android"} |
| created | 2019-01-23 15:08:27 |
| last_update | 2019-01-23 15:08:27 |
| depth | 3 |
| children | 2 |
| last_payout | 2019-01-30 15:08:27 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 619 |
| author_reputation | 62,201,653,753,684 |
| root_title | "Steemit's Security Values & How Steem Keychain Can Help" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 78,818,641 |
| net_rshares | 0 |
A website whitelisted to use active authority by a user could, if falling into wrong hands : - Instantly steal all of the user's liquid assets - Broadcast an account update that would change the private keys and therefore take control of the account - Initiate power down, etc. I think the tradeoff between security and convenience is too big here, thats why we only authorize listing for actions requiring posting authority, since they don t have a direct impact on stake.
| author | stoodkev |
|---|---|
| permlink | re-fr3eze-fr3eze-re-stoodkev-re-fr3eze-re-yabapmatt-steemits-security-values--how-steem-keychain-can-help-20190123t163058571z |
| category | steemit |
| json_metadata | {"tags":["steemit"],"app":"steemit/0.1"} |
| created | 2019-01-23 16:31:00 |
| last_update | 2019-01-23 16:31:00 |
| depth | 4 |
| children | 1 |
| last_payout | 2019-01-30 16:31:00 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 475 |
| author_reputation | 190,283,772,273,558 |
| root_title | "Steemit's Security Values & How Steem Keychain Can Help" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 78,822,410 |
| net_rshares | 0 |
>the tradeoff between security and convenience is too big I agree and they are all valid concerns. But you can still offer user the ability to decide whether they are willing to go for the tradeoff or not. Maybe the whitelisting process can be more hidden in the setting or put up a significant warning sign in the whitelist page for active authority. Option are tons.
| author | fr3eze |
|---|---|
| permlink | re-stoodkev-re-fr3eze-fr3eze-re-stoodkev-re-fr3eze-re-yabapmatt-steemits-security-values--how-steem-keychain-can-help-20190124t015842000z |
| category | steemit |
| json_metadata | {"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["steemit"],"users":[],"links":[],"image":[]} |
| created | 2019-01-24 01:58:45 |
| last_update | 2019-01-24 01:58:45 |
| depth | 5 |
| children | 0 |
| last_payout | 2019-01-31 01:58:45 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 370 |
| author_reputation | 62,201,653,753,684 |
| root_title | "Steemit's Security Values & How Steem Keychain Can Help" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 78,845,169 |
| net_rshares | 0 |
hiveblocks