Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tony Arcieri
    @tarcieri
    if you have ideas, by all means
    Carl Wallace
    @carl-wallace
    i forgot about the yubihsm-shell. will give a look there to see how it works. i had worked up the skeleton of the yubico-piv-tool in structopt. i need to see what of that could move over to gumdrop (like list of permitted slots, enums corresponding to parameters, etc)
    Tony Arcieri
    @tarcieri
    all of those work in gumdrop, although not necessarily the same way as structopt
    structopt is kind of… messy… and permits things that don’t necessarily have a valid mapping to Rust syntax
    so I’d need to see what you had in mind
    but otherwise a certificate read (or cert read), cert import, cert delete set of subcommands
    Tony Arcieri
    @tarcieri
    separately something I’ve been thinking about is a flag for testing destructive changes...
    live against a YubiKey that is
    perahps an environment variable?
    YUBIKEY_PIV_DESTRUCTIVE_TESTS=true or something like that?
    str4d
    @str4d
    That seems more reasonable than just relying in --ignored
    e.g. the generate_* tests I added will happily overwrite whatever key is in the first retired slot
    Side-track: signatory 0.17 is out and I see tendermint/signatory#180 is still open (and a problem). @tarcieri would you like me to make a PR?
    Tony Arcieri
    @tarcieri
    yeah, which was fine for me because I didn’t care
    and damn, yeah sure
    maybe I should just flip it over to use GitHub Actions
    lack of Windows CI is annoying
    str4d
    @str4d
    tendermint/signatory#187
    Tony Arcieri
    @tarcieri
    cool
    I can release a v0.17.1 with that
    tarcieri @tarcieri nukes ancient rand from dev-dependencies :sweat_smile:
    str4d @str4d is just checking it does fix the problem
    str4d
    @str4d
    https://github.com/str4d/ire/pull/74/checks?check_run_id=350838263
    Tony Arcieri
    @tarcieri
    that’s with the git version?
    str4d
    @str4d
    Yes, PR is patched to current develop HEAD
    Huh
    Tony Arcieri
    @tarcieri
    different file :weary:
    pkcs8.rs
    str4d
    @str4d
    Argh
    I'll make a new signatory branch and run my PR against it until it passes
    Tony Arcieri
    @tarcieri
    haha ok
    I should really flip Signatory over to GitHub actions
    I say again, lol
    this is annoying
    str4d
    @str4d
    Woop, that was the only other problem
    @tarcieri tendermint/signatory#188
    Tony Arcieri
    @tarcieri
    cool
    I’ll cut a release and poke at flipping it over to Actions
    @str4d ok merged. if you can confirm it’s fixed I’ll cut another release
    str4d
    @str4d
    https://github.com/str4d/ire/pull/74/checks?check_run_id=350938440 is running
    with signatory patched to bfcf85d
    Tony Arcieri
    @tarcieri
    cool
    str4d
    @str4d
    Looks like it passes!
    Tony Arcieri
    @tarcieri
    woop
    ok will cut a new release
    Tony Arcieri
    @tarcieri
    @str4d it’s out: https://crates.io/crates/signatory/0.17.1
    on a completely different matter...
    @str4d it’d be cool if name here were Option<&’a str>
    here, that is https://github.com/str4d/x509.rs/blob/master/src/lib.rs#L136
    and if it were, omit CN entirely