Aleksa Sarai

@alphapapa > Since this proposal apparently requires complete cooperation by server and client implementations, of which there are many, any uncooperative server or client could break the expectation that an...

@alphapapa > > i think that descoping the feature because of finding min_lifetime an unintuitive way of expressing "the minimum time to retain this data" is very much throwing the...

@jaromil What benefit does having an encrypted version of the header inside the encrypted data have? There still is a single point of failure because you can't read the encrypted...

I'm not convinced that making this the *default* setting is the best idea. Unprivileged user namespaces have been a source of kernel 0days quite a few times in recent years,...

I think having unprivileged user namespaces enabled *by distributions* is a good thing. The risk profile is different when it comes to containers. Being able to spawn an rootless container...

> I know. I didn't mean to imply you didn't know -- I was just mentioning it since I didn't know until I looked at the issue you linked. >...

This still needs some tests -- though I'm a little cautious about how we're going to test the seed values in a way that doesn't cause us problems in the...

As an update, it looks like old bash versions don't like the `arrays_equal` code. I will need to take a look at this...

@jasonkarns As far as I'm aware there aren't many other testing tools which provide something like this. @sublimino [mentioned this](https://github.com/bats-core/bats-core/issues/171#issuecomment-462130265) in #171. Ruby has `--seed` and random ordering is the...

I will go with `--random [SEED]` then. My point was that: > Virtually every testing tool that I'm aware of, which supports random execution, also supports re-running a prior random...