|
Apr
29 |
|
revised |
Is this solution RESTful and secure? added 1606 characters in body |
|
Apr
29 |
|
comment |
Is this solution RESTful and secure? @Oleksi - I am quite aware of that, but could you please be a little more helpful and perhaps answer a solution that is safe (or at least, safer)? |
|
Apr
28 |
|
awarded | Editor |
|
Apr
28 |
|
revised |
Is this solution RESTful and secure? added 148 characters in body |
|
Apr
28 |
|
comment |
Is this solution RESTful and secure? I am far from a security expert and that is why I posted here. I use AES encryption and transmit over SSL. I generate a simple key using some known server-client algorithm and send all necessary data along. My main concern is to ensure that all requests are only made from non-tampered clients on mobile devices. |
|
Apr
28 |
|
comment |
Is this solution RESTful and secure? @redreggae - Forgot to mention, this will be implemented on mobile devices without any 3rd party identification (Facebook, Google, etc) |
|
Apr
28 |
|
comment |
Is this solution RESTful and secure? Is it possible to use OAuth with .NET? Like I said, first time I've tackled such an issue - I'm a RESTful noob :) |
|
Apr
28 |
|
awarded | Student |
|
Apr
28 |
|
revised |
Is this solution RESTful and secure? edited tags |
|
Apr
28 |
|
asked | Is this solution RESTful and secure? |
|
Apr
18 |
|
asked | Selecting a correct data layer for an asynchronous online game |
|
Apr
13 |
|
awarded | Popular Question |
|
Mar
3 |
|
awarded | Popular Question |
|
Jan
30 |
|
awarded | Popular Question |
|
Dec
20 |
|
comment |
"Super meatboy"-ish replay My original idea was to record at 60FPS, which is definitely an overkill. Your approach seems very reasonable, simple and failsafe - I'll definitely give it a go! |
|
Dec
20 |
|
awarded | Supporter |
|
Dec
20 |
|
accepted | "Super meatboy"-ish replay |
|
Dec
20 |
|
awarded | Editor |
|
Dec
20 |
|
revised |
"Super meatboy"-ish replay added 168 characters in body |
|
Dec
19 |
|
asked | "Super meatboy"-ish replay |
