As your keybase user run:
$ keybase bot token create > /tmp/bot-token
You'll get back a base64 token, like: 6C37sjCBgMNf06Z6oTgixIxHJpja8G-Qp
. This is your bot token that allows you to sign up bots.
This gist is to configure a Mosquitto MQTT Broker behind a Traefik reverse-proxy, both in a docker container. Mosquitto will be configuread as a TCP Service.
This is a simple configuration used on the same single server. Probably to be adapted for other cases. Having mosquitto behind a reverse proxy enables you to configure TLS on Traefik (likely you already do that for other applications as well) and to load balance different MQTT instances, but that goes beyond this gist.
As noted in Traefik docs, in the router you must use the rule HostSNI(`*`)
when using non-TLS routers like in this example. Ref. https://docs.traefik.io/routing/routers/#rule_1
docker-compose.yml
(^ that's a short-link to this page, so you can open it in Linux)
Some users are discussing this guide in #hacking on the JoyConDroid Discord: https://discord.gg/SQNEx9v.
DO NOT ask for, or share links to, Amiibo bins in the comments! They will be removed. Thank you for understanding.
# official docs: https://graphql-ruby.org/dataloader/sources.html | |
# app/graphql/sources/association.rb | |
class Sources::Association < ::GraphQL::Dataloader::Source | |
def initialize(association_name, scope = nil) | |
@association_name = association_name | |
@scope = scope | |
end | |
def fetch(records) |
A newer version of this info is available at https://badcfe.org/how-to-paxton-with-rfidler/
Paxton fobs and readers are popular in the UK especially the Net2 system where the fobs look like this with a blue ring:
Paxton readers often look like this:
A list of rewritable RFID blanks that are compatible with Flipper Zero.
X indicates a particular protocol is writable.
? indicates it is unknown if a particular protocol is writable.
Brand | Type | Chip | EM4100 | H10301 | Indala26 | IoProxXSF | AWID | FDX-A | FDX-B | HIDProx | HIDExt | Pyramid | Viking | Jablotron | Paradox | PAC/Stanley | Keri | Gallagher |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ETEKJOY | Fob | EM4305 | X | X | X | X | X | X |
Term | Meaning |
---|---|
WUP-SAK | SAK Value found during the Wake up & Anti-collision process, what you would see reported from a basic search. |
Vanity SAK | SAK Value represented in Block 0 of a Mifare Classic, on legitimate cards this does not inform the value of the WUP-SAK. |
Magic Card | An illegitimate card capable of changing it's UID; some magic cards are also able to change other values such as ATQA/SAK. |
Here is somethig you might find useful: automatic pio assembly -> h file generation for platformio.
I have tested it on Linux only.
Contrary to the docs, stating the pioasm is installed together with the dev platform:
https://registry.platformio.org/tools/earlephilhower/tool-pioasm-rp2040-earlephilhower/installation
the json file
https://github.com/maxgerhardt/platform-raspberrypi/blob/develop/platform.json
Research by Grayson Martin
Last Updated 7/8/23
Value Added Services (VAS) is the protocol used by NFC capable passes in Apple Wallet. Access to this protocol is heavily restricted on both the device end (a special certificate issued by Apple is required to create these passes) and the reader end (NDA enforced confidentiality). As such, a desire arose to better understand the protocol in order to explore additional use cases and examine its cryptographic integrity. There are gaps in understanding in certain parts of this protocol, however this document contains the minimum necessary understanding to automatically select, read data from, and decrypt a pass.
Importantly, this specification does not enable a malicious actor to read the data from a pass for which they do not have both the reader's private key, and the pass type identifier. Imp
NDEF (NFC Data exchange format) is a method of transferring (relatively small amounts of) information from a passive or actively emulated tag by way of "records" which specify the type of information is being received and the function it is meant to have.
iPhones do not have a full suite of NDEF compatibility, the reason for this is unknown (to me at least), what this means is the background polling on iPhones will not interpret some specific record types, with compatible NDEF records, a notification will pop up directing the user to follow the received data into its respective app to complete whatever action was intended by the record.
Below are the options offered by NFC Tools on IOS for NDEF Encoding, some of the options below are other record types but with a specific function IE social links are just URLs.