Rohos Logon Key Changelog

What's new in Rohos Logon Key 5.0 Preview

Feb 1, 2023
  • What’s new in Rohos Logon Key 5.0:
  • Improvements in ‘2FA bypass control’ feature. Now the special option “Rememebr 2FA” allows defining a time interval in seconds to reduce possible false-positive alarms. Also ‘2FA bypass’ events are now added to the authentication event log with IP address information.
  • Java Card support module is temporarily removed from the setup package to comply with Microsoft Defender.

New in Rohos Logon Key 4.8 (Aug 23, 2021)

  • Experimental ‘2FA bypass’ control
  • Minor improvements

New in Rohos Logon Key 4.7 (Aug 23, 2021)

  • Added a possibility to use U2F FIDO security keys for Windows remote desktop access. RemoteFX device redirection option in MS RDC should be used by Network Admins, to setup U2F keys on TS host side. “Rohos Logon Key compact” setup should be installed on client PC. More details read below.
  • Added support of 16/32 bytes HOTP tokens/keys and other minor improvements for One-Time-Password MFA method.
  • Added support for Omnikey RFID readers.
  • Added support for LastPass automated login with Rohos MFA Key, by inserting a password right to LastPass plugin via web browser extension. Rohos may enter your password right to LastPass login screen in Chrome/Firefox or some website. Current MFA Key is used as password storage. This is an experimental feature for those who prefer to keep LastPass locked after inactivity timeout.
  • Minor Improvements in Rohos Logon Key Push token MFA method. Added possibility to setup Smartphone login without entering user account password.
  • Added a possibility to enter a specific Username in the “Setup Key” dialog box, which allows to setup a key for users which cannot be resolved with the “Select Users” dialog provided by Windows API.
  • Improvements with Emergency Logon functionality with an online user account (email address is used).
  • Improvements with Emergency Logon functionality with online user account (email address is used).
  • Added a possibility to display Message Box in RDP login screen, thus populating Remote Access dialog full screen allowing user to enter OTP credentials (by using RDP_notice registry value).
  • Fixed issue with “Setup Key” dialog box when user password is empty
  • Added a possibility to Add MFA keys with a flag “user must enter password during next MFA login”. That allows to setup keys/cards without entering user account password.
  • Rohos Management Tools update.
  • Other bug fixing.

New in Rohos Logon Key 4.6 (Feb 2, 2020)

  • Allows to setup and login by using different type of Authentication methods. This allows to combine 2FA devices and use a particular available device depending on use case: at home, work or remote desktop access.
  • Improved MFA control for “Remote Desktop users from AD user group” rule.
  • Fixed FIDO U2F implementation for long user names.
  • Improved “Smartphone” MFA method (MFA Push token) for Active Directory networks.
  • Added experimental support of 3rd party OTP verification protocols: added LinOTP verification URL support.
  • Improved password renewal support for AD networks.

New in Rohos Logon Key 4.3 (Jan 29, 2020)

  • Added an option to control adaptivity level for face recognition.
  • Added possibility to use Face Login over a remote desktop connection.
  • Added option to control strong two-factor authentication to login into your computer.
  • Added Emergency Logon feature to bypass two-factor authentication if you cant login by face.
  • Added more options to customize Face Logon on logon screen.
  • Option “Face models profile path” allows to change folder location where rohos keep biometric data. This allows to set centralized location or network shared folder for face models across multiple users and computers.

New in Rohos Logon Key 4.0 (Mar 4, 2019)

  • Possibility to use multiple 2FA methods in parallel : keys like Yubikey, U2F, RFID and Google Auth OTP for remote sessions;
  • Twillio SMS gateway support for OTP based 2FA on Terminsal Servers;
  • Yubico v5 validation protocol and minor improvements on Microsoft Laptop;
  • Added Amazon WorkSpaces and Azure VDI computers support. Simple and cost effective MFA for remote desktops with Google Auth OTP or Yubikey devices;
  • Added experimental feature to disable OTP history for multiple times usage . TOTP token can be used with a long period (5hr) and will be valid multiple times, but only inside its predefined time period of one day;
  • Possibility to disable MFA for locked remote desktop sessions initially authenticated with MFA;
  • Display regular user accounts on logon screen. Those users who are without 2FA control can be displayed on logon screen.
  • Options > More > Show users
  • Rohos Management Tools improvements.

