Skip to content

Commit

Permalink
Merge pull request WebOfTrust#897 from SmithSamuelM/main
Browse files Browse the repository at this point in the history
Some minor cleanup typos comments
  • Loading branch information
SmithSamuelM authored Dec 3, 2024
2 parents 7737bfd + 4028b58 commit e8dc2b4
Show file tree
Hide file tree
Showing 4 changed files with 13 additions and 5 deletions.
2 changes: 1 addition & 1 deletion src/keri/core/coring.py
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@ class MatterCodex:
Big: str = 'N' # Big 8 byte b2 number
X25519_Private: str = 'O' # X25519 private decryption key/seed, may be converted from Ed25519
X25519_Cipher_Seed: str = 'P' # X25519 sealed box 124 char qb64 Cipher of 44 char qb64 Seed
ECDSA_256r1_Seed: str = "Q" # ECDSA secp256r1 256 bit random Seed for private key
ECDSA_256r1_Seed: str = 'Q' # ECDSA secp256r1 256 bit random Seed for private key
Tall: str = 'R' # Tall 5 byte b2 number
Large: str = 'S' # Large 11 byte b2 number
Great: str = 'T' # Great 14 byte b2 number
Expand Down
8 changes: 4 additions & 4 deletions src/keri/core/eventing.py
Original file line number Diff line number Diff line change
Expand Up @@ -2710,19 +2710,19 @@ def validateDelegation(self, serder, sigers, wigers, wits, delpre, *,
to detect a comprimised or duplicitious superseding rotation and
prevent the additional verification from proceding.
ToDo:
Mitigations of malicious source seal couples:
Repair the approval source seal couple in the 'aess' database on recursive
climb the kel tree. Once an event has been accepted into its kel.
Later adding a source seal couple to 'aes' should then be OK from a
security perspective since its only making discovery less expensive.
When malicious source seal couple is received but event is validly
delegated and the delegation source seal is repaired then need to replace
When a malicious source seal couple is received but event is validly
delegated and the delegation source seal is repaired then replace
malicious source seal couple with repaired seal so repaired seal not
malicous seal gets written to 'aes' db. When the event is valid but
non-delegated then need to nullify malicous source seal couple so it
does not get written to 'aes' datable
does not get written to 'aes' database.
"""
if not delpre: # not delegable so no delegation validation needed
Expand Down
3 changes: 3 additions & 0 deletions src/keri/db/basing.py
Original file line number Diff line number Diff line change
Expand Up @@ -1022,6 +1022,9 @@ def reopen(self, **kwa):
self.udes = subing.CatCesrSuber(db=self, subkey='udes.',
klas=(coring.Seqner, coring.Saider))
self.uwes = self.env.open_db(key=b'uwes.', dupsort=True)
#self.uwes = subing.CatCesrIoSetSuber(db=self, subkey='uwes.',
#klas=(coring.Saider, indexing.Siger))

self.ooes = self.env.open_db(key=b'ooes.', dupsort=True)
self.dels = self.env.open_db(key=b'dels.', dupsort=True)
self.ldes = self.env.open_db(key=b'ldes.', dupsort=True)
Expand Down
5 changes: 5 additions & 0 deletions src/keri/db/subing.py
Original file line number Diff line number Diff line change
Expand Up @@ -43,10 +43,15 @@
ordinal number so that the ordering within each key prefix is monotonically
increasing numeric
B64Suber provides separated fields of B64 primitives for values. Useful when don't
need to CESR ser/des the primitives or performance
The term 'set' of values means that no value may appear more than once in the set.
Sets support idempotent adds and puts to db. This means one can add or put the same
(key, val) pair multiple times and not change the db.
DupSuber provides set of lexicographic ordered values at each key. Each value has
a limited size (key + value <= 511 byes). The set is performant. Good for indices.
Expand Down

0 comments on commit e8dc2b4

Please sign in to comment.