If you use Google's two-step verification feature, you will stumble upon an authentication error with SIM Manager, when attempting to synchronize your SIM with the online phonebook.
Two-step authentication is something that can easily slip out of your mind, so you may think that the problem is with your password, or with the software. After repeated attempts to synchronize your phonebook, you just give up (and maybe blame it on SIM Manager)
To fix this, you have to create an application-specific password in your Google account settings, and use that password with SIM Manager.
Log onto your Gmail account and click account settings
Edit your two-step verification settings
Click Manage application-specific passwords
Generate a password for SIM Manager
Use this password with SIM Manager
That's it. Have fun synchronizing your contacts!
p.s. the password in the screenshot has been changed, don't try to use it ;-)
A fresh version of smart card Logon for Windows 7 x64 is now available: httx://dl.dropbox.com/u/3258602/DKbeta/Logon-x64.msi
The software is also compatible with:
This is a free version without any feature limitations. Get it while it is hot! ;-)
A fresh beta of Logon for Vista is now available for download: http://files.dekart.com/beta/Logon-2.23.1-TVMonday.msi
The Citrix ICA client can be migrated to a removable disk, so you can connect to Citrix servers without having to install a client locally. This can be paired with Dekart Logon for Citrix, which can also run from removable media. As a result, a bundle is obtained, offering you a secure way to connect to remote servers.
How does it work?
Edit C:\Program Files\Citrix\ICA Client\WFCLIENT.INI, by adding
Here is a set of points that emphasize the benefits of a smart-cart or token-based authentication solution, coupled with biometric authentication; the example is focused on Dekart Logon for Citrix, but it also applies to other user authentication software by Dekart.
Q: what are the benefits of using your product? Am I simply substituting a PIN for a user/password combination? And can an external user without a flash drive or smart card still access the server?
A: Dekart Logon for Citrix is not a server-side application, it should be used on the clients.
The benefits can be summarized as:
the software can also be used with flash disks, being entirely self-contained:
In this case the user is immune to keyloggers. Even if the keylogger manages to capture the PIN:
And as a side effect, this also means that unloyal end-users won't be able to disclose confidential data even if they want to. In other words, you can implement the "need to know" approach, by not giving users more information than they actually need to get their work done.
The data stored on USB drives are encrypted with AES-256 bit, our implementation of the algorithm is certified by NIST. This is much stronger encryption than the one used by the Citrix client itself.
Q: And can an external user without a flash drive or smart card still access the server?
A: Technically, this is possible, but you can counter that by:
You will probably want to take a look at Key Manager, this is the tool that allows you to write credentials to keys, make copies, edit contents of a key, etc.
Note - you can do these with Dekart Logon for Citrix itself, but if you're planning to operate with many keys (in a corporate environment), you'll find Key Manager very useful. A license for the tool is given for free if a certain number of licenses for Logon for Citrix is purchased.
Q: Couldn't someone with a citrix client installed on their machine get to my server logon screen on the remote machine and execute a brute force attack there?
A: Although that is technically possible, it is not an optimal scenario for the attacker to use:
In other words, a local brute-force attack can take thousands or millions of years, while doing it over the network is totally insane. It may only work for trivial passwords such as '11111' or ones that can be found in any dictionay. But even in that case, a dictionary attack won't be feasible if the network admin took the right measures and prevents one from physically connecting to the server if they've had too many unsuccessful attempts.
Finally, the last detail is that you can use randomly generated passwords, which are extremely long - brute forcing THAT is impractical.
If I were an attacker, I'd try to find alternative ways, such as social engineering applied against a naive employee.
2g 3g adapter authentication beta biometry «blue screen» bsod business cdma driver email encryption «file system» forensics form-filling google gsm howto internet keeper keylogger logon mobile name password «password carrier» portability privacy «private disk» release security seven sim «sim card» «sim manager» «sim reader» «smart card» software synchronization tips token troubleshooting usb usim vista windows «windows 7» wiping xp