New in Rohos Logon Key 3.5 (Dec 22, 2017)

  • Whats new in Rohos Logon Key 3.5:
  • Rohos now disables Windows 10 lock screen feature to speed-up authentication process. This eliminates the requirement to press any-key on a keyboard to close Lock screen picture.
  • (Rohos modifies registry key HKEY_LOCAL_MACHINE SOFTWAREPoliciesMicrosoftWindowsPersonalization, NoLockScreen=1)
  • Added support of RFID reades by RFIDeas.com. “Wave ID” pcProx, plus, nano, writer. Rohos uses RFIDeas API to read RFID tag serial number via USB connection. Keyboard output is not required. A great variety of 125 kHz cards are supported: HidProx, Indala, EM410x etc.
  • Added network mode support for Active Directory networks. Now Rohos Logon Key automatically detects the presence of its database in Active Directory and switches to use domain-wide 2FA settings and 2FA devices controls which are set by using Rohos Management Tools installed on Domain Controller. A few improvement was made in Rohos Logon Key network mode:
  • Custom “Wrong PIN”, “Wrong 2FA device” messages;
  • Custom value for the Maximum number of wrong PIN attempts for 2FA devices like RFID tags;
  • New option “RFID devices KCY/pcProx” was added to Rohos Remote Config;
  • Auditing of all 2FA events, Emergency logons, Wrong PIN entries, etc.

New in Rohos Logon Key 3.4 (Jun 26, 2017)

  • Rohos Logon automatically detects Active Directory during install and uses it’s settings from the domain:
  • Each time during user authentication procedure Rohos reads it’s setting from the Active Directory.
  • On each 2 factor authentication authentication attempt Rohos verifies authentication media serial number or device id by using the list of allowed devices from the Active Directory database.

New in Rohos Logon Key 3.1 (Nov 29, 2013)

  • New features:
  • Improved “Allows to login only by USB Key” option
  • New option “Check Key serial” that control the list of keys accepted for login
  • Customizable text notices for a user: Rohos Logon installation notice, Rohos Logon main window notice, setup key notice and logon screen notice text
  • Users and Keys dialog box to view and manage configured users and keys
  • License policy changes: Rohos Logon Key server license for Terminal Server. License policy is per PC now. RFID token license is disabled
  • Rohos Key Management Tools is now freeware

New in Rohos Logon Key 3.0 (Mar 14, 2013)

  • Google Authenticator support – one time passwords (OTP) generator from Google.
  • New settings and bugs fixed for wireless key - “Wireless PC Lock” – based on RFID technology.
  • New settings features have been added for easyident FS- 2044 wireless reader equipped with elegant tags in the shape of EM 4100 watches.
  • Auto Logoff Timer
  • Yubikey – we have introduced import/export of the key settings. PIN code feature has been disabled.

New in Rohos Logon Key 2.9 (Sep 21, 2012)

  • When you use “Allow to login only by USB Key” feature, you may define a set of users that will be able still to login by a regular password (without USB Key). Please note:
  • - Current user name is added to this list automatically by default .
  • - We recommend to set it to Terminal Server administrator user name
  • - If it is blank: regular password based login will be disabled for any user (ensure that you have defined Emergency Login or have a valid USB Key)
  • - Rohos Icon in Credentials Prompt dialog box allows any user name credential to be entered manually.
  • On the Windows 7/2008 logon screen you have Rohos logon icon.
  • Now it contains User name and password fields. This is designed specially for network Admins to be able to access computer in a regular way locally or via Remote Desktop.
  • User Account Control credentials prompt with Rohos icon. Now you can regular use here User Name and password. Please note - this credentials prompt accepts USB Key or any user name and password entered manually.
  • On Windows 7/ 2008 Rohos logon key creates “Rohos Logon Key (User)” shortcut that allows regular users to setup and manage USB Key for Windows authentication.
  • Rohos Logon Key allows to setup redirected USB flash drive as a Login Key for Windows Remote Desktop. On the screenshot “\\tsclient\G” is a USB flash drive connected to client PC. After setting up this USB drive it will contain also portable Rohos components to login into Remote Desktop from any PC with this Key (without installing Rohos on it)

New in Rohos Logon Key 2.7 (Sep 9, 2009)

  • Now Rohos Logon supports eToken PRO in Windows Vista x64. We have run compatibility tests with eToken PKI Client 5.0 SP1 for Windows Vista/XP x64. The result is a SUCCESS!
  • Fixed YubiKey support for Windows x86/x64 bug
  • Fixed error in Windows Seven/Vista when using USB Key + PIN in Credentials Prompt dialog box (UAC).

