Elichai Turkel

@Elichai2

Software Engineer, Bitcoin, Rust, Cryptography, Open Source, PGP: 5607C93B5F86650C A human fuzzer.

World Citizen
Vrijeme pridruživanja: siječanj 2011.

Tweetovi

Blokirali ste korisnika/cu @Elichai2

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

  1. prije 10 sati

    Arghh. Ignoring the 72 byte limit of bcrypt is a problem. Saying "just hash it before" is worse. Because an attacker can potentially shift the brute force from cracking bcrypt to cracking a hash. If you're using bcrypt, either switch to something else or *limit password length*

    Poništi
  2. 29. sij

    I think most people underestimate how broken everything is. (especially at the OS and HW level)

    Poništi
  3. 27. sij
    Poništi
  4. 18. sij

    I agree 100% I belive unsafe code is the new bikeshedding in rust. It's easy to argue against the idea of unsafe instead of arguing with complex designs/functions etc. Unsafe isn't inherintly bad, and safe code doesn't mean good. Hell most of std is unsafe :)

    Poništi
  5. 16. sij

    Question for Twitter :) Why does libstd prefers Free functions / Non member functions over Class Methods? (ie std::begin, std::get etc.)

    Poništi
  6. 10. sij

    Is this serious? Does anyone have packets of this? I'd like to inspect them (luckily I don't have an iPhone) Someone need to tell Apple when to stop. Next thing all your internet will go through some rando iPhone next to you who will MitM you.

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

    is anyone still using the bitcoin binaries for 32-bit x86 linux? if you do, please let us know—the current idea is to phase them out in the not-so-distant future

    Poništi
  8. 7. sij

    Who's planing to attend in Feb? Trying to decide if I want to go

    Poništi
  9. 31. pro 2019.

    TIL 64bit x86 architectures only have 48 bit addresses. (and even that is only virtual, physically it's 39bits. how does that work?)

    Poništi
  10. 27. pro 2019.
    Poništi
  11. 21. pro 2019.

    Obviously overtime you learn the symbols and common variable names for everything. But then you go on to learn a new thing/concept and you're back in the loop all over again.

    Prikaži ovu nit
    Poništi
  12. 21. pro 2019.

    OMG yes. I've been complaining about this all the time. It's so hard for new people to understand papers if they assume so much symbols just to be able to *read*. There are only a handful of papers that try to explain everything, but most of them assume so much.

    Prikaži ovu nit
    Poništi
  13. 21. pro 2019.

    And obviously thanks once again for transcribing and making it easier to read through :)

    Prikaži ovu nit
    Poništi
  14. 21. pro 2019.

    Even after reading the BIPs multiple times, participating in reviews, participating in etc. I still learned a lot about tapscript's gears from this talk(specifically the *reasons* for the different upgrade mechanisms) Thanks !

    Prikaži ovu nit
    Poništi
  15. 11. pro 2019.

    The future of peer review. I'd love to see an app like that.

    Poništi
  16. 9. pro 2019.
    Prikaži ovu nit
    Poništi
  17. 9. pro 2019.

    2019 C: goto are bad, they break the program's code flow. Go: Hold my beer

    Prikaži ovu nit
    Poništi
  18. 8. pro 2019.

    Controversial opinion: Deep fakes are a good thing. They can potentially cast doubt on the authenticity of all revenge porn, making all future nudes pics/video "leak" uninteresting and de facto fake.

    Poništi
  19. 5. pro 2019.
    Prikaži ovu nit
    Poništi
  20. 5. pro 2019.

    On top of that / speratly a paper/book explaining/anaylizng the different mechanisms used in proofs (ie the forking lemma)

    Prikaži ovu nit
    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:

    ·