@kitten

kitten @kitten@elizabeth.cat

Admin

This user has been bitten by a soft cat

You found my personal account! If you know me from formal or irl spaces, you probably shouldn't look in here. Proceed at your own risk.

26
Clichéd transfem. Poly cuddle slut. Nonsexual little. Frequent meower. Kinky pervert. I pee myself a lot.

I contribute code somewhere, but I forgot where.

I like to be referred to as "kitten" or "little one". You can do that if you want and it'll make me happy but it's not a requirement (also don't use the latter in adult contexts)

formerly @me@elizabeth.cat

"a pervert who lost control over their life"

Location Europe

Birthday 1999-03-02

Pronouns they/them (EN)

Pronouns they/them, although she/her when I don't feel like explaining

kitten @kitten@elizabeth.cat

even more kink, silly, wax, e-stim

@lis you don't need to solder anything to me for that, but you can still [choose your own adventure: wax, e-stim]

kitten @kitten@elizabeth.cat

kink

@lis .....meow

kitten @kitten@elizabeth.cat

self-subpost

@lis hey! you'd only need to solder those 4 cables and run a command!

kitten @kitten@elizabeth.cat

(my knowledge in cryptography is very basic, any insight from people more into it is welcome)

kitten @kitten@elizabeth.cat

self-subpost

anyone who got physical access to my tag

the one you'd be always wearing at a few millimetres from your skin you mean?

kitten @kitten@elizabeth.cat

feels a bit... not as safe? anyone who got physical access to my tag could dump the firmware super easily and get both those values (and then leave the tag as it was so it kept tracking). it'd be nicer if the algorithm could derive p(i) from p(0) or p(i-1) instead

kitten @kitten@elizabeth.cat

so, my current doubts stem from:

from the people behind OpenHaystack there is this paper. in section 6.1 they explain:

Equation (1) derives a new symmetric key from the last used symmetric key with 32 bytes length. Equation (2) derives the so-called “anti-tracking” keys ui and vi from the new symmetric key with a length of 36 bytes each. Finally, Eqs. (3) and (4) create the advertisement key pair via EC point multiplication using the anti-tracking keys and the master beacon key d0

now, what confuses me is, looking at OpenHaystack's code, we can see that what they transfer to the device on flashing is a symmetric key (SK0 in the equations) and what they call a "public key"

but I'm under the impression that it's actually the private key, and thus the device needs to hold both the symmetric key and the private key (d0)

kitten @kitten@elizabeth.cat

@mildsunrise ......ah

kitten @kitten@elizabeth.cat

okay but why is the third argument here an int??? why not a bool?

docs.nordicsemi.com/bundle/sdk_nrf5_v12.2.0/page/group_sha256.html#gae275b489baf65a4362dc2bc724d07ccd

kitten @kitten@elizabeth.cat

cryptography is actually, like, difficult

kitten @kitten@elizabeth.cat

@LilaHexe every being is meant for different things

kitten @kitten@elizabeth.cat

kitten playing with trackers

@ayke hmmm, is tempting to try, because I really like Go... but I think it'd add extra complexity more than anything

kitten @kitten@elizabeth.cat

kitten playing with trackers

@Doridian yes!

kitten @kitten@elizabeth.cat

@puppygirlhornypost2

kitten @kitten@elizabeth.cat

kitten playing with trackers

@ayke hm!!

okay I'll check it out, thanks. the main thing would be being able to also access cryptography utils

kitten @kitten@elizabeth.cat

kitten playing with trackers

so... time to start writing that firmware

I think I'll usethis as base, but I'll still do some more research

also, I did some quick testing, and it seems like tracker #1's case is at least a bit waterproof (I put it empty in the sink full of water and none got in the inside). which is nice, because, you know, this might get at least a bit wet eventually

kitten @kitten@elizabeth.cat

kink, silly, references dubious consent

dubious consent: unknowingly using people's iPhones for our own kinky satisfaction

kitten @kitten@elizabeth.cat

"Risk-Aware Consensual Kink" also acknowledges writing memory-unsafe code from time to time

kitten @kitten@elizabeth.cat

fedi

it's time

let's write some C code

kitten @kitten@elizabeth.cat

❮ Previous page Next page ❯