Firstyear
Firstyear
This has been on my radar for a bit. I have "ideas" about how to do this right :)
Well, it's worse than that, it actually crould introduce DB/schema/other corruption. We need to actually refuse to run/open the db while another proc has it open.
Backups are done in a read-txn so we don't need exclusive mode. The main issue here is what happens across a container boundary or similar. Also what happens in a...
there may actually be a way to do this, so we don't block at all, but the run of the admin tool can indicate in the DB that the next...
We need to actually rewrite the error handling around passwords because internally we get details from zxcvbn about this. We could apply the same rules client side so that we...
Hmmm ... that's a good point. That a future account policy setting may affect those requirements. I'm a bit unsure about how far I want to go down that route...
@yaleman Isn't this kind of done now? We can certainly polish it, but it's all in place.
Yeah, we can probably implement std::fmt::Display for this to make it more human?
Yeah, ssh certs is an option as well, but there are different requirements there. I do want ssh certs of course! I think that the ssh certs are a bit...
Saying that maybe it's better to focus on ssh certs long run so I'll close this ...