fr33domlover 4053f2f2b4 Record usage of instance keys in the DB ... When we verify an HTTP signature, * If we know the key, check in the DB whether we know the actor lists it. If it doesn't, and there's room left for keys, HTTP GET the actor and update the DB accordingly. * If we know the key but had to update it, do the same, check usage in DB and update DB if needed * If we don't know the key, record usage in DB However, * If we're GETing a key and discovering it's a shared key, we GET the actor to verify it lists the key. When we don't know the key at all yet, that's fine (can be further optimized but it's marginal), but if it's a key we do know, it means we already know the actor and for now it's enough for us to rely only on the DB to test usage.		2019-02-19 10:54:55 +00:00
..
2016_08_04.model	Complete DB migration list, allowing to upgrade 2016-08-04 running instance	2018-03-27 14:28:56 +00:00
2016_09_01_just_workflow.model	Remove scope field from 2016_09_01 migration model, it didn't exist yet	2018-04-05 00:02:12 +00:00
2016_09_01_rest.model	Complete DB migration list, allowing to upgrade 2016-08-04 running instance	2018-03-27 14:28:56 +00:00
2019_01_28_project_collabs.model	Default roles for repos and turn user/anon collab tables into proj/repo fields	2019-01-29 22:24:32 +00:00
2019_02_03_verifkey.model	Record usage of instance keys in the DB	2019-02-19 10:54:55 +00:00