After getting my Next v2 put in, I started asking questions at work about getting my door access added to it and was promptly told that the facilities team had more important things to deal with, so I’m not getting any help from them.
We appear to use a Gallagher T15 muti-tech reader for door access here. By my research it should be compatible with LF and HF chips, though we exclusively use Gallagher’s iphone app for access. The app only uses bluetooth to unlock the door (so I can’t sniff any details), though I’m sure the RFID reading on the reader is not disabled as when I swipe my chip it plays an access denied tone.
I’d pretty much given up hope on setting this up until today, when I was digging around in the app and found my access credentials. I’ve got 2 sets of things (not sure what the right term is) listed, one labelled as my key and the other labelled as the site key. Each is a list of 32 sets of 2 characters (eg A1 BB C2 DE etc). Is it possible to write these details manually to my chip to enable door access?
If possible I’d like to put them onto the LF side of the chip, though I’m happy to overwrite my vcard on the NFC side if needed. Does this sound possible with just this info or am I missing other important details too?
If it were me, and I could not rely on help from the staff.. I would at least see if I could request a fob or card as a backup credential. Tell them it’s because your phone is unreliable or you sometimes leave it at home or you just want a backup access method that doesn’t require charging a battery.
If you are able to convince them to issue you one of these credentials, then we can test it to see if it’s clonable to an implant. It would have to be a low frequency card to have half a shot at being clonable. These are typically the cheapest options for card credentials though so there is a chance.
I found the policy right as you posted this, mobile access is explicitly listed as the only way to access site, no fobs will be issued. Oh well, it was worth a shot
If your HF lights up, you’re outta luck, as Gallagher uses DESFire for HF I believe (it maybe compatiable with others, but if DESfire, it wont write to your NExTV2 anyway)
If your LF lights up, there is hope.
MOST Gallagher readers will work with xSeries (You might struggle with the outdoor ones)
Let us know how that test goes, and we can step through the options (It will require their support, but we can make that super low drag for them ie. easy to do, and hard to deny)
There may be an easy way to do HF (but I am.less certain on that) IF that works, you wont need to worry about your NDEF data, as it would be UID enrollment only.
You’re going to need to do some social engineering, but that will be easier if we give you the knowledge to present.
It does ping as HF, so I’m triple out of luck it seems.
I’d assumed until now that because it reacts to my chip it must be compatible in some way but I suppose it could scan and give a no access tone by default for any incompatible chips/cards, couldn’t it? At least this is educational disappointment
Usually the badge reader just gives a beep whenever it sees something it can recognize, whether it’s valid or not
The reader doesn’t usually know if a credential is valid, it just sends the data down to the controller
Support for multiple card technologies including: MIFARE DESFire EV1®,MIFARE DESFire EV2®, MIFARE Plus® and MIFARE Classic® as well as 125 kHz proximity and Bluetooth® wireless technology
So it probably either also accepts CSN from the HF side of your implant, or is sneaky-sneaky polling LF and your RDC just missed it
It does give a distinct “womp womp womp” descending tone, though I don’t know the difference between the reader and controller so that probably still adds up. I’ll do some reading on it.
I’ll try the diagnostic card on it again, if the card has just missed an LF scan ya’ll will be the first to know
you will need their help.