Our Blogs

GitLab 8.9 gets better with file locking, hardware U2F support

June 30, 2016
GitLab 8.9 has been released with a refreshed UI with support for hardware-based two-factor authentication. The latest release provides the ability to automatically lock a binary file, thus keeping anyone except the locker from modifying a particular file or directory. These features are necessary for game or imaging assets in which conflicts are not easily resolved.

According to Hacker News user sdesol, the need for enterprise products enables you to reduce risk. This is because a simple problem can lock an entire company. If you are a domain expert, you will make use of the new features included with GitLab 8.9.

Eventhough mistakes can't be avoided in the open source world, is's easy to wash the hands if you an indivdual. However, it will be costly affair for enterprises since it will result in loss of money.

Coming to the UI front, things have changed since the project navigation bar on the top of the screen moved out from its original position on the left. You will continue to view system-wide navigation on the left side but with an option to automatically hide it when not in use.

The latest release of GitLab provides support for FIDO Universal 2nd Factor (U2F) authentication in association with Yubico to work with YubiKey devices. Even though two-factor authentication was available with the rapid emergence of mobile phones and a TOTP code, the use of a hardware YubiKey and the Chrome browser can speed up the process.

You need not have to provide the 6-digi code. Instead, a developer can plug in the USB key and have their session automatically authenticated. You will be eligible to get Firefox support behind a flag in the nightly version.

As a developer, you will be able to add U2F support to their own applications using Yubico's developer resources. If you are unaware, YubiKeys are used in some large companies such as Google, Facebook, and Salesforce for securing employee access to resources.