David Lawrence cb2dd07edc the server was not setting the longer snapshot expiry time. When generating a timestamp it was also retriving the snapshot directly from the database and only validating the checksum still matched what was in the timestamp. Due to the addition of consistent downloads, this mean a new snapshot never got generated. It is necessary for GetOrCreateTimestamp to call GetOrCreateSnapshot to ensure a new snapshot is generated as and when required ... Signed-off-by: David Lawrence <david.lawrence@docker.com> (github: endophage)		2016-02-24 15:51:31 -08:00
..
errors	Pass original invalid version storage error details into standardized errors	2016-01-14 09:57:36 -08:00
handlers	changing API for updating delegations	2016-02-23 11:57:08 -08:00
snapshot	Revert "switching out to consistently use canonical json for all marshalling of TUF data"	2016-01-08 14:53:09 -08:00
storage	cleaning up logging	2016-01-24 10:38:55 -08:00
timestamp	the server was not setting the longer snapshot expiry time. When generating a timestamp it was also retriving the snapshot directly from the database and only validating the checksum still matched what was in the timestamp. Due to the addition of consistent downloads, this mean a new snapshot never got generated. It is necessary for GetOrCreateTimestamp to call GetOrCreateSnapshot to ensure a new snapshot is generated as and when required	2016-02-24 15:51:31 -08:00
integration_test.go	completely removing KeyDB	2016-02-16 21:11:13 -08:00
server.go	the server was not setting the longer snapshot expiry time. When generating a timestamp it was also retriving the snapshot directly from the database and only validating the checksum still matched what was in the timestamp. Due to the addition of consistent downloads, this mean a new snapshot never got generated. It is necessary for GetOrCreateTimestamp to call GetOrCreateSnapshot to ensure a new snapshot is generated as and when required	2016-02-24 15:51:31 -08:00
server_test.go	update metrics endpoint	2016-02-02 09:52:43 -08:00