| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
local mail connections are much preferred for this service, and those
needn't be encrypted.
|
| |
|
|
|
| |
not necessary for the standalone server, but if we want to launch many
server for testing it'll be relevant.
|
| |
|
|
| |
u8 arrays are copy, no need to not have our wrappers be copy.
|
| |
|
|
| |
the trait doesn't leave the module, so sealing doesn't do anything useful.
|
| |
|
|
|
| |
there's no benefit to keeping it around, the zeroing behavior it had was
never any good and without it it's just a fancy [u8; N]
|
| | |
|
| |
|
|
| |
the db already does this, crypto did not.
|
| |
|
|
| |
using SecretBytes for all of them isn't that great.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
it never worked out, but a bit of support stuff remained.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
these are not "official" test vectors, just an example of what the
implementation does currently. since it works with other parts of the
ecosystem (most importantly firefox itself) they seem good enough to
include.
|
| |
|
|
|
| |
this doesn't do much for performance, but it does allow running the
tests with a simple `cargo t`.
|
| | |
|
| |
|
|
|
|
|
| |
firefox wants to delete profile access tokens after they're expired and
logs errors if it can't do that. since this happens every hour we can
end up with a bunch of error logs very quickly, so we better let it do
what it wants.
|
| |
|
