Remote password
- Thread starter bananaman
- Start date
Hi bananaman,
You don't have to accept the device manually every time you connect. You can add the client device used for connection to the trusted list and it will let this device in without authorization (when connecting with ID or using device name).
The authorization fingerprint is created using machine GUIDs or mobile device ID so it is always unique and cannot be hacked.
We also recommend to lock the pc to always connect to the logon screen with the password for the PC account. You will see the "(locked)" state for this device on the device list if you are logged in to your Remotly account on this host/server machine.
In version 1.17.0 we we are switching to 14 digit/letter IDs. This is basically an ID with a password mixed together. There are 10^21 possibilities of such IDs so it is impossible to guess it. There is also a mechanism that bans users who try to somehow automate login with random IDs. Since it is not allowed to connect with an ID more than one time per second it would take 31709791983764 years to try all 14 digit/letter IDs
We think that all this + the upcoming TPM 2.0 support is enough to keep everyone safe and secure. But... we will add passwords in Remotly 2.0 too for all users who need it
You don't have to accept the device manually every time you connect. You can add the client device used for connection to the trusted list and it will let this device in without authorization (when connecting with ID or using device name).
The authorization fingerprint is created using machine GUIDs or mobile device ID so it is always unique and cannot be hacked.
We also recommend to lock the pc to always connect to the logon screen with the password for the PC account. You will see the "(locked)" state for this device on the device list if you are logged in to your Remotly account on this host/server machine.
In version 1.17.0 we we are switching to 14 digit/letter IDs. This is basically an ID with a password mixed together. There are 10^21 possibilities of such IDs so it is impossible to guess it. There is also a mechanism that bans users who try to somehow automate login with random IDs. Since it is not allowed to connect with an ID more than one time per second it would take 31709791983764 years to try all 14 digit/letter IDs
We think that all this + the upcoming TPM 2.0 support is enough to keep everyone safe and secure. But... we will add passwords in Remotly 2.0 too for all users who need it
Last edited:
Hi bananaman,
You don't have to accept the device manually every time you connect. You can add the client device used for connection to the trusted list and it will let this device in without authorization (when connecting with ID or using device name).
The authorization fingerprint is created using machine GUIDs or mobile device ID so it is always unique and cannot be hacked.
We also recommend to lock the pc to always connect to the logon screen with the password for the PC account. You will see the "(locked)" state for this device on the device list if you are logged in to your Remotly account on this host/server machine.
In version 1.17.0 we we are switching to 14 digit/letter IDs. This is basically an ID with a password mixed together. There are 10^21 possibilities of such IDs so it is impossible to guess it. There is also a mechanism that bans users who try to somehow automate login with random IDs. Since it is not allowed to connect with an ID more than one time per second it would take 31709791983764 years to try all 14 digit/letter IDs
We think that all this + the upcoming TPM 2.0 support is enough to keep everyone safe and secure. But... we will add passwords in Remotly 2.0 too for all users who need it
Alright thanks for the clarification. Cheer.