Timeline for Approach to Authenticate Clients to TCP Server
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2013 at 0:13 | history | edited | dab | CC BY-SA 3.0 | added 1024 characters in body |
| Nov 5, 2013 at 21:07 | vote | accept | dab | ||
| Nov 5, 2013 at 20:53 | comment | added | GomoX | By the way, if you don't have an excellent reason to do so, avoid rolling your own protocol over TCP. | |
| Nov 5, 2013 at 20:50 | comment | added | GomoX | If you don't want to manually validate the new clients, then the approach mentioned on my last paragraph below should work just fine. I have extensive experience with agent-based systems and I would recommend you generate a GUID and store it in the client instead of using a MAC address which can create a lot of problems (unless what you are identifying are actually ethernet cards). | |
| Nov 5, 2013 at 20:45 | comment | added | dab | I've appended some more detail at the end. Hopefully that clarifies things a bit better. | |
| Nov 5, 2013 at 20:44 | history | edited | dab | CC BY-SA 3.0 | Adding extra detail about the protocol use. |
| Nov 5, 2013 at 20:32 | review | First posts | |||
| Nov 5, 2013 at 20:45 | |||||
| Nov 5, 2013 at 20:25 | comment | added | GomoX | I posted a reply below, but more information on the uses of the protocol might allow use to post a better answer. | |
| Nov 5, 2013 at 20:24 | answer | added | GomoX | timeline score: 3 | |
| Nov 5, 2013 at 20:16 | history | asked | dab | CC BY-SA 3.0 |