Right. So… what you’re saying is, if I protect a tag with the Dangerous NFC app, I’m SOL if I want to write an NDEF record into the tag with TagWriter and NFC Tool afterwards. That’s unfortunate - but clearly miles better than writing something with either of those apps and then being SOL because you don’t know the damn password they set.
Good to know before I bring any of those app anywhere close to my doNExT
I think what I’ll do is play with the Proxmark3’s NTAG sim, see if it’ll let me record the transaction, then get TagWriter or NFC Tool to write a NDEF to the Proxmark3, then work out what the password it set was.
With any luck, the app implements a simple transform function that I’ll be able to work out. If not, I could run several passwords into the app until I find one that happens to be transformed into an ASCII string that I can input in the Dangerous NFC app. Like, say, I use “GRAA” in TagWriter and it turns out to make 0x41 0x4d 0x41 0x4c “AMAL” in the 32 bit value.
I must say, this whole business is way more stupid and complicated that it needs to be… No fault of DT’s of course (apart perhaps that I don’t much like not being able to set 0xDEADBEEF as a password in the Dangerous NFC app), but I really wonder why I have to jump through those loops to use MY fucking password in MY fucking tag. Why is it that all NFC apps always want to do stuff like that behind your back? Gee…
I’m almost tempted. Never done any Android development - mainly because I still quite can’t wrap my head around using a telephone for things other than placing phone calls - but that might be the incentive I needed to get into that.