4

Closed

Beta 4 feedback!

description

Just installed, here you are the first report!
 
 
the msi setup force you to remove first the previous version, it would be nice if an upgrade will be supported
into the Organize favorites windows, clicking on an item will immediately activate the
edit of the name, personally I prefere to just select the row!
 
a double click will first activate the edit of the name and then open the edit window, as per the above this action should just open the edit window
I do not like the new change logic, one has to remember the shortcuts or go to Edit and then select a sub-option; to me was better before
 
at logof/close of the remote connection the Terminals' window is still quickly
flashing my log is still full of decript errors (I do not have a master password set)
ERROR 2011-11-28 09:28:33,312 319806ms Terminals DecryptPassword - Error Decrypting Password
System.Security.Cryptography.CryptographicException: Parametro non corretto.
 
in System.Security.Cryptography.ProtectedData.Unprotect(Byte[] encryptedData, Byte[] optionalEntropy, DataProtectionScope scope)
in Terminals.Security.PasswordFunctions.DecryptByEmptyKey(String encryptedPassword)
in Terminals.Security.PasswordFunctions.DecryptPassword(String encryptedPassword, String keyMaterial)
ERROR 2011-11-28 09:33:40,979 627473ms Terminals DecryptPassword - Error Decrypting Password
System.Security.Cryptography.CryptographicException: Parametro non corretto.
 
in System.Security.Cryptography.ProtectedData.Unprotect(Byte[] encryptedData, Byte[] optionalEntropy, DataProtectionScope scope)
in Terminals.Security.PasswordFunctions.DecryptByEmptyKey(String encryptedPassword)
in Terminals.Security.PasswordFunctions.DecryptPassword(String encryptedPassword, String keyMaterial)
 
each time I opend an RDP connection I get a "logon error -2 without any description"
 
ERROR 2011-11-28 09:36:01,550 768044ms Terminals lient_OnLogonError - There was a logon error returned from the RDP Connection, details:
Logon Code:-2
Logon Description:

file attachments

Closed Dec 6, 2011 at 10:45 PM by RobChartier
Associated with 94633

comments

pstemper wrote Nov 30, 2011 at 6:30 PM

I get the same "logon error -2", plus, but it happens AFTER I manually type my password, as the "automagically logon with the saved credentials" no longer seems to work for any of the connections. If I switch back to the older version of terminals, it works.

richarddeeming wrote Dec 2, 2011 at 12:57 PM

Same logon error here:

ERROR 2011-12-02 13:53:48,555 26210ms Terminals lient_OnLogonError - There was a logon error returned from the RDP Connection, details:

Logon Code:-2

Logon Description:


The connection still logs in, and I can use it as normal after I acknowledge the error message.

nielsvdc wrote Dec 3, 2011 at 8:00 AM

The message popup with "Logon Code: -2" is fixed. It was showing messages that aren't really errors but notifications of the state of Windows. Most of the time Windows was showing the same messages.

echoDreamz wrote Dec 6, 2011 at 6:03 PM

I too have this issue. I can login to the RDP server without issues, but I get the popup warning (There was a logon error returned from the RDP Connection, details:
Logon Code:-2
Logon Description:)

RobChartier wrote Dec 6, 2011 at 8:15 PM

"logon error -2", issue has been fixed.

Looking at the crypto errors

RobChartier wrote Dec 6, 2011 at 8:20 PM

so the current immplentation works as expected, but with new passwords
I wonder if the issues here are existing passwords using the old scheme (without "keyMaterial") misbehaving using the new setup.

echoDreamz wrote Dec 6, 2011 at 8:50 PM

Rob, is this a new beta coming that fixes this error?

RobChartier wrote Dec 6, 2011 at 9:19 PM

The login error is fixed, the security error is one which I'm trying to get ironed out right now.

RobChartier wrote Dec 6, 2011 at 9:46 PM

@echoDreamz : Can you try this:

Find a favourite which is throwing the crypto exception (repro the issue). Then manage that favourite and update the password value and try again?

Let me know

Thanks.

jirkapok wrote Dec 6, 2011 at 9:55 PM

Yes, there was a bug in usage of empty keys and key material. But it is still possible, that the error messages in log comm from not updated passwords in stored credentials or favourite passwords.

RobChartier wrote Dec 6, 2011 at 10:45 PM

So the solution for the decrypt password is not 100% perfect but it is a solution.

If you edit the connection which has an invalid password then you will get a message letting you know that you must reset and save the password. This has been checked in and will be in the next build.

echoDreamz wrote Dec 6, 2011 at 11:36 PM

@Rob, all favs are doing this. All my favorites use the credentials manager (All use the same AD user). I have updated my credentials in the credentials manager, but they still throw this.

Grimolfr wrote Dec 22, 2011 at 1:05 PM

I'm getting a similar logon error w/ Logon Code:3, but so far I've only gotten it from one remote server.

I do not store my password in terminals for auto-logon, as my passwords change to frequently and I don't want it to contribute to locking me out of those environments. I do, however, have terminals store the domain & user name for this connection.

It would appear that terminals is attempting to perform an auto-logon even though there's no password specified.

ctbrasel wrote May 31, 2012 at 1:46 PM

I see this issue was closed but it is not clear what the fix is. What can I do to fix the Logon Cod: -2 issue as others have described above?

GiangiRE wrote May 31, 2012 at 2:29 PM

You have tu use the Final v2.0 version!

Sign in to add a comment