Timeline for Unique Identifier for raspberry pi board [closed]
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 31, 2017 at 3:36 | vote | accept | benny96 | ||
| Jul 26, 2017 at 4:54 | history | closed |
Milliways Jacobm001 |
Needs details or clarity | |
| Jul 25, 2017 at 14:30 | answer | added | Eugen | timeline score: 0 | |
| Jul 25, 2017 at 12:22 | review | Close votes | |||
| Jul 26, 2017 at 4:54 | |||||
| Jul 25, 2017 at 7:56 | comment | added | Bex | Spoofed in what context? If you're going to transmit this unique id it can be changed or impersonated in the transmission. If so, you need a challenge-response approach. | |
| Jul 25, 2017 at 6:40 | comment | added | Steve Robillard | Have you considered a certificate based approach | |
| Jul 25, 2017 at 6:37 | comment | added | Steve Robillard | Are your end users really like to change the serial number and what are the chances of that compared to just stealing it. | |
| Jul 25, 2017 at 6:17 | comment | added | benny96 | Actually, I'm trying to create a device using raspberry pi, which i should be able to continuously keep a track on. So I need that specific identifier to be unique and which cannot be spoofed or cracked or changed? Any suggestions? | |
| Jul 25, 2017 at 6:11 | comment | added | Steve Robillard | What is the use case? | |
| Jul 25, 2017 at 6:11 | review | First posts | |||
| Jul 25, 2017 at 7:56 | |||||
| Jul 25, 2017 at 6:10 | comment | added | benny96 | It is because, I read that it can easily be spoofed. I just wanted it to be unique | |
| Jul 25, 2017 at 6:09 | history | edited | benny96 | CC BY-SA 3.0 |
deleted 1 character in body
|
| Jul 25, 2017 at 6:09 | comment | added | Steve Robillard | Why won't the serial number work? | |
| Jul 25, 2017 at 6:08 | history | asked | benny96 | CC BY-SA 3.0 |