effem

Ok, thanks Francesco

Also in my opinion, you could leave the choice to the user. Those who wish may decide to enter a password to encrypt the departure of btsync (client side) their secret keys. The same password can be requested at the time of display of the keys in the GUI. So, in windows, there is the possibility to set a config file to change the directory location .sync? Francesco

I use only linux, and the problem I see much less noticeable! As you said, I can run with a user btsync ad hoc and block the permissions so much stronger than you could do a "simple" windows user. Maybe you did not understand: I really like the idea of secret keys! But I think it is much harder to find a decryption key in the process memory rather than reading the key in a file, especially if the majority of people who use windows put the keys in the same position! By the way, you can change the directory location .sync as in linux? Thanks, Francesco

Greetings to all, BTsync is really interesting. The problem with using your username and password rather than secret key is not given the difficulty of use. The problem, in my opinion, is that the password is not written anywhere and stays in people's heads. The secret key instead is written in clear on your pc and this can lead to being stolen. If a person physically takes possession of my computer for a few seconds can be seen in light of the secret key and send it anywhere. We must, in some way, do not write anywhere the secret key and the display of the same must be done with an additional password. At least as an additional feature for the truly paranoid The key in plain sight (especially in Windows) is not safe. Francesco