Timeline for Prevent or detect key copy
Current License: CC BY-SA 3.0
40 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 12, 2015 at 18:02 | history | edited | user91560 | CC BY-SA 3.0 |
added 4 characters in body
|
| Nov 12, 2015 at 15:15 | answer | added | Daan Bakker | timeline score: 0 | |
| Nov 12, 2015 at 13:18 | comment | added | user91560 | @RoryAlsop:the core of the question hasn't changed. But I won't anymore | |
| Nov 12, 2015 at 13:09 | comment | added | Rory Alsop♦ | user200312 - please don't make so many edits to the core of your question. it has begun to invalidate the answers already posted. | |
| Nov 10, 2015 at 21:45 | history | edited | user91560 | CC BY-SA 3.0 |
added 64 characters in body
|
| Nov 10, 2015 at 21:33 | history | edited | user91560 | CC BY-SA 3.0 |
added 229 characters in body
|
| Nov 10, 2015 at 21:18 | history | edited | user91560 | CC BY-SA 3.0 |
clarified question
|
| Nov 10, 2015 at 19:47 | history | edited | user91560 | CC BY-SA 3.0 |
added 50 characters in body
|
| Nov 10, 2015 at 19:33 | history | edited | user91560 | CC BY-SA 3.0 |
added 157 characters in body
|
| Nov 10, 2015 at 19:24 | history | edited | user91560 | CC BY-SA 3.0 |
added 123 characters in body
|
| Nov 10, 2015 at 18:05 | history | edited | user91560 | CC BY-SA 3.0 |
added 32 characters in body
|
| Nov 10, 2015 at 17:49 | history | edited | user91560 | CC BY-SA 3.0 |
[Edit removed during grace period]
|
| Nov 10, 2015 at 17:36 | history | edited | user91560 | CC BY-SA 3.0 |
added 106 characters in body
|
| Nov 10, 2015 at 17:30 | history | edited | user91560 | CC BY-SA 3.0 |
added 106 characters in body
|
| Nov 10, 2015 at 17:29 | answer | added | Andrew Philips | timeline score: 4 | |
| Nov 10, 2015 at 17:29 | history | edited | user91560 | CC BY-SA 3.0 |
added 106 characters in body
|
| Nov 10, 2015 at 17:20 | history | edited | user91560 | CC BY-SA 3.0 |
added 19 characters in body
|
| Nov 10, 2015 at 16:18 | answer | added | Matthew | timeline score: 2 | |
| Nov 10, 2015 at 15:27 | history | edited | user91560 | CC BY-SA 3.0 |
added 98 characters in body
|
| Nov 10, 2015 at 14:37 | comment | added | user91560 | @Matthew: So to make clear I am looking for solutions not related to HSM say | |
| Nov 10, 2015 at 14:27 | history | edited | user91560 | CC BY-SA 3.0 |
deleted 17 characters in body
|
| Nov 10, 2015 at 14:10 | history | edited | user91560 | CC BY-SA 3.0 |
added 166 characters in body
|
| Nov 10, 2015 at 14:07 | comment | added | user91560 | @Matthew: Yes I refer to similar I used to have something similar to USB devices which stored the key and you could not copy that. I am looking for other ways now - software, cryptography specific, etc. | |
| Nov 10, 2015 at 14:07 | comment | added | user91560 | @Matthew:You mean something like this: wisegeek.com/what-is-a-hasp-dongle.htm#didyouknowout ? (With these devices you can't copy they key). I am looking for other ideas also. Maybe application wise something is possible to be done - e.g. accept request only from some IP address but this is not secure IMO and can't work if IP addresses aren't static. So I am looking for the best practice | |
| Nov 10, 2015 at 13:52 | comment | added | user91560 | Well, yes that is my point, I think I explained the scenarios mostly - if you have some questions, please ask, if no, please provide an answer in your post - you are welcome to do that. Covering all aspects - which in the end result in secure solution to my problem. | |
| Nov 10, 2015 at 13:48 | comment | added | sybond | Yeah, if they know the structure of your certificate, and how you signed it. Another point is how you secure your client app againts reverse engineering also valueable key to prevent unauthorized use of your app. | |
| Nov 10, 2015 at 13:38 | comment | added | user91560 | Well that is my point I am looking for a secure way to do this, for example MAC you suggest can be easily spoofed; attacker could also probably read HDD serial CPU ID from my PC - copy them and pass in a hardcoded way to the server, isn't it? (signed of course) | |
| Nov 10, 2015 at 13:37 | comment | added | sybond | It is your own digital cert scheme, so its depend on how you want to identify the client. You can use all the unique IDs of the client combined together (MAC, HDD serial, CPU ID etc) for example. | |
| Nov 10, 2015 at 13:29 | comment | added | user91560 | What if someone steals that certificate? | |
| Nov 10, 2015 at 13:25 | comment | added | Matthew | No, that is a software dongle. A HSM is specifically designed for storing keys - en.wikipedia.org/wiki/Hardware_security_module | |
| Nov 10, 2015 at 13:24 | comment | added | sybond | You can implement your own scheme of digital signature for example. Legitimate client can be determined by their certificate, since it will be signed using your server private key. | |
| Nov 10, 2015 at 13:14 | history | edited | user91560 | CC BY-SA 3.0 |
added 10 characters in body
|
| Nov 10, 2015 at 13:14 | comment | added | user91560 | and how does that protect from copying and authenticating the client to the server still? | |
| Nov 10, 2015 at 13:12 | comment | added | sybond | Best way is to modernize your method by using asymmetric key encryption :) | |
| Nov 10, 2015 at 13:05 | comment | added | Matthew | You might want to consider looking at a Hardware Security Module (HSM), which is designed to solve this issue. You can't tell the difference between original and copied data though - they are, by definition, identical. | |
| Nov 10, 2015 at 12:58 | history | edited | user91560 | CC BY-SA 3.0 |
added 22 characters in body
|
| Nov 10, 2015 at 12:39 | history | edited | user91560 | CC BY-SA 3.0 |
added 102 characters in body
|
| Nov 10, 2015 at 12:33 | history | edited | user91560 | CC BY-SA 3.0 |
added 177 characters in body
|
| Nov 10, 2015 at 12:32 | review | First posts | |||
| Nov 10, 2015 at 13:55 | |||||
| Nov 10, 2015 at 12:27 | history | asked | user91560 | CC BY-SA 3.0 |