@cheyclough @EmilyLShepherd @rabbit_hmi @AndroidAuth Not even then, you could just use a valid imei in your request anyways, a lot get shared accidentally. The best thing would be is to bind an imei to a user account and MAKE SURE that only that user can use it though that link. But as of now you can use any imei in the known… Tweet added by Marcel @MarcelD505

Marcel

2 months

@cheyclough @EmilyLShepherd @rabbit_hmi @AndroidAuth Not even then, you could just use a valid imei in your request anyways, a lot get shared accidentally. The best thing would be is to bind an imei to a user account and MAKE SURE that only that user can use it though that link. But as of now you can use any imei in the known…

1

0

6

Marcel

@MarcelD505

2 months

@cheyclough @EmilyLShepherd @rabbit_hmi @AndroidAuth With binding an imei to a user account i mean bind it on purchase, i don't know the humane process but i think they tie a device to your user account as soon as you buy it. That would solve all of this but will make it integration hell for rabbit.

1

0

4

Marcel

@MarcelD505

2 months

@cheyclough @EmilyLShepherd @rabbit_hmi @AndroidAuth Or like send any identifiable information to the device on first connection from an account and just don't allow other accounts to access it until its unlinked from that specific account + don't print the imei on the freaking box.

2

0

4

Replies