by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Zaki Manian
    @zmanian
    Might be a good example
    Tony Arcieri
    @tarcieri
    well, we did, until that was implicated in several deadlocks and I ripped it out...
    Zaki Manian
    @zmanian
    Oh
    (Charles_K)
    @charleschege
    @tarcieri I am building an authentication system and I want to save time as TAI64 since I don't care about leap seconds or the time being human readable. Chrono is really big time library and I want something small so Tai64 crate seems like a good candidate. However, when I try to use it with Secrecy::Secret, it errors out with zeroize not implemented for Tai64N, I don't want time to be accessible from the console via debug, so is implementing Zeroize for Tai64 a good idea? Can the feature be added to the Tai64 crate?
    Tony Arcieri
    @tarcieri
    sure, and yes
    just add a zeroize feature to tai64
    i.e. add zeroize as an optional dependency
    (Charles_K)
    @charleschege
    @tarcieri I have implemented the zeroize feature, all checks have passed except the code coverage one, I am unable to solve that and would like some help
    (Charles_K)
    @charleschege
    @tarcieri I have a project that requires a value to be hashed into a hashmap, but the value is of secrecy::Secret<T>. Would there be a security problem if I implement Hash for Secret<T>?
    Tony Arcieri
    @tarcieri
    that’s a tricky question, as used incorrectly it could leak information about the secret. Ditto for Ord
    something like DebugSecret that marks the underlying impl does constant-time comparisons or hashing could work
    Santiago Torres
    @SantiagoTorres
    hey, I've been trying zero-out the emmc on an usbarmory by following the instructions in here https://github.com/iqlusioninc/usbarmory.rs/tree/develop/firmware/usbarmory#setting-up-an-emmc-boot
    for some reason minicom doesn't seem to be working (on this line minicom -b 115200 -D /dev/ttyUSB2), I don't get any echo back. I wonder what'd be a good place to start debugging my situation
    Zaki Manian
    @zmanian
    Hi!
    Santiago Torres
    @SantiagoTorres
    zmanian: hey! :D
    Zaki Manian
    @zmanian
    So one thing is the the basic examples with the USB runner will work without zeroing the eMMC if it’s a fresh from box device
    Santiago Torres
    @SantiagoTorres
    I'm still rather worried that I may not have been setting the debugger dongle properly :(
    Santiago Torres
    @SantiagoTorres
    I'm starting to think that my u-boot build is proabbly what's bork
    Zaki Manian
    @zmanian
    So one thing we’ve found with the debugger board is on cold boot it take 500ms to warm up
    So I spent a very frustrating weekend debugging not getting debugger board output
    One thing to try is just doing the rust blink example
    We are right in the middle of this big Game of Zones project
    Will have more time to help you mid week
    Santiago Torres
    @SantiagoTorres
    okido, thanks! I'll try to do blinky then
    Santiago Torres
    @SantiagoTorres
    woot, blinky works :)
    yeah, I assume that the hello, world! should be read from the UART, but I can't see anything :/
    Tony Arcieri
    @tarcieri
    yeah, we had some odd problems with it on MacOS
    you're on Linux?
    Santiago Torres
    @SantiagoTorres
    yup, arch on 5.6.8
    I've been trying to sniff on usbmon to see if there's traffic and there's defo sth going on
    Santiago Torres
    @SantiagoTorres
    I kinda wonder if it's one of those "cheap microusb cable is adding noise and breaking things" situations
    Zaki Manian
    @zmanian
    @SantiagoTorres if you drop a delay into hello world it should work
    Santiago Torres
    @SantiagoTorres
    zmanian: oh, let me try that one out
    Zaki Manian
    @zmanian
    this is just the warmup period on the debug board
    Santiago Torres
    @SantiagoTorres
    ah, I thought that was what COLD_BOOT=1 was doing no?
    I'll try it out anyway soon :)
    Santiago Torres
    @SantiagoTorres
    silly question, Ijust noticed this is a no_std crate. Any way to add the delay other than thread::sleep? :P
    Santiago Torres
    @SantiagoTorres
    ah nevermind, found it in the usbarmory crate
    this is basically the changes I'm doing to the hello world example: https://paste.xinu.at/zHngY/
    Zaki Manian
    @zmanian
    yes that should work!
    does it?
    Santiago Torres
    @SantiagoTorres
    you won't believe this but
    if you plug the debug board upside down it works
    did I miss some crucial documentation on board orientation?
    Santiago Torres
    @SantiagoTorres
    ah, and apparently either they changed the settings or the minirc config file as described wasn't being duplex. SO things were working all along :/ picocom seems to be working over here. Sorry for al the spam
    Zaki Manian
    @zmanian
    I think we mention the board orientation thing in the docs
    but yeah it's a thing
    Santiago Torres
    @SantiagoTorres
    Yeah I only found reference to it here https://github.com/f-secure-foundry/usbarmory/tree/master/hardware/mark-two-debug-accessory but I may have missed it as well on the usbarmory.rs repo