recently got an xsiid blue installed! Im wondering if there are machines out there that may issue a lock command to it like a payment terminal, security rfid scanners for stores, or a smart lock lol? Maybe its just paranoia but i would like to avoid having my xsiid maliciously or accidentally locked permanently before i start waving it around.
Ive read into a little of how to “lock it open” (where you can read easily but not modify without password) on the forum and i wanted to know if this is a non issue or how i might going about it if its deemed necessary?
here are the commands i would also like to know if i have them correct.
so initially you need to set the password with this command.
A2E5[Password]
would this be appropriate for the password of “swag” (for example lol)
A2E573776167
then i would need to disable wrong password attempt limiter with this
A2E400000000
following it with this to finally (initially) lock the whole chip from writes
1B73776167
A2E3000000E2
then the unlock and lock commands as follows?
Unlock with
1B73776167
A2E3000000E2
To re-lock issue:
1B73776167
A2E300000000
do these commands see good for the xsiid (not relevant most likely but blue lol)?
Lastly Ive heard i need to issue this with the RAWNFC app that was recently released in quick succession. After this is done am i still able to write with the NFC TOOLS app (ios orange app) easily? will it prompt for a password when writing or just error out?
There are some systems out there designed to attempt to brick magic tags, but I don’t believe there is much risk to an xSIID. That said, some apps/cloners might attempt to set their own passwords, so you should be somewhat aware of what you’re doing.
I personally keep my xSIID locked, but that’s mostly just for the fun of it
Those look right to me, but a few notes:
The password attempt limiter should be disabled by default, so that shouldn’t technically be necessary, but it couldn’t hurt to double check either
The xSIID might be locked from DT, so you may need to unlock it to begin with. I know the NExT is shipped this way, but am not totally certain about the xSIID. If it is locked, the password would probably be DNGR ( 0x44 0x4E 0x47 0x52)
If the implant is locked from DT, it’s pretty likely they locked all the pages you’d really need to worry about, so you might not need to further lock it yourself
I know you already know, but be triple-double-extra sure you’re certain you’re setting the correct password prior to sending the command. I’d also recommend being familiar with how/where the implant reads on your phone to make sure the connection is solid
I’m not certain if that app is available on IOS, but you I believe can just use the Advanced section of NFC Tools too, just separate the commands by a comma
Nope, just errors, you’ll have to unlock it prior to writing. (NFC Tools android does for me anyways)
thank you for the welcome! Took me 6 years to eventually do it lol
I dont believe the xsid was locked as i was able to write to it immediately.
I have an android too with the raw nfc app but good to know the IOS app has the ability to fire off multiple commands with commas.
I think the password is the correct conversion of swag. I used this online tool which i think what the command is expecting? ASCII to Hex | Text to Hex Code Converter
I’m going to also message the dev of nfc tools, it would be so much easier if i could just use the set and remove password functions in the app. Maybe Amal could also add command libraries to the rawnfc app, text to hex pw conversion prompt would be so cool. bc im still paranoid about issuing these commands.
They would only lock the configuration pages, not the user memory
That site has been pretty reliable for me, just make sure you remember what you set
You might give that suggestion to @Az_F too, he’s working on a similar project
It can definitely be a little nerve-wracking sending raw commands to something inside you, but as you do it and start to get a feel for how the chip works that will start to go away
Yeah I’m 100% doing all of that in ZINC , just not very soon. In October I’ll be in the US and in November I’m moving to mainland France and looking for a job there so yeah, soon™…
It sounds easy but it’s not actually that simple. You cannot remove the password from the chip. The chip always needs to have a password value of some kind because a particular memory page acts as the password storage. Even if you want to set this to all null bytes, then the password becomes four null bytes.
Basically you should review the data sheet first before asking developers to make changes what we’ve done is disable the lock bites so you can’t accidentally permanently lock your chip has read only. The password, as I said, cannot be removed but it can be set to a factory default value.
Even so, there is a byte in the configuration pages called the Auth0 byte. The value of this particular byte tells the chip at which memory page to apply password protections. If you set this value to FF for example, this is far beyond the last memory page on the chip and therefore you’re basically saying don’t apply any password protections to any memory pages on the chip. We do not recommend this however, because it also means the password page itself is unprotected and can be changed or overwritten without first needing to authenticate. We also suggest setting auth0 to protect the configuration pages (which includes the password page) so nobody can change any of the critical configuration bytes without first authenticating.
You should also check out the prot bit value which determines if the password protection is only for writing or both reading and writing.
