Live data from Hacker News

Viewing profile — ewpratten

ewpratten

HN member
Joined
Wed, Jan 22, 2020, 9:30 PM UTC
HN karma
192
Public activity
77 items

About ewpratten

https://ewpratten.com

Recent public activity

  1. story
  2. comment
    Comment #46824757

    I’m doing that (similar scale and same language) with a base model M4 mini. Works great. Anything more is overkill imo.

  3. comment
    Comment #46527058

    I completely agree with you. In my opinion, using GPS as Stratum 0 feels like a cheat. I do hope to some day (definitely not any time soon) own an atomic clock of some kind though.…

  4. story
  5. story
  6. comment
    Comment #46353607

    Regarding the Cloudflare part of this, I’d recommend taking a look at “Authenticated Origin Pulls”. It lets you perform your validation at the TLS layer instead of doing it with IP…

  7. story
  8. story
  9. story
  10. comment
    Comment #44327444

    You should probably be looking at the Cargo.toml file(s) (for direct dependencies at least) instead of the lock file as the lock file will include dependencies used for dev/testing…

  11. story
  12. comment
    Comment #43743492

    It’s automated in the kind of way that makes a lot of sense to people familiar with the internal HR systems.

  13. story
  14. comment
    Comment #42427585

    Think of it like a subset of MIFARE. In a simple sense, NTAG cards can do NFC things, but MIFARE can do lots more (access control for example)..and also NFC things..somewhat. Magic…

  15. comment
    Comment #42427575

    All my knowledge is trial & error. I've found the people over in the DT forum are pretty helpful with the cloning and usage aspect of things: https://forum.dangerousthings.com Addi…

  16. comment
    Comment #42427511

    Are you sure? The NFC app for iPhone can always read tags. Its specifically getting phones without the app to read them. Try wiping, then writing a URL from Android. Then just tap …

  17. comment
    Comment #42427493

    There's lots of info about the NDEF "packet" format online. I used this page as reference when I was putting together the "magic bytes" in the final section of the blog post: https…

  18. comment
    Comment #42427468

    Thank you very much! Something's clearly up there. You can see that even IOS and Android disagree with each other on what NDEF should look like by a few bytes. Very interesting.

  19. comment
    Comment #42427442

    Wipe the card. Make a dump after doing "hf mf ndefformat". Then make a dump after writing a payload from an iPhone. (since iPhone seems to want ndefformat anyways) Then wipe again …

  20. comment
    Comment #42427416

    Ya, looks like the iPhone is tinkering with the NDEF message itself. If my Android phone wasn't dead, I'd love to compare an iPhone's write against the Android NFC Tools app's writ…

  21. comment
    Comment #42427411

    There's approx 4 generations of "Magic". Gen 1, 1a, 3 and 4 all use special commands to unlock and edit block 0. Gen 2 treats block 0 as always being r/w. This allows Android phone…

  22. comment
    Comment #42427376

    Proxmark's "auto" command should get you most of the way to knowing. Then check if any of the "hf mf c*" commands work on it (in which case, you have a gen1a magic card)

  23. comment
    Comment #42427363

    HN formatting is going to do bad things here.. Here's the first 6 blocks of the card after I ran through the instructions of the post, then a ndefformat-only card (that never touch…

  24. comment
    Comment #42427354

    Hm, its definitely blocks 0-2. All remaining blocks after that are identical. Going to look further at the actual data in the first 3 blocks momentarily.

  25. comment
    Comment #42427345

    My quick eye-skim didn't see much, but I'll do a byte-for-byte diff. I imagine its a difference in the NDEF headers? (but even that doesn't make sense, since I wrote the headers ag…