Timeline for Update URL over HTTP
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2020 at 12:24 | comment | added | Seraphim's host | "... it allows caching of the file by content distributors" thanks, now I know something new! | |
| Oct 9, 2020 at 12:22 | vote | accept | Seraphim's host | ||
| Oct 9, 2020 at 12:16 | answer | added | A. Hersean | timeline score: 3 | |
| Oct 9, 2020 at 12:15 | history | edited | schroeder♦ | CC BY-SA 4.0 |
added 1 character in body; edited tags; edited title
|
| Oct 9, 2020 at 11:58 | comment | added | A. Hersean | It depends if the downloaded file is signed with it's metadata (version number). Using HTTP to distribute signed updates is common because it allows caching of the file by content distributors. So, the real question is: is the update signed? And is the associated metadata signed with it (to avoid rollback to a previous vulnerable version)? | |
| Oct 9, 2020 at 11:51 | history | asked | Seraphim's host | CC BY-SA 4.0 |