| 22 Aug 2024 |
 K900 ⚡️ | Or something | 10:04:13 |
 hexa | In reply to @k900:0upti.me
My robot vacuum runs openwrt huh, mine runs fckn Athena Linux | 11:47:53 |
| hexa | thanks dreame | 11:53:45 |
| K900 ⚡️ | That's an openwrt | 11:56:09 |
| hexa | wild | 11:57:48 |
 flare | In reply to @k900:0upti.me
My robot vacuum runs openwrt I fucking love this thought | 15:51:03 |
| flare | I am trying to implement smart cards with x509 certs set up and am having a hell of a time getting a writer | 15:52:03 |
| flare | millions of readers easy of iso 7816 cards but very few writers. have to write your own drivers. bleh | 15:52:30 |
| 23 Aug 2024 |
|  lmmohr joined the room. | 01:24:12 |
|  rolfst joined the room. | 13:15:04 |
|  Jake Thompson joined the room. | 16:57:21 |
| Jake Thompson | That just sounds interesting all over. I wish there was more industry support for various ones now that you mention that.
Maybe someone can pitch that to one of these VC's out here . | 16:58:57 |
| flare | I might actually be dumb. Turns out I was mixing up memory cards and PKI cards as they both use the same interface.
So now I have the backwards issues. Lots of potential writers. But very few cards. And albiet quite expensive | 19:03:57 |
| flare | 15 USD for a single one yeesh | 19:04:10 |
| 24 Aug 2024 |
|  @shymega:one.ems.host changed their display name from Dom Rodriguez (shymega) to [DEPRECATED] Dom 'shymega' Rodriguez. | 01:58:36 |
|  darkwater4213 left the room. | 02:21:20 |
|  lychee joined the room. | 04:25:42 |
|  summit0 joined the room. | 06:06:53 |
| Jake Thompson | In reply to @flare:matrix.darkc0de.one
I might actually be dumb. Turns out I was mixing up memory cards and PKI cards as they both use the same interface.
So now I have the backwards issues. Lots of potential writers. But very few cards. And albiet quite expensive wow , seeing as those have the same interface , that's definitely a manufacturer concern. I will look more into the ISO's around it , as you would think there would be some standardization around it you know. | 13:29:08 |
| Jake Thompson | In reply to @flare:matrix.darkc0de.one
I might actually be dumb. Turns out I was mixing up memory cards and PKI cards as they both use the same interface.
So now I have the backwards issues. Lots of potential writers. But very few cards. And albiet quite expensive if you don't mind me asking , whats the general case that , people in general use these for , is it like for hardware storage or an encrypted key?
| 13:30:51 |
| 25 Aug 2024 |
|  LinearArray changed their profile picture. | 05:01:15 |
|  Richard Cory joined the room. | 09:15:34 |
| flare | its similar to the Yubikey in that it is a hardware cryptographic token.
They are most commonly used in Government where its is an ID card with a certificate loaded. Some european countries also use it for national IDs. for the US however its limited to government contractors and military personel | 16:51:29 |
| flare | In reply to @vampyr3:matrix.org
wow , seeing as those have the same interface , that's definitely a manufacturer concern. I will look more into the ISO's around it , as you would think there would be some standardization around it you know. The thing is that ISO 7816 is essentially a full contact smart card specification stack.
For example what I have gathered is that ISO 7816-4 describes the pin interface and a lot of cards are compliant with this standard | 16:52:56 |
| flare | however 7816-15 describes how the internal data structure of the smartcard is to be laid out and access.
I havent read into this specific part too much as to whether specifically defines crypto tokens but either way it describes a file like data structure on smart cards
However no smart card has to follow BOTH. Memory cards are Just EEPROMs that connect to the contact interface specified in 7816-4. But dont provide any crypto circuity. So, not useful as a token.
| 16:56:22 |
| flare | so to have a smart card for crypto purposes you need to have a 7816-4 smart card with 7816-15 OR* pkcs#15 (crypto specific file system spec for smart card tokens).
All fine and dandy. apparently its impossible to find those cards that provide full pkcs#15 compliance so that they can be programmed by opensc. You usually find cards that only impliment partially pkcs#15 and the rest of how data is stored is left up to the manufacturer.
This is because FIPS 201 and SP 800-73 (US Government standards for ID smart card crypto tokens) Leave the internal data structure of the smart cards up to the manufacturuers
| 17:01:35 |
| flare | so in conclusion | 17:01:43 |
| flare | its one hell of a muddled mess. and If you want the exact same solution that is easy and nice to use. Get a yubikey | 17:02:16 |
| flare | Fun fact: You debit or credit card is also a smart card that follows these standards as a crypto token. Just its own decades long mess there | 17:03:21 |
| flare | * Fun fact: Your debit or credit card is also a smart card that follows these standards as a crypto token. Just its own decades long mess there | 17:03:29 |
