Password protection on fresh implants

[Pilgrimsmaster]

Welcom Buddy, I hope the installs went well!
Positions L0 and R0?

Naming convention for implant locations in the hand

During a discussion on another thread in this forum, it became clear that a naming convention of some sort should be made for the implant locations in the hand. I simply modeled the way dentists talk about teeth in the mouth, and concluded the following should suffice. Flex series implant considerations It is recommended that flex implants not be placed in position 4 or 5 (see below). These locations often put too much stress on the implant and tend to have a higher failure rate when flex impla…

The NExT is also done at the factory so no need to do anything.
The xSIID I don’t have, but the same deal, just different password

but just let me find you a link or two so you can read for yourself, wait one…

Just ordered an xSIID+LED NFC chip, how should I properly set it up?

So this is my second implant, first one I got was the xNT and to set it up and secure it I used the dangerous NFC app to password protect the lock bytes. Would this chip follow the same procedure? I also saw this thread https://forum.dangerousthings.com/t/xsiid-tag-is-not-ndef-compliant/7539 I assume I’ll have to follow the same procedure to make it recognizable? Anyway thanks for reading and have a good day Also thanks Amal you never disappoint <3 can’t wait for it to arrive! …

THIS ONE says it all and straight from Amal from 5 days ago.

@amal

The current batch of NExT does have a password set, but we decided to leave the xSIID password set to factory default FF FF FF FF. We did set AUTH0 to enable protections, just to ensure there was an extra step at least to alter those bytes… but it was a gamble… so many badly written NFC apps will gladly issue the PWDAUTH command with factory default just as a check mechanism, and in doing so, may possibly impact the AUTHLIM counter (if it’s enabled) which is a terrible disservice as an app to take a potentially destructive action without even informing the user… but then once PWDAUTH is issued, it can freely overwrite config bytes by accident… if it’s badly written… so you see it’s a bit of a risk for our users to not set a password on the xSIID…

I think though that once we have our own app (@hoker), we will program the next batch to have a non-factory but defacto default password… maybe we will make all DT product passwords DNGR from the factory… dunno yet.

Pretty much you are good to go!!!
Enjoy

Any questions come on back