| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
a few were vulnerable according to cargo-audit, but none of it would've
mattered for us (probably). time is still vulnerable, but that really
doesn't matter.
|
| |
|
|
|
|
| |
upgrading dependencies will mean we have to use hyper for web-push
instead of isahc. sadly hyper doesn't send content-length headers for
empty bodies, but we can fudge that for the tests.
|
| | |
|
| |
|
|
|
|
| |
prompted by a cargo audit run. time works just as well and is better
maintained. web-push still uses chrono, but from the looks of things it
won't be affected.
|
| |
|
|
|
| |
we'll send mail so rarely, keeping a connection open at all times just
spams syslog
|
| |
|
|
|
|
|
|
| |
this is not so much a problem as a possible source of false security for
the readers. all secret keys we handle are serialized in some form, and
those serialization buffers are *not* zeroed out after use. zeroing our
raw buffers doesn't help much in that case, using a zero-on-free
allocator would be much more helpful.
|
| |
|
