Erick Tryzelaar

Ran into another case where this would be handy. I added a dependency on clippy and compiletest to aster. Both only compile on nightly, so to keep things building on...

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Hello @rohe: I'm slowly working on a PR. Current challenge is that xmlsec1 currently only allows passwords to be passed in on the commandline, or through an interactive prompt. The...

Unfortunately I don't actually know the state of python-xmlsec. It seems to have some fairly regular downloads (1289 in the past month), but I'm not personally familiar with the project.

Just to let you know, in Hue we've implemented a short term [solution](https://github.com/cloudera/hue/commit/961d43a5359a8d352e2d2324e282f1f7b1a6f397) in our fork of pysaml2. It decrypts the certificate in memory, then passes it to `xmlsec1` through...

@rohe: Yeah that would be the best solution. We thought though that we wouldn't have the time to validate saml using a new xmlsec library for our next release. Long...

I don't have firm opinions on this either (especially since I haven't actually had to use this library for real yet :) ). The main consequence would be that users...

For repositories like `FileSystemRepository`, I assume we don't need to check for trickle attacks, but do you think we ought to verify the hash on every read?

Circling back, yes we should verify the hash on every read in `FileSystemRepository`. On fuchsia, we store our trusted root in a read only location, so we can cryptographically verify...

This is mostly implemented. `TargetDescription`s now capture the target `custom` field. We just need to make `Client::fetch_target_description` public.