108 reputation
3
bio website
location
age
visits member for 1 year, 11 months
seen Aug 27 at 17:48

Dec
28
awarded  Scholar
Dec
28
accepted Secure login feature with low CPU power
Dec
28
comment Secure login feature with low CPU power
Now I'm 100% sure that I don't know anything about the CPU time that encryption needs. I'm going to try it soon, thanks you very much for your answer. I'm sorry that I marked Polynomial answer as correct, but you have my upvote.
Dec
21
comment How can I embed iframe securely without restricting its functionality?
I guess that you need to make a "controller" that validates the JavaScript of the site or you can hide the functions from the application that he can't use. But it is all a lot of work and if they really want they can avoid your "security". This is very bad practice and I advice you not to implement this. But why do you want this?
Dec
21
comment Secure login feature with low CPU power
To make clear why I didn't choose for HTTPS: The target is to create an efficient implementation that doesn't wast CPU power. A requirement of my project is to create everything as efficient as possible. Efficient is more important then time when there is a visible performance improvement. So when I could create something that is 10% more efficient but it cost 20% more time, then I’m willing to spend the extra time to get 10% more performance. But this needs to be on a part of the system that has a great impact on the performance. An encrypted network connection is a big part.
Dec
21
awarded  Student
Dec
21
comment Secure login feature with low CPU power
An other problem of HTTPS is that you are encrypting data that doesn't need to get encrypted. This is just a wast of CPU time. I know it is secure, but there needs to be a better way that takes less power. You are 100% ride when you are logging in to a bank account, but I'm building a browser game, it doesn't matter if some one else knows how many supplies some one else has. It doesn't harm the user. The only thing that matters is in this case the users password and that some one else can't send an action to preform by another user.
Dec
21
comment Secure login feature with low CPU power
That is also true, the only downside is that the browser can't cache data. Images need to get downloaded every single time. So it will take a lot more bandwidth. But I could do some tests with libcurl. Thanks!
Dec
21
asked Secure login feature with low CPU power
Dec
21
awarded  Supporter