Remote server api explained
In some ciphers, hashes, encoders etc you might see green banner like this:
This means that for example hashing process is done by my Raspberry Pi 3 server remotely. Reason why is that for this case example Argon2 didn't have any implementation for Android (when I wrote this) and I have been trying to find good reason to buy Raspberry Pi and at last I got one.
12.04.2017 I have generated self signed TLS (more secure than SSL) certificate for my server. Since it's self signed it's handled at application side in a way -> so if it's correct, connection is allowed --> meaning that Android app is shipped with clone of that certificate. I decided to use self signed cert cause signed ones seems to cost money, except "let's encrypt" provided ones. I go with self signed since it's easier to me and hey at least I didn't made app allow every TLS certificate it get's like many developers do.
Port 80 traffic is at 12.04.2017 closed for ever.
26.12.2017 - Correction => Signed certificate from Let's Encrypt is easier to set up than I thought, for example: www.digitalocean.com/community/tutorials/how-to-set-up-let-s-encrypt-certificates-for-multiple-apache-virtual-hosts-on-ubuntu-14-04 Cryptography app will use self signed till it's not valid anymore and then I will enable let's encrypt verified certificate.
18.11.2018 - These methods will use valid verified certificate for now on.
12.04.2017 I have generated self signed TLS (more secure than SSL) certificate for my server. Since it's self signed it's handled at application side in a way -> so if it's correct, connection is allowed --> meaning that Android app is shipped with clone of that certificate. I decided to use self signed cert cause signed ones seems to cost money, except "let's encrypt" provided ones. I go with self signed since it's easier to me and hey at least I didn't made app allow every TLS certificate it get's like many developers do.
Port 80 traffic is at 12.04.2017 closed for ever.
26.12.2017 - Correction => Signed certificate from Let's Encrypt is easier to set up than I thought, for example: www.digitalocean.com/community/tutorials/how-to-set-up-let-s-encrypt-certificates-for-multiple-apache-virtual-hosts-on-ubuntu-14-04 Cryptography app will use self signed till it's not valid anymore and then I will enable let's encrypt verified certificate.
18.11.2018 - These methods will use valid verified certificate for now on.
|
Here's the awesome little server Raspberry Pi 3 model b or it should be but it's working perfectly so rest doesn't matter. More interesting is Raspbian Jessie Lite config than device itself, hahaha!
I want to see how current amount of users can punch this device in the future. |
|
Here's an example of the first implementation using remote server api which is Argon2 and all it's modes.
When you create an hash, there's an progress bar coming in to the view for short period of time depending on your distance to my server. If progress bar won't go away in short period of time, there might be an issues with your connection or server is down. You get an alert about it after timeout limit is reached. One thing to note: I don't log nor monitor your inputs. Less I know, better I feel. If you have any questions feel free to use contact form. |