New in Rohos Logon Key 2.6 (Jan 25, 2009)

  • Experimental support for Windows 7.
  • improved "Windows welcome screen + Rohos" logon model when using
  • "Allow only USb Key logon" option.
  • fixed bug in "Rohos welcome screen" logon model under Windows 2000.
  • Added support for YubiKey One-time-password token, that includes
  • remote OTP validation and decryption.
  • Updated server version with "Manage USb keys" dialog box (for Yubikey)
  • Multilanguage setup
  • fixed minor issues in 'Rohos welcome screen (gina.dll)' logon model

New in Rohos Logon Key 2.5 (Mar 21, 2008)

  • Support for USB tokens ruToken, Aladdin eToken PRO/R2, uaToken. Support for any PKCS11 tokens and smart cards.
  • In order to try another PKCS11 compatible USB token you should put down its module name in the registry: HKEY_LOCAL_MACHINESOFTWARERohos "USBKeyPkcs11" = "%dll name%"
  • Support for Wireless Logon on the base of BlueTooth enabled mobile or
  • PocketPC. Access to Windows by using mobile phone.
  • Support for Biometric USB flash drives(Transcend, Apacer).
  • Enhanced Server Version with USB Keys Remote Setup and the program options
  • Emergency Logon enhancements.
  • Fix Windows Vista x64 support: Emergency Logon, error on changing in between logon models.
  • Fix on Windows Vista: Hibernate/Shutdown PC options after USb Key removal.

New in Rohos Logon Key 2.4 (Aug 10, 2007)

  • Added AMD64 version of Rohos Credential Provider for Windows Vista.
  • Now Rohos Logon Key offers full support for Windows Vista including: Vista Remote Desktop login via USB key, change password screen (via CAD) with USB Key update and all USb Key removal options such lock,logoff...
  • This is possible thanks to Rohos Credential provider component specially designed to enchance or replace typical Vista authentication.
  • To use new feature you need to install Rohos Logon Key v2.4, change Logon Model (via Configure Options dialog) to "Rohos
  • Credential Provider" and restart
  • Fixed bug: (Logon model 'Native Windows msgina.dll') When login via
  • Remote Desktop Connection with pre-defined user name and password, then 'Allow only USB Key login' policy doesnt worked.
  • Added registry tweak to customize welcome screen text's color:
  • Path: HKEY_LOCAL_MACHINESOFTWARERohos
  • DWORD: HeaderTextColor
  • this is a color value in form 0xBBGGRR (Blue Green Red) For example: 2288ff
  • Added registry tweak:
  • Path: HKEY_LOCAL_MACHINESOFTWARERohos
  • DWORD: DisableUSBatRDP.
  • Program will ignore USB key at RDP session login.
  • DWORD: NativeGinaAtRPD
  • With logon mode "Rohos gina.dll" run native gina when working via remote session.
  • Immproved Windows Vista support. "Only USB key login" feature works.
  • Improved "Rohos welcome screen (gina.dll)" logon model when working via remote desktop.
  • Improved Novell Client support. "Only USB key login" feature works.
  • Emergency Logon feature allows to access your system if
  • - USB Key lost or damaged;
  • - "only USB Key login" is enabled;
  • - you forget PIN code;
  • Added Safe Mode support. Now Rohos protects your computer even in Safe Mode boot-up thus prevents anyone access Windows by usual password avoiding the USB Key.
  • Fixed "Disabling USB flash drives for users" feature that didnt work under some conditions.
  • fixed bugs in Remote Login component. (use unauthorized Key duplicates, strange behaviour while RDP login).
  • Added registry tweak:
  • Path: HKEY_LOCAL_MACHINESOFTWARERohos
  • DWORD: DisableBaloonInstructions.
  • 1- Rohos will not provide any instructions on the screen regarding the use of the USB key, which is something that an unwelcome user doesn't need to know.
  • USB Key Administration utility now set full copy-right protection options for created USB Keys.

New in Rohos Logon Key 1.8 (Aug 17, 2006)

  • Added Network support. Now USB stick can contain network user profile for login operations.
  • Supports multiple accounts stored on USB stick.
  • Added Password improvement function. (generates strong password and keep it on the USB stick);
  • Password rotation was improved. If it is required by the windows policy Rohos will change password automatically.
  • Administrator's utility for USB key issuing and managing;http://www.rohos.com/network.htm; can create USB login Key and setup PIN code in multiuser environment.
  • fixed bugs with WinXP native welcome screen login.
  • Added Novell Netware login support (with installed Novel Client 4.*);
  • Rohos Welcome does not replace NWGINA.DLL but closely integrates with it; the login password entered automaticaly into Novell Netware Login dialog box; This solution keeps existing network authentication procedures but adds Two-factor authentication;