1. 07 9月, 2017 3 次提交
  2. 29 8月, 2017 1 次提交
  3. 26 8月, 2017 1 次提交
  4. 24 8月, 2017 1 次提交
  5. 16 8月, 2017 5 次提交
  6. 07 8月, 2017 1 次提交
  7. 02 8月, 2017 1 次提交
  8. 01 8月, 2017 1 次提交
  9. 28 7月, 2017 1 次提交
    • N
      Ref #2, #7: Progress towards authorizing transactions · 67c9b8b4
      Nathan Hourt 提交于
      As of now, almost all the ingredients are in place for authorizing
      transactions. We check that the transaction bears signatures sufficient to
      satisfy its declared authorizations, and as we execute the transaction,
      we ensure that the declared authorizations are sufficient to satisfy the
      authorizations required by executing the message handlers, and we ensure
      that all of the transaction's declared authorizations were used.
      
      What's not done:
       - Detecting/rejecting duplicate signatures and unnecessary signatures
       - Choosing the correct permission level when a message handler requires
      an authorization
      
      Choosing the correct permission level is the big ticket item. To
      implement this, we need to implement a missing chunk of system contract
      functionality, specifically around defining links from a user's
      permissions tree to contracts and message types.
      67c9b8b4
  10. 26 7月, 2017 3 次提交