diagprov

@diagprov

Software/Security engineer . Mathematician, Cryptology. 🇬🇧 in 🇨🇭. Personal account. EN|FR|DE. DMs open.

Switzerland
Vrijeme pridruživanja: srpanj 2018.

Tweetovi

Blokirali ste korisnika/cu @diagprov

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @diagprov

  1. prije 3 sata
    Poništi
  2. proslijedio/la je Tweet
    prije 6 sati

    new post about E4's cryptography, answering questions such as: - why AES SIV and not GCM? - why SHA-3 and not BLAKE2? - what about side channels? - how are keys stored? etc.

    Poništi
  3. prije 11 sati

    "We would like to take this opportunity to offer support" "Sorry your studies were disrupted this year. You're now required to do the same amount of work in less time. Btw our exam period is 4 days long so we have some schedule clashes, 7 hour exam is fine yeh?"

    Prikaži ovu nit
    Poništi
  4. prije 11 sati

    University: We're aware you're having difficulties and will support you in your studies! University automated email: you are no longer allowed to study with us unless you explain how you will succeed in your studies, please see regulation 12F.e3b.

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    1. velj

    some weekend blogging of a quick comparison of Docker /Podman operations

    Poništi
  6. proslijedio/la je Tweet
    31. sij

    before our post on E4's crypto, this writeup by starts by talking of threat modelling, functional constraints, trust assumptions, business needs, platform support, etc. the opposite or typical twitter/HN is-it-secure-or-insecure discussions

    Poništi
  7. proslijedio/la je Tweet
    29. sij

    this IOActive report on LoRaWAN is more marketing than research, as usual , but correctly points out known security shortcomings of LoRa encryption and key management; tech can help here, for Sigfox as well

    Poništi
  8. 29. sij

    I don't really understand what I just did, but I installed ghc 8.8.

    Poništi
  9. 29. sij

    I don't know about you , but I don't want to live in a world where someone else makes the world a better place better than we do.

    Poništi
  10. 29. sij

    Compiling code with cargo +random_version_of_the_compiler_that_may_have_bugs install package. Any chance we can rename nightly to yolo?

    Poništi
  11. proslijedio/la je Tweet
    29. sij

    It was an honor and a pleasure to collaborate with MongoDB to help review and strengthen their new client-side encryption, great crypto engineering challenge!

    Poništi
  12. proslijedio/la je Tweet
    28. sij

    among the following WIP for 's E4, which one should we prioritize? (see , )

    Poništi
  13. proslijedio/la je Tweet
    27. sij

    New cache attack against Intel CPUs:

    Poništi
  14. proslijedio/la je Tweet
    27. sij
    Poništi
  15. proslijedio/la je Tweet
    27. sij

    Interesting post by on the security goals and constraints of end-to-end encryption in the IoT ecosystem, drawing comparisons with examples in other ecosystems such as Signal/secure messaging.

    Poništi
  16. proslijedio/la je Tweet
    27. sij

    where we explain, among others, why "the Signal protocol of IoT" must be very different than the Signal protocol great post by

    Poništi
  17. proslijedio/la je Tweet

    UK government have today announced plans to regulate Internet of Things devices, aka poor product cybersecurity. “...it is now clear that decisive action is needed to ensure that strong cyber security is built into these products by design.” 👍🏾

    Prikaži ovu nit
    Poništi
  18. proslijedio/la je Tweet
    23. sij

    Greetings from , where presents a project to protect connected lampposts, where end-to-end encryption and key management played a crucial role - the kind of use case where E4 is now the ideal solution :)

    Poništi
  19. proslijedio/la je Tweet
    22. sij

    As an early Sonos adopter and fan of the early products, I am dismayed by the turn the company and products are taking. Aside from constant upgrading of software & snooping on users (why do I need to register to use my speakers?), their policies about bricking devices and ...

    Prikaži ovu nit
    Poništi
  20. proslijedio/la je Tweet
    22. sij

    this is IBM on end-to-end encryption for MQTT, which then gives an example of CBC encryption with a static key, no authentication, and potentially padding oracles (@ ) to do this the right way (real security, low-energy), use E4

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·