How to Choose the Best Password Manager in 2025
Infrastructure
05.06.2025
13 min read
Share
Although passwords are not considered the most secure method of authentication, they remain widely used for interacting with various services and applications. Today, more and more users face the need to manage dozens or even hundreds of passwords for different platforms. Storing them in notes, personal messages, or browser memory is not only inconvenient but also unsafe. To solve this problem, there are special types of password security software that not only store but also protect sensitive data, providing a secure space for your credentials.
The market offers dozens of password management tools. In this article, we’ll take a closer look at password manager software and examine their key features.
What Is a Password Manager?
A password manager is software designed for securely storing and using passwords and other confidential data.
Password managers simplify password handling by allowing users to remember just one code (commonly known as the master password) instead of multiple complex combinations. Most password managers also offer additional features, such as data breach monitoring, integration with third-party services, and support for storing other types of information like logins and payment card details.
They also minimize human error in security management. For example, they eliminate the need to invent and remember complex passwords by offering cryptographically secure auto-generated alternatives. This greatly reduces the risk of weak or reused passwords — one of the main causes of account compromise.
Key Features of Password Managers
Before diving into reviews of specific software products, it's important to outline the minimum essential features a password manager should offer:
Password Generation Service
This feature enables the creation of unique, long, and cryptographically strong passwords. A major advantage is having flexible settings to meet the requirements of various services (e.g., length, special characters, etc.).
Autofill
Automating the process of entering passwords improves user experience and streamlines interactions with the password manager. Browser, OS, and app integration allow autofill to speed up logins and reduce error rates.
Data Synchronization
Especially relevant for cross-platform password apps that run on multiple operating systems. Synchronization can be cloud-based or local. It ensures access to your private data from any supported device, anywhere. For security, encrypted data transfer channels are essential to minimize leakage risks.
Supported Security Measures
These include encryption (e.g., AES-256) and two-factor authentication (2FA). Some managers also support biometric authentication using fingerprint scanners or facial recognition.
Security Level
The most important criterion to prioritize. Ensure that the app uses modern encryption algorithms (specifically AES-256) and supports 2FA.
Regular security audits are also crucial. Many password manager developers publish the results of independent security checks, which builds trust.
Pricing
Depending on user needs, there are various pricing options. Free plans are good for basic use but may be limited (e.g., single-device access, no cloud sync). Paid plans offer expanded functionality, tech support, better security, and business features.
Open-Source Options
It’s also worth noting that free open-source solutions can offer functionality comparable to paid options.
Top Proprietary Password Managers
Now let’s review three popular proprietary password management services:
NordPass
NordPass is a password vault developed by Nord Security. It helps users keep their credentials safe with a user-friendly interface and secure storage.
Key Features
- Secure password storage: Unlimited encrypted password storage with cloud sync for cross-device access.
- Password generator: Automatically creates strong combinations; includes checks for length, special characters, and other criteria.
- Autofill: Streamlines login by auto-filling credentials on websites.
- Data breach monitoring: Scans accounts for potential compromise from hacks or data leaks.
- Offline mode: Allows access to stored passwords even without an internet connection.
Advantages
- Advanced encryption: Uses the XChaCha20 algorithm for data protection.
- Cross-platform support: Available for Windows, macOS, Linux, Android, and iOS; also includes browser plugins.
- Ease of use: Clean interface that is accessible even to non-technical users.
- Family and business plans: Offers flexible plans for individuals, families, and organizations.
Disadvantages
- Limited free version: The free plan only offers basic features and doesn’t include multi-device sync.
- Cloud-only storage: No local-only storage option, which may concern users who prefer full control over their data.
- Closed-source software: Unlike some competitors, NordPass is proprietary, which may deter open-source advocates.
Pricing Plans
- Free: Basic functionality with no sync across devices.
- Family: Supports up to six accounts.
- Business: Team management features for organizations.
Pricing varies by region and subscription length, with longer terms offering better value.
1Password
1Password is one of the most popular password managers, offering secure data storage and access control. It’s designed to enhance cybersecurity and protect accounts and sensitive information online.
Key Features
- Password storage: Secure login credential storage.
- Password generation: Built-in tool for creating strong, security-compliant passwords.
- Form autofill: Fast access to websites without manual data entry.
- Personal data storage: Supports storing not just passwords but also bank cards, licenses, notes, documents, and other important files.
- Leak monitoring: Alerts users in case of password leaks or data breaches.
Advantages
- Robust security: Uses top-tier encryption algorithms.
- Flexible organization: Create multiple vaults for different users or purposes.
- Cross-platform compatibility: Works on Windows, macOS, Linux, iOS, Android, with browser integration.
- Business solutions: Includes tools for team access control and administration.
Disadvantages
- No permanent free plan: Only a 14-day free trial is available, after which a subscription is required.
- Cloud-only storage: While convenient for syncing, some users prefer local-only data management.
Pricing Plans
- Individual: $2.99/month (billed annually) with full features and cross-device sync.
- Family: $4.99/month for up to 5 users with individual vaults.
- Teams Starter Pack: $19.95/month for up to 10 users.
Encryption AlgorithmDashlane
Dashlane is an app for storing passwords and confidential information that provides strong protection. The program helps users simplify access to credentials and protect them from unauthorized use.
Key Features
- Password storage: A secure vault for passwords from various websites and applications.
- Built-in password generator: A tool for creating reliable and unique character combinations.
- Autofill: Automatically fills in passwords, logins, financial, and other data on web pages.
- Data breach monitoring: A monitoring system warns about potential breaches and recommends password changes.
- Cross-device synchronization: Access your information from various devices, including PCs, smartphones, and tablets.
- Digital wallet: Secure storage for bank cards and payment details for convenient online shopping.
- Secure data sharing: Alerts about potential unauthorized access attempts and suggests password changes.
Advantages
- High level of protection: Uses AES-256 encryption and Zero-Knowledge architecture, ensuring complete privacy.
- User-friendly interface: Simple and intuitive UI suitable even for beginners.
Disadvantages
- Subscription cost: Dashlane is among the more expensive solutions, which may be a barrier for budget-conscious users.
- Limited functionality in the free version: The free plan offers only basic features and works on a single device.
Pricing Plans
- Free plan: Store up to 25 passwords on one device.
- Premium: $4.99/month. Includes credit monitoring and identity theft protection.
- Family plan: $7.49/month (billed annually), supports up to 6 users, each with their own vault.
Comparison Table
|
Criteria |
NordPass |
1Password |
Dashlane |
|
Free version available |
Yes |
Yes |
Yes |
|
Autosave |
Yes |
Yes |
Yes |
|
Passkey support |
Yes |
Yes |
Yes |
|
Data breach alerts |
Yes |
Yes |
Yes |
|
Multi-factor authentication |
Yes |
Yes |
Yes |
|
Email masking |
Yes |
Yes |
No |
|
Password generator |
Yes |
Yes |
Yes |
|
Supported devices |
Unlimited |
Unlimited |
Unlimited |
|
Family plan |
Yes (up to 6) |
Yes (up to 5) |
Yes (up to 10) |
|
Encryption algorithm used |
XChaCha20 |
AES-GCM-256 |
AES-256 |
Among proprietary password managers, we compared three programs: NordPass, 1Password, and Dashlane. All three offer similar functionality, differing mainly in the encryption algorithms they use. Each product also features a free version, allowing users to try it out and select the one that best suits their needs.
Top Open-Source Password Managers
In contrast to proprietary solutions, the market also offers open-source options. Notably, some open-source solutions can be self-hosted in your own infrastructure.
KeePass
KeePass is a popular free password manager for Windows that ensures secure storage of passwords and credentials. It operates in offline mode, providing maximum control over stored data.
Key Features
- Password management: Stores passwords accessible via a master password. Storage is limited only by vault size.
- Local data storage: User data is stored locally on the device, not in the cloud.
- Autofill: Automatically fills in data on websites and in apps.
- Cross-platform support: Versions exist for Windows, macOS, Linux, Android, and iOS.
Advantages
- High security: Supports multiple encryption algorithms, including AES-256, ChaCha20, and Twofish.
- Offline mode: No cloud dependency reduces the risk of data leaks.
Disadvantages
-
Cumbersome synchronization: Requires manual configuration for cross-device syncing.
KeePassXC
KeePassXC is a free, open-source, cross-platform tool for secure password storage. It is a modern adaptation of the original KeePass, tailored for use on Windows, macOS, and Linux.
Key Features
- Local encrypted storage: Data is stored locally and securely on the user's machine. No cloud dependency unless manually configured.
- 2FA support: Stores 2FA codes and integrates with hardware security keys (e.g., YubiKey).
- Autofill: Supports browser integration for auto-filling credentials.
- Cross-platform: Available on Windows, macOS, and Linux. Mobile access through compatible apps like KeePassDX for Android.
- Password generator: Customizable password creation tool.
Advantages
- Ease of use: Offers a more user-friendly interface than the original KeePass.
- Offline operation: Does not require cloud storage; all data remains local.
Disadvantages
- No official mobile apps: KeePassXC is limited to desktop; mobile support is only via third-party apps.
- Limited plugin options: Compared to KeePass, KeePassXC has fewer plugins available.
Bitwarden
Bitwarden is an open-source password manager popular for its reliability, simplicity, and transparency.
Key Features
- Password storage: Stores unlimited passwords with access from anywhere. Data is encrypted using AES-256.
- Password generator: Allows custom password generation based on length, character type, etc.
- Autofill: Automatically fills in credentials on websites and in apps.
- Cross-platform support: Available on Windows, macOS, Linux, Android, and iOS.
- Two-factor authentication (2FA): Supports 2FA via apps, email, or hardware tokens (e.g., YubiKey).
Advantages
- Open source: Public code base allows independent security audits.
- High security: Client-side end-to-end encryption ensures privacy even from Bitwarden developers.
- Affordable and accessible: The free tier includes many features often restricted in paid plans elsewhere.
- Local and cloud storage options: Can be hosted in the cloud or self-hosted for full control.
Disadvantages
-
Complex setup for beginners: Self-hosting and advanced configuration may be difficult for inexperienced users.
Pricing Plans
- Self-hosted: Users can deploy Bitwarden on their own server.
- Premium plan: $10/year, adds breach monitoring and 1 GB of encrypted file storage.
- Family plan: $40/year, supports up to 6 users.
- Business plan: Starts at $3/user/month, with advanced team management features.
Padloc
Padloc is a cross-platform, open-source password management app focused on simplicity and ease of use. It allows users to store, manage, and synchronize passwords across multiple devices.
Key Features
- Open Source: The project’s source code is available on GitHub and is distributed under the GPL-3 license.
- Cloud Synchronization: Supports storing data on cloud servers with an option for local encryption.
- Encryption Support: Utilizes AES-256 and Argon2 encryption algorithms.
- Cross-Platform: Available for Windows, macOS, Linux, Android, and iOS. Browser extensions are also available.
- Password Generator: Enables creation of strong passwords with customizable options.
Advantages
- Ease of Use: Minimalist and beginner-friendly interface.
- Team Collaboration Support: Allows sharing of passwords within a team.
Disadvantages
- No Offline Mode: Fully dependent on the cloud.
- Fewer Features Compared to Alternatives: Lacks features like 2FA support, SSH agent integration, and advanced security settings.
Pricing Plans
- Premium: $3.49/month. Includes 2FA support, 1GB of encrypted file storage, breach report generation, and note-taking functionality with Markdown support.
- Family Plan: $5.95/month. Includes all Premium features and allows up to 5 users.
- Team: $3.49/month. Includes Premium features and supports up to 10 user groups with flexible management.
- Business: $6.99/month. Includes all Team features and supports up to 50 user groups with flexible configuration.
- Enterprise: Price upon request. Includes all Business features, unlimited user groups, and custom branding options.
Psono
Psono is a password manager geared toward self-hosting and enterprise use. It can be deployed on a private server, giving users full control over their data. Psono offers strong security, team features, and multi-factor authentication (MFA).
Key Features
- Open Source: Source code is available on GitHub under the Apache 2.0 license.
- Self-Hosted: Can be deployed on a private server for full data control.
- Encryption Support: Uses AES-256, RSA, and Argon2 for encryption.
Advantages
- High Security: Supports modern encryption standards and hardware keys.
- Team Collaboration Support: Ideal for businesses and IT teams.
Disadvantages
-
Setup Complexity: Requires server deployment for full functionality.
Pricing Plans
- Self-Hosted: Free option for private deployment.
- SaaS Edition (Business): $3.50/month. Adds SAML & OIDC SSO, audit logging, and extended support on top of the free version’s features.
Comparison
|
Criteria |
KeePass |
KeePassXC |
Bitwarden |
Padloc |
Psono |
|
Cloud Sync |
No |
No |
Yes |
Yes |
Yes |
|
Auto-Save |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Passkey Support |
Yes |
Yes |
Yes |
No |
Yes |
|
Data Breach Alerts |
No |
No |
No |
No |
Yes |
|
Multi-Factor Authentication (MFA) |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Email Masking |
No |
No |
Yes |
No |
No |
|
Password Generator |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Supported Devices |
Single device |
Single device |
Unlimited |
Two (free version) |
Unlimited (paid) |
|
Family Plan Available |
No |
No |
Yes (up to 6 users) |
Yes (up to 5 users) |
No |
|
Encryption Algorithm |
AES-256, SHA-256, HMAC-SHA-256/512 |
AES256 |
AES-256 E2EE, salted hashing, PBKDF2 SHA-256 |
AES |
XSalsa20 + Poly1305 |
Conclusion
In this article, we explored password managers and thoroughly analyzed the most popular software solutions for secure information storage—both paid and free.
Each reviewed product has its own strengths and weaknesses. A well-chosen password manager can simplify the management of personal data and protect it from unauthorized access. When selecting a solution, it’s important to consider the functionality, security level, and ease of use.
Infrastructure
05.06.2025
13 min read
Share
Similar
Infrastructure
Virtualization vs Containerization: What They Are and When to Use Each
This article explores two popular technologies for abstracting physical hardware: virtualization and containerization. We will provide a general overview of each and also discuss the differences between virtualization and containerization.
What Is Virtualization
The core component of this technology is the virtual machine (VM). A VM is an isolated software environment that emulates the hardware of a specific platform. In other words, a VM is an abstraction that allows a single physical server to be transformed into multiple virtual ones.
Creating a VM makes sense when you need to manage all operating system kernel settings. This avoids kernel conflicts with hardware, supports more features than a specific OS build might provide, and allows you to optimize and install systems with a modified kernel.
What Is Containerization
Containers work differently: to install and run a container platform, a pre-installed operating system kernel is required (this can also be on a virtual OS). The OS allocates system resources for the containers that provide a fully configured environment for deploying applications.
Like virtual machines, containers can be easily moved between servers and provide a certain level of isolation. However, to deploy them successfully, it’s sufficient for the base kernel (e.g., Linux, Windows, or macOS) to match — the specific OS version doesn’t matter. Thus, containers serve as a bridge between the system kernel layer and the application layer.
What Is the Difference Between Containerization and Virtualization
Some, especially IT beginners, often frame it as "virtualization vs containerization." But these technologies shouldn't be pitted against each other — they actually complement one another. Let’s examine how they differ and where they overlap by looking at how both technologies perform specific functions.
Isolation and Security
Virtualization makes it possible to fully isolate a VM from the rest of the server, including other VMs. Therefore, VMs are useful when you need to separate your applications from others located on the same servers or within the same cluster. VMs also increase the level of network security.
Containerization provides a certain level of isolation, too, but containers are not as robust when it comes to boundary security compared to VMs. However, solutions exist that allow individual containers to be isolated within VMs — one such solution is Hyper-V.
Working with the Operating System
A VM is essentially a full-fledged OS with its own kernel, which is convenient but imposes high demands on hardware resources (RAM, storage, CPU).
Containerization uses only a small fraction of system resources, especially with adapted containers. When forming images in a hypervisor, the minimal necessary software environment is created to ensure the container runs on an OS with a particular kernel. Thus, containerization is much more resource-efficient.
OS Updates
With virtualization, you have to download and install OS updates on each VM. To install a new OS version, you need to update the VM — in some cases, even create a new one. This consumes a significant amount of time, especially when many virtual machines are deployed.
With containers, the situation is similar. First, you modify a file (called a Dockerfile) that contains information about the image. You change the lines that specify the OS version. Then the image is rebuilt and pushed to a registry. But that’s not all: the image must then be redeployed. To do this, you use orchestrators — platforms for managing and scaling containers. Orchestration tools (the most well-known are Kubernetes and Docker Swarm) allow automation of these procedures, but developers must install and learn them first.
Deployment Mechanisms
To deploy a single VM, Windows (or Linux) tools will suffice, as will the previously mentioned Hyper-V. But if you have two or more VMs, it’s more convenient to use solutions like PowerShell.
Single containers are deployed from images via a hypervisor (such as Docker), but for mass deployment, orchestration platforms are essential. So in terms of deployment mechanisms, virtualization and containerization are similar: different tools are used depending on how many entities are being deployed.
Data Storage Features
With virtualization, VHDs are used when organizing local storage for a single VM. If there are multiple VMs or servers, the SMB protocol is used for shared file access.
Hypervisors for containers have their own storage tools. For example, Docker has a local Registry repository that lets you create private storage and track image versions. There is also the public Docker Hub repository, which is used for integration with GitHub. Orchestration platforms offer similar tools: for instance, Kubernetes can set up file storage using Azure’s infrastructure.
Load Balancing
To balance the load between VMs, they are moved between servers or even clusters, selecting the one with the best fault tolerance.
Containers are balanced differently. They can’t be moved per se, but orchestrators provide automatic starting or stopping of individual containers or whole groups. This enables flexible load distribution between cluster nodes.
Fault Tolerance
Faults are also handled in similar ways. If an individual VM fails, it’s not difficult to transfer that VM to another server and restart the OS there.
If there’s an issue with the server hosting the containerization platform, containers can be quickly recreated on another server using the orchestrator.
Pros and Cons of Virtualization
Advantages:
Reliable isolation. Logical VM isolation means failures in one VM don’t affect the others on the same server. VMs also offer a good level of network security: if one VM is compromised, its isolation prevents infection of others.
Resource optimization. Several VMs can be deployed on one server, saving on purchasing additional hardware. This also facilitates the creation of clusters in data centers.
Flexibility and load balancing. VMs are easily transferred, making it simpler to boost cluster performance and maintain systems. VMs can also be copied and restored from backups. Furthermore, different VMs can run different OSs, and the kernel can be any type — Linux, Windows, or macOS — all on the same server.
Disadvantages:
Resource consumption. VMs can be several gigabytes in size and consume significant CPU power. There are also limits on how many VMs can run on a single server.
Sluggishness. Deployment time depends on how "heavy" the VM is. More importantly, VMs are not well-suited to scaling. Using VMs for short-term computing tasks is usually not worthwhile.
Licensing issues. Although licensing is less relevant for Russian developers, you still need to consider OS and software licensing costs when deploying VMs — and these can add up significantly in a large infrastructure.
Pros and Cons of Containerization
Advantages:
Minimal resource use. Since all containers share the same OS kernel, much less hardware is needed than with virtual machines. This means you can create far more containers on the same system.
Performance. Small image sizes mean containers are deployed and destroyed much faster than virtual machines. This makes containers ideal for developers handling short-term tasks and dynamic scaling.
Immutable images. Unlike virtual machines, container images are immutable. This allows the launch of any number of identical containers, simplifying testing. Updating containers is also easy — a new image with updated contents is created on the container platform.
Disadvantages:
Compatibility issues. Containers created in one hypervisor (like Docker) may not work elsewhere. Problems also arise with orchestrators: for example, Docker Swarm may not work properly with OpenShift, unlike Kubernetes. Developers need to carefully choose their tools.
Limited lifecycle. While persistent container storage is possible, special tools (like Docker Data Volumes) are required. Otherwise, once a container is deleted, all its data disappears. You must plan ahead for data backup.
Application size. Containers are designed for microservices and app components. Heavy containers, such as full-featured enterprise software, can cause deployment and performance issues.
Conclusion
Having explored the features of virtualization and containerization, we can draw a logical conclusion: each technology is suited to different tasks.
Containers are fast and efficient, use minimal hardware resources, and are ideal for developers working with microservices architecture and application components.
Virtual machines are full-fledged OS environments, suitable for secure corporate software deployment.
Therefore, these technologies do not compete — they complement each other.
10 June 2025 · 7 min to read
Infrastructure
Top RDP Clients for Linux in 2025: Remote Access Tools for Every Use Case
RDP (Remote Desktop Protocol) is a proprietary protocol for accessing a remote desktop. All modern Windows operating systems have it by default. However, a Linux system with a graphical interface and the xrdp package installed can also act as a server. This article focuses on Linux RDP clients and the basic principles of how the protocol works.
Remote Desktop Protocol
RDP operates at the application layer of the OSI model and is based on the Transport Layer Protocol (TCP). Its operation follows this process:
A connection is established using TCP at the transport layer.
An RDP session is initialized.
The RDP client authenticates, and data transmission parameters are negotiated.
A remote session is launched: the RDP client takes control of the server.
The server is the computer being remotely accessed.
The RDP client is the application on the computer used to initiate the connection.
During the session, all computational tasks are handled by the server. The RDP client receives the graphical interface of the server's OS, which is controlled using input devices. The graphical interface may be transmitted as a full graphical copy or as graphical primitives (rectangles, circles, text, etc.) to save bandwidth. By default, RDP uses port 3389, but this can be changed if necessary.
A typical use case is managing a Windows remote desktop from a Linux system. From anywhere in the world, you can connect to it via the internet and work without worrying about the performance of the RDP client.
Originally, RDP was introduced in Windows NT 4.0. It comes preinstalled in all modern versions of Windows. However, implementing a Linux remote desktop solution requires special software.
RDP Security
Two methods are used to ensure the security of an RDP session: internal and external.
Standard RDP Security: This is an internal security subsystem. The server generates RSA keys and a public key certificate. When connecting, the RDP client receives these. If confirmed, authentication takes place.
Enhanced RDP Security: This uses external tools to secure the session, such as TLS encryption.
Advantages of RDP
RDP is network-friendly: it can work over NAT, TCP, or UDP, supports port forwarding, and is resilient to connection drops.
Requires only 300–500 Kbps bandwidth.
A powerful server can run demanding apps even on weak RDP clients.
Supports Linux RDP connections to Windows.
Disadvantages of RDP
Applications sensitive to latency, like games or video streaming, may not perform well.
Requires a stable server.
File and document transfer between the client and server may be complicated due to internet speed limitations.
Configuring an RDP Server on Windows
The most common RDP use case is connecting to a Windows server from another system, such as a Linux client.
To enable remote access, the target system must be configured correctly. The setup is fairly simple and works "out of the box" on most modern Windows editions.
Enable remote desktop access via the Remote Access tab in System Properties.
Select the users who can connect (by default, only administrators).
Check firewall settings. Some profiles like “Public” or “Private” may block RDP by default. If the server is not in a domain, RDP might not work until you allow it manually via Windows Firewall → Allowed Apps.
If behind a router, you might need to configure port forwarding via the router’s web interface (typically under Port Forwarding). Recall that RDP uses TCP port 3389 by default.
Best RDP Clients for Linux
Remmina
Website: remmina.org
Remmina is a remote desktop client with a graphical interface, written in GTK+ and licensed under GPL. In addition to RDP, it supports VNC, NX, XDMCP, SPICE, X2Go, and SSH.
One of its key features is extensibility via plugins. By default, RDP is not available until you install the freerdp plugin. After installing the plugin, restart Remmina, and RDP will appear in the menu.
To connect:
Add a new connection.
Fill in connection settings (you only need the remote machine's username and IP).
Customize further if needed (bandwidth, background, hotkeys, themes, etc.).
Save the connection — now you can connect with two clicks from the main menu.
If you need to run Remmina on Windows, a guide is available on the official website.
FreeRDP
Website: freerdp.com
FreeRDP is a fork of the now-unsupported rdesktop project and is actively maintained under the Apache license.
FreeRDP is a terminal-based client. It is configured and launched entirely via the command line. Its command structure is similar to rdesktop, for example:
xfreerdp -u USERNAME -p PASSWORD -g WIDTHxHEIGHT IP
This command connects to the server at the given IP using the specified credentials and screen resolution.
KRDC
Website: krdc
KRDC (KDE Remote Desktop Client) is the official remote desktop client for KDE that supports RDP and VNC protocols.
It offers a clean and straightforward interface consistent with KDE's Plasma desktop environment.
KRDC is ideal for users of KDE-based distributions like Kubuntu, openSUSE KDE, and Fedora KDE Spin. It integrates well with KDE's network tools and provides essential features such as full-screen mode, session bookmarking, and network browsing via Zeroconf/Bonjour.
KRDC is actively maintained by the KDE community and is available through most Linux package managers.
GNOME Connections
Website: gnome-connections
Vinagre was the former GNOME desktop's default remote desktop client. GNOME Connections, a modernized remote desktop tool for GNOME environments, has since replaced it.
GNOME Connections supports RDP and VNC, providing a simple and user-friendly interface that matches the GNOME design language. It focuses on ease of use rather than configurability, making it ideal for non-technical users or quick access needs.
Features:
Bookmarking for quick reconnections
Simple RDP session management
Seamless integration into GNOME Shell
Connections is maintained as part of the official GNOME project and is available in most distribution repositories.
Apache Guacamole
Website: guacamole.apache.org
This is the simplest yet most complex remote desktop software for Linux.
Simple because it works directly in a browser — no additional programs or services are needed.
Complex because it requires one-time server installation and configuration.
Apache Guacamole is a client gateway for remote connections that works over HTML5. It supports Telnet, SSH, VNC, and RDP — all accessible via a web interface. Although the documentation is extensive, many ready-made scripts exist online to simplify basic setup.
To install:
wget https://git.io/fxZq5 -O guac-install.sh
chmod +x guac-install.sh
./guac-install.sh
After installation, the script will provide a connection address and password.
To connect to a Windows server via RDP:
Open the Admin Panel, go to Settings → Connections, and create a new connection.
Enter the username and IP address of the target machine — that's all you need.
The connection will now appear on the main page, ready for use.
Conclusion
RDP is a convenient tool for connecting to a remote machine running Windows or a Linux system with a GUI. The server requires minimal setup — just a few settings and firewall adjustments — and the variety of client programs offers something for everyone.
09 June 2025 · 6 min to read
Infrastructure
Docker Container Storage and Registries: How to Store, Manage, and Secure Your Images
Docker containerization offers many benefits, one of which is image layering, enabling fast container generation. However, containers have limitations — for instance, persistent data needs careful planning, as all data within a container is lost when it's destroyed. In this article, we’ll look at how to solve this issue using Docker’s native solution called Docker Volumes, which allows the creation of persistent Docker container storage.
What Happens to Data Written Inside a Container
To begin, let’s open a shell inside a container using the following command:
docker run -it --rm busybox
Now let’s try writing some data to the container:
echo "Hostman" > /tmp/data
cat /tmp/data
Hostman
We can see that the data is written, but where exactly? If you're familiar with Docker, you might know that images are structured like onions — layers stacked on top of each other, with the final layer finalizing the image. Each layer can only be written once and becomes read-only afterward. When a container is created, Docker adds another layer for handling write operations.
Since container lifespans are limited, all data disappears once the container is gone. This can be a serious problem if the container holds valuable information. To solve this, Docker provides a solution called Docker Volumes. Let’s look at what it is and how it works.
Docker Volumes
Docker Volumes provide developers with persistent storage for containers. This tool decouples data from the container’s lifecycle, allowing access to container data at any time. As a result, data written inside containers remains available even after the container is destroyed, and it can be reused by other containers. This is a useful solution for sharing data between Docker containers and also enables new containers to connect to the existing storage.
How Docker Volumes Work
A directory is created on the server and then mounted into one or more containers. This directory is independent because it is not included in the Docker image layer structure, which allows it to bypass the read-only restriction of the image layers for containers that include such a directory.
To create a volume, use the following command:
docker volume create
Now, let’s check its location using:
docker volume inspect volume_name
The volume name usually consists of a long alphanumeric string. In response, Docker will display information such as the time the volume was created and other metadata, including the Mountpoint. This line shows the path to the volume. To view the data stored in the volume, simply open the specified directory.
There are also other ways to create a Docker Volume. For example, the -v option can be added directly during container startup, allowing you to create a volume on the fly:
docker run -it --rm -v newdata:/data busybox
Let’s break down what’s happening here:
The -v argument follows a specific syntax, indicated by the colon right after the volume name (in this case, we chose a very creative name, newdata). After the colon, the mount path inside the container is specified. Now, you can write data to this path, for example:
echo "Cloud" > /data/cloud
Data written this way can easily be found at the mount path.
As seen in the example above, the volume name is not arbitrary — it matches the name we provided using -v. However, Docker Volumes also allow for randomly generated names, which are always unique to each host. If you’re assigning names manually, make sure they are also unique.
Now, run the command:
docker volume ls
If the volume appears in the list, it means any number of other containers can use it. To test this, you can run:
docker run -it --rm -v newdata:/data busybox
Then write something to the volume. Next, start another container using the exact same command and you’ll see that the data is still there and accessible — meaning it can be reused.
Docker Volumes in Practice
Now let’s take a look at how Docker Volumes can be used in practice. Suppose we're developing an application to collect specific types of data — let’s say football statistics. We gather this data and plan to use it later for analysis — for example, to assess players’ transfer market values or for betting predictions. Let’s call our application FootballStats.
Preserving Data After Container Removal
Obviously, if we don’t use Docker Volumes, all the collected statistics will simply be lost as soon as the container that stored them is destroyed. Therefore, we need to store the data in volumes so it can be reused later. To do this, we use the familiar -v option:
-v footballstats:/dir/footballstats
This will allow us to store match statistics in the /dir/footballstats directory, on top of all container layers.
Sharing Data
Suppose the FootballStats container has already gathered a certain amount of data, and now it's time to analyze it. For instance, we might want to find out how a particular team performed in the latest national championship or how a specific player did — goals, assists, cards, etc.
To do this, we can mount our volume into a new container, which we’ll call FootballStats-Analytics. The key advantage of this setup is that the new container can read the data without interfering with the original FootballStats container’s ongoing data collection. At the same time, analysis of the incoming data can be performed using defined parameters and algorithms.
This information can be stored anywhere, either in the existing volume or a new one, if needed.
Other Types of Mounts
In addition to standard volumes, Docker Volumes also supports other types of mounts designed to solve specialized tasks:
Bind Mount
Bind mounts are used to attach an existing path on the host to a container. This is useful for including configuration files, datasets, or static assets from websites. To specify directories for mounting into the container, use the --mount option with the syntax <host path>:<container path>.
Tmpfs Mount
Tmpfs mounts serve the opposite purpose of regular Docker Volumes — they do not persist data after the container is destroyed. This can be useful for developers who perform extensive logging. In such cases, continuously writing temporary data to disk can significantly degrade system performance. The --tmpfs option creates temporary in-memory directories, avoiding constant access to the file system.
Drivers
Docker Volume Drivers are a powerful tool that enable flexible volume management. They allow you to specify various storage options, the most important being the storage location — which can be local or remote, even outside the physical or virtual infrastructure of the provider. This ensures that data can survive not only the destruction of the container but even the shutdown of the host itself.
Conclusion
So, we’ve learned how to create and manage storage using Docker Volumes. For more information on how to modify container storage in Docker, refer to the platform’s official documentation.
09 June 2025 · 6 min to read
Do you have questions,
comments, or concerns?
Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
whether you need help or are just unsure of where to start.
