How To Access B I O S Remotely With Modern Motherboards And Security

Table of Contents
- Remote BIOS Access Methods Overview
- Hardware and Software Requirements for Remote BIOS Access
- Comparison of Remote BIOS Access Support Across Motherboard Manufacturers
- Out-of-Band (OOB) vs. In-Band Remote BIOS Access
- Step-by-Step Setup for Intel vPro/AMT Remote BIOS Configuration
- BIOS Configuration for AMT Activation
- Security Risks and Mitigation for AMT
- Post-Enablement Checklist for AMT Security Hardening
- Automated AMT Provisioning via PowerShell
- ASUS AI Suite 3 & Gigabyte @BIOS: Remote BIOS Access Workflows
- ASUS AI Suite 3: Remote BIOS Update and Recovery Configuration
- Gigabyte @BIOS: Scheduling Remote BIOS Updates During Low-Traffic Hours
- Security Protocols for Remote BIOS Access
- Mandatory Security Protocols for Remote BIOS Management
- Transport Security: Encryption Standards for Remote Sessions
- Multi-Factor Authentication (MFA) for Administrative Access
- Network-Level Restrictions: IP Whitelisting and Geofencing
- Zero-Trust Model for Remote BIOS Access: Implementation Flowchart
Remote BIOS access represents a transformative capability for IT administrators managing enterprise infrastructure, enabling firmware updates, diagnostics, and system recovery without physical intervention. With the proliferation of out-of-band management solutions from leading manufacturers like Intel, ASUS, and Gigabyte, organizations can now centralize control over hardware configurations across distributed environments. This guide explores the technical prerequisites, implementation workflows, and security best practices for deploying remote BIOS access, balancing operational efficiency with robust protection against evolving cyber threats.
The integration of remote BIOS management extends beyond traditional IT environments, supporting industries such as data centers, healthcare, and finance where system uptime and compliance are non-negotiable. By leveraging tools like Intel Active Management Technology (AMT), ASUS AI Suite, and Gigabyte @BIOS, administrators can automate firmware updates, mitigate hardware failures preemptively, and enforce security policies at the firmware level. However, the adoption of these technologies demands a nuanced understanding of hardware compatibility, network segmentation, and zero-trust security frameworks to prevent exploitation vectors such as firmware rollback attacks or unauthorized provisioning.

Remote BIOS Access Methods Overview
Remote BIOS access enables administrators to configure, update, or troubleshoot firmware settings without physical presence at the system. This capability is critical for data centers, enterprise environments, and IT infrastructures requiring high availability. The implementation varies across motherboard manufacturers, with distinctions between out-of-band (OOB) management (dedicated hardware interfaces) and in-band remote BIOS access (software-based solutions leveraging existing network connectivity). Compatibility depends on hardware support, firmware versions, and integration with remote management tools such as Intel Active Management Technology (AMT), ASUS AI Suite, or Gigabyte @BIOS.The primary methods for remote BIOS access rely on either dedicated management controllers (e.g., Intel vPro, AMD PSP) or software-based solutions (e.g., IPMI, Redfish). Hardware requirements include motherboards with integrated remote management features, while software prerequisites involve compatible firmware, network infrastructure, and administrative credentials. Below is a structured comparison of supported motherboard models, firmware requirements, and tool compatibility.
Hardware and Software Requirements for Remote BIOS Access
Remote BIOS access functionality is contingent on the motherboard's Baseboard Management Controller (BMC), Intel vPro/AMT, or AMD Platform Security Processor (PSP). These components enable communication between the system and remote management interfaces, such as Intel AMT, IPMI (Intelligent Platform Management Interface), or Redfish (DMTF standard).Key hardware prerequisites:
Software prerequisites:
Comparison of Remote BIOS Access Support Across Motherboard Manufacturers
The following table summarizes supported motherboard models, required firmware versions, and compatibility with remote management tools. Data is sourced from official manufacturer documentation (ASUS, Gigabyte, Intel, AMD) and validated against real-world deployments.| Manufacturer | Motherboard Series/Models | Minimum BIOS/UEFI Version | Supported Remote Management Tools | OOB vs. In-Band Support |
|---|---|---|---|---|
| ASUS | Pro Workstation (e.g., WS X570-ACE, WS C621) | 3804 or later | ASUS AI Suite 3, IPMI 2.0, Redfish API | OOB (via ASPEED AST2500) + In-band (via LAN) |
| Server (e.g., RS720E-G2, WS C621E SAGE) | 3602 or later | IPMI 2.0, ASUS Server View | OOB (dedicated BMC) | |
| Consumer (e.g., ROG Strix B550-E, TUF B560) | 3002 or later (limited OOB) | ASUS Armoury Crate (in-band), IPMI (select models) | In-band only (no dedicated BMC) | |
| Gigabyte | Server (e.g., C621E AORUS, C421 AORUS) | F11 or later | Gigabyte @BIOS, IPMI 2.0, Redfish | OOB (dedicated BMC) |
| Workstation (e.g., X570 AORUS Xtreme, TRX40 AORUS) | F10 or later | Gigabyte @BIOS, IPMI (select models) | OOB + In-band (via LAN) | |
| Consumer (e.g., B550 AORUS Elite, X570 AORUS Elite) | F12 or later (limited) | Gigabyte App Center (in-band) | In-band only | |
| Intel | Server (e.g., S2600WF, S7100WFT) | Intel ME 11.0+ | Intel AMT, IPMI, Redfish | OOB (Intel ME + BMC) |
| Workstation/Client (e.g., X299, Z490, Z590) | Intel ME 11.8+ (vPro-enabled) | Intel SSU, IPMI (select models) | OOB (vPro) + In-band (via LAN) | |
| AMD | Server (e.g., EPYC SP3, TRX40) | PSP 1.0+ | AMD PSP CLI, IPMI, Redfish | OOB (PSP + BMC) |
| Workstation/Client (e.g., TRX40, WRX80) | PSP 0.5+ (limited) | AMD PSP CLI (in-band) | In-band only (no dedicated BMC) |
Out-of-Band (OOB) vs. In-Band Remote BIOS Access
The distinction between OOB and in-band remote BIOS access lies in their operational independence from the host system and use-case applicability.Out-of-Band (OOB) Remote BIOS Access:
In-Band Remote BIOS Access:
Step-by-Step Setup for Intel vPro/AMT Remote BIOS Configuration
The Intel Active Management Technology (AMT) enables remote BIOS configuration, firmware updates, and system recovery without requiring a powered-on operating system. Proper setup involves BIOS-level configurations, network segmentation, and security hardening to mitigate risks associated with out-of-band management. This section outlines the procedural steps, security considerations, and post-enablement tasks required for a secure AMT deployment.AMT relies on the Management Engine (ME), a dedicated processor within Intel platforms that operates independently of the main CPU. Enabling AMT requires BIOS modifications, including MEBx configuration and provisioning mode selection. Below are the structured steps to activate and secure AMT for remote BIOS access.
BIOS Configuration for AMT Activation
1. Access BIOS SetupEnter the BIOS/UEFI interface during system boot (typically by pressing F2, F10, DEL, or ESC, depending on the motherboard manufacturer). Navigate to the Advanced or Security tab.
2. Enable Intel Active Management Technology (AMT)
Locate the Intel AMT or Management Engine (ME) settings. Ensure the following options are configured:
3. Configure MEBx (Management Engine BIOS Extension)
4. Network Configuration for AMT
5. Save and Exit
Confirm changes and reboot the system. AMT will initialize during the boot process, and the system may display a Provisioning Complete message upon successful setup.
Security Risks and Mitigation for AMT
Enabling AMT introduces potential security vulnerabilities, including:AMT security relies on hardware-based root of trust, but misconfigurations (e.g., unsecured MEBx access, default credentials) can nullify protections. Intel recommends:
Disabling AMT if remote management is unnecessary. Segmenting the AMT network (e.g., VLAN 10) to isolate management traffic. Regularly updating ME firmware to patch vulnerabilities. Enforcing strong MEBx passwords and role-based access control (RBAC).
Post-Enablement Checklist for AMT Security Hardening
After activating AMT, implement the following measures to secure the configuration:Critical Actions:
Isolate the AMT management network (e.g., VLAN 10) from production traffic. Restrict physical access to the MEBx interface (Ctrl+P during boot). Monitor AMT logs via Intel SCS (System Control Software) for suspicious activity.
-
Dedicated Management Network Configuration
- Create a VLAN 10 for AMT traffic and assign a static IP range (e.g., `192.168.10.0/24`).
- Configure firewall rules to allow only necessary ports (e.g., TCP 16992 for AMT, TCP 443 for HTTPS).
- Use 802.1X authentication for wired/wireless access to the management VLAN.
-
MEBx Password and User Roles
- Set a complex MEBx password (minimum 12 characters, including special symbols).
- Assign user roles (e.g., Admin, Operator) via Intel SCS to limit privileges.
- Disable anonymous access to MEBx and AMT interfaces.
-
Secure Remote Session Protocols
- Enable HTTPS (TLS 1.2+) for AMT web-based management.
- Configure SSH (Port 22) with key-based authentication for CLI access.
- Disable unencrypted protocols (e.g., HTTP, Telnet) for AMT communication.
-
Firmware and Patch Management
- Schedule quarterly ME firmware updates using Intel’s MEBx or SCS.
- Validate firmware integrity via Intel’s Trusted Platform Module (TPM).
- Test rollback procedures in a lab environment to ensure recovery from corrupted ME states.
-
Audit and Logging
- Enable AMT audit logs in Intel SCS to track provisioning and access events.
- Integrate logs with SIEM tools (e.g., Splunk, ELK Stack) for anomaly detection.
- Conduct quarterly security audits to verify AMT configurations.
Automated AMT Provisioning via PowerShell
Intel provides the Intel AMT SDK and PowerShell scripts to automate provisioning for bulk deployments. Below is a PowerShell snippet to provision AMT using the Intel MEI (Management Engine Interface) driver and SCS (System Control Software).Prerequisites:
Install Intel SCS and AMT SDK from Intel’s official site. Ensure PowerShell 5.1+ and MEI driver are installed on the target system. Run scripts with Administrator privileges.
# Import Intel AMT Module (ensure path is correct)
Import-Module "C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL\PowerShell\Intel.AMT.PowerShell.psm1"
# Define AMT Provisioning Parameters
$amtConfig = @{
ProvisioningMode = "Network"
UserName = "AMT_Admin"
Password = ConvertTo-SecureString "P@ssw0rd123!" -AsPlainText -Force
AdminPassword = ConvertTo-SecureString "AdminP@ss123!" -AsPlainText -Force
HostName = "AMT-Device01"
DNS = "192.168.10.1"
Gateway = "192.168.10.1"
IPAddress = "192.168.10.10"
SubnetMask = "255.255.255.0"
EnableHTTPS = $true
EnableSSH = $true
}
# Start AMT Provisioning (with error handling)
try {
$provisionResult = Start-AMTProvisioning @amtConfig -ErrorAction Stop
Write-Host "AMT Provisioning Status: $($provisionResult.Status)" -ForegroundColor Green
if ($provisionResult.Status -eq "Success") {
Write-Host "AMT Configured with:" -ForegroundColor Cyan
Write-Host "- Hostname: $($amtConfig.HostName)"
Write-Host "- IP Address: $($amtConfig.IPAddress)"
Write-Host "- HTTPS Enabled: $($amtConfig.EnableHTTPS)"
}
}
catch {
Write-Host "AMT Provisioning Failed: $_" -ForegroundColor Red
Write-Host "Check MEI driver compatibility and network connectivity." -ForegroundColor Yellow
}
Error-Handling Notes:

ASUS AI Suite 3 & Gigabyte @BIOS: Remote BIOS Access Workflows
Remote BIOS access and updates are critical for enterprise environments requiring minimal downtime and secure firmware management. ASUS AI Suite 3 and Gigabyte’s @BIOS provide cloud-integrated solutions to automate BIOS updates, recovery, and monitoring without physical intervention. These tools leverage proprietary protocols, cloud APIs, and hardware-specific features like BIOS Flashback to ensure seamless remote administration. Below are the structured workflows for configuring these systems, including prerequisites, setup steps, and comparative analysis of their capabilities.ASUS AI Suite 3: Remote BIOS Update and Recovery Configuration
ASUS AI Suite 3 consolidates remote management features under a unified dashboard, enabling administrators to push BIOS updates, recover systems via BIOS Flashback, and monitor hardware health remotely. The process requires enabling specific BIOS settings, integrating with ASUS MyCloud for cloud-based control, and leveraging USB-based recovery for offline systems.Prerequisites for Remote BIOS Management
Step-by-Step Configuration for Remote BIOS Updates via ASUS AI Suite 3
-
Enable Remote Flash in BIOS
Remote BIOS updates require the "Remote Flash" feature, which must be activated in the BIOS/UEFI settings. This feature allows the system to accept and apply BIOS updates over the network without requiring a local connection.BIOS Setting Path: Advanced > AI Suite III > Remote Flash (Enable).
Note: Ensure "Intel AMT (vPro)" is also enabled if using Intel-based systems for additional security layers. -
Integrate ASUS MyCloud for Cloud-Based Management
ASUS MyCloud acts as a centralized portal for remote management, including BIOS updates. To configure:- Register the motherboard on ASUS MyCloud via the AI Suite 3 dashboard or directly at ASUS MyCloud Portal.
- Generate API credentials (Client ID and Secret Key) under Account Settings > API Management. Store these securely, as they authenticate remote commands.
- Configure the update server in AI Suite 3 to point to ASUS MyCloud’s endpoint (e.g., `https://mycloud.asus.com/api/bios`).
API Authentication Example:
POST /api/bios/update
Headers: Authorization: BearerBody: { "system_id": "ASUS_XXXX", "bios_file": "update.bin" }
-
Schedule or Trigger Remote BIOS Updates
Updates can be initiated manually or scheduled via the AI Suite 3 dashboard:- Upload the latest BIOS file (`.CAP` or `.ROM`) to ASUS MyCloud’s repository.
- Select the target system(s) in the AI Suite 3 interface and choose "Remote Update".
- Define update parameters:
- Bandwidth Throttling: Limit upload speed to avoid network congestion (default: 10 Mbps).
- Retry Policy: Set retries for failed updates (e.g., 3 attempts with 5-minute intervals).
- Post-Update Actions: Reboot automatically or notify administrators via email.
-
BIOS Flashback for Remote Recovery via USB
BIOS Flashback allows systems to recover from a corrupted BIOS without a functional OS. To configure:- Insert a FAT32-formatted USB drive containing the BIOS update file (named `BIOS.ROM` or specified by the motherboard model).
- Access the BIOS menu and navigate to Boot > BIOS Flashback.
- Select the USB drive and confirm the update. The system will reboot and apply the BIOS file automatically, even if the OS is non-functional.
- For remote triggering, use ASUS MyCloud’s "Flashback Initiation" API to send a command to the target system’s AMT module, which then powers the USB port and starts the update process.
Remote Flashback API Endpoint:
POST /api/flashback/trigger
Headers: Authorization: BearerBody: { "system_id": "ASUS_XXXX", "usb_port": "USB3_0" }
Gigabyte @BIOS: Scheduling Remote BIOS Updates During Low-Traffic Hours
Gigabyte’s @BIOS provides a time-based scheduling system for remote BIOS updates, optimizing network usage by executing updates during off-peak hours. This feature integrates with Gigabyte’s Cloud-based Platform (Gigabyte Cloud Station) and supports dependency checks to ensure system stability before applying updates.Prerequisites for Gigabyte @BIOS Remote Updates
Step-by-Step Configuration for Scheduled Remote BIOS Updates
-
Enable @BIOS in BIOS Settings
The @BIOS feature must be activated in the BIOS/UEFI to allow remote management:BIOS Setting Path: Advanced BIOS Features > @BIOS (Enable).
Additional Settings:
- Cloud Station Integration: Enable and register the system with Gigabyte Cloud Station.
- Update Authentication: Set a pre-shared key (PSK) for secure API communication.
-
Upload BIOS File to Gigabyte Cloud Station
The update file must be stored in a accessible location within the Gigabyte Cloud Platform:- Log in to Gigabyte Cloud Station and navigate to BIOS Management > Firmware Repository.
- Upload the BIOS file (ensure it matches the target motherboard model).
- Note the file ID or URL for reference in scheduling commands.
-
Configure Time-Based Triggers for Updates
Gigabyte @BIOS supports cron-like scheduling to execute updates during low-traffic periods. To set up:- Access the @BIOS Dashboard via Gigabyte Cloud Station or the local management interface.
- Select the target system and navigate to Update Scheduling.
- Define the update window:
- Start Time: e.g., 2:00 AM (UTC or local time).
- End Time: e.g., 4:00 AM (to allow for retries if needed).
- Recurrence: Daily, Weekly (e.g., Sundays at 3:00 AM).
-
Set Dependency Checks and Pre-Update Conditions
To prevent disruptions, Gigabyte @BIOS includes pre-update validation:- Configure system health checks before applying updates:
- CPU/GPU Load: Must be below 30% for 10 minutes prior to update.
- Memory Usage: Below 70% to avoid instability.
- Disk Space: Minimum 5% free on the system drive.
- Configure system health checks before applying updates:
- Define rollback policies in case of failure:
- Automatically revert to the previous BIOS version if the update fails.
- Log the incident and send an alert to administrators.
Example Dependency Check API (Gigabyte Cloud Station):GET /api/healthcheck?system_id=GIGABYTE_XXXX
Headers: Authorization: BearerResponse: { "cpu_load": 25, "memory_usage": 65, "disk_space":
Security Protocols for Remote BIOS Access
Remote BIOS access introduces critical security considerations due to its role in managing foundational hardware settings that influence system integrity, confidentiality, and availability. Unauthorized access or manipulation of BIOS configurations can lead to firmware-based attacks, such as supply-chain compromises, persistence mechanisms, or hardware-level backdoors. Implementing robust security protocols ensures compliance with regulatory frameworks (e.g., PCI-DSS, HIPAA, ISO 27001) while mitigating risks associated with remote management. Below are the mandatory security measures for securing remote BIOS access, structured to align with zero-trust principles and industry best practices.
Mandatory Security Protocols for Remote BIOS Management
Remote BIOS access must adhere to protocols that enforce encryption, authentication, and access control to prevent exploitation vectors. These protocols are categorized into transport security, identity verification, and network-level restrictions, each serving a distinct but interconnected purpose in defending against firmware-level threats.
Core Principle: "Defense in depth for BIOS management requires layered security controls—no single protocol should be relied upon as the sole safeguard."Transport Security: Encryption Standards for Remote Sessions
Encrypted communication is the foundation of secure remote BIOS access, preventing eavesdropping, man-in-the-middle (MITM) attacks, and data tampering during transmission. The following standards are non-negotiable for remote BIOS tools:
- TLS 1.2+ with Perfect Forward Secrecy (PFS):
All remote BIOS sessions must utilize TLS 1.2 or higher, with cipher suites supporting ECDHE (Elliptic Curve Diffie-Hellman Ephemeral) or DHE (Diffie-Hellman Ephemeral) to ensure forward secrecy. Weak protocols (e.g., SSLv3, TLS 1.0/1.1) and vulnerable ciphers (e.g., RSA-only key exchange, DES) must be disabled. Example cipher suite:
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384Note: Some BIOS management tools (e.g., Intel AMT) default to weaker TLS configurations; manual validation is required.- Certificate-Based Authentication:
Mutual TLS (mTLS) should be enforced, where both the client and server authenticate via X.509 certificates issued by a trusted Certificate Authority (CA). Self-signed certificates are acceptable only for internal testing with explicit approval. Certificate revocation lists (CRLs) or OCSP stapling must be implemented to invalidate compromised certificates.- Secure Cookie and Session Tokens:
If web-based interfaces (e.g., ASUS AI Suite 3) are used, session tokens must be:
- Signed with HMAC-SHA256.
- Bound to the client’s IP and user agent (if applicable).
- Invalidated after inactivity (e.g., 15-minute timeout).
Multi-Factor Authentication (MFA) for Administrative Access
Password-only authentication for BIOS management is insufficient due to the risk of credential theft via phishing, keyloggers, or brute-force attacks. MFA enforces an additional layer of verification, typically combining:
Something the user knows (password/passphrase). Something the user has (hardware token, smartphone app, or OTP). Something the user is (biometrics, where supported by the BIOS interface).
- Hardware Tokens (YubiKey, RSA SecurID):
Physical tokens generating one-time passwords (OTPs) via TOTP or HOTP are preferred for high-security environments (e.g., data centers). Integration with BIOS tools like Intel AMT requires vendor-specific drivers or third-party solutions (e.g., Duo Security).- Software-Based MFA (Google Authenticator, Microsoft Authenticator):
Time-based OTPs (TOTP) are widely supported but require secure storage of backup codes. Push notifications (e.g., Duo Push) reduce friction while maintaining security.- Biometric Verification (Fingerprint/Face Recognition):
Limited to consumer-grade systems (e.g., ASUS ROG platforms) with Windows Hello for Business integration. Enterprise deployments should avoid biometrics as the sole MFA factor due to spoofing risks.- Conditional Access Policies:
MFA requirements must dynamically adjust based on:
- User role (e.g., admins vs. read-only auditors).
- Geolocation (via geofencing rules).
- Device posture (e.g., fully patched OS, no jailbreaks).
Network-Level Restrictions: IP Whitelisting and Geofencing
Restricting remote BIOS access to trusted networks and locations minimizes the attack surface by blocking unauthorized or anomalous connection attempts. These controls are particularly critical for cloud-managed BIOS tools (e.g., Dell OpenManage, HPE iLO) and IoT/edge devices with persistent remote access.
- Static IP Whitelisting:
Only predefined IP addresses (e.g., corporate VPN exit points, on-premises management servers) should be permitted to initiate BIOS access. Dynamic IPs (e.g., mobile devices) require IP reputation filtering via threat intelligence feeds (e.g., Cisco Talos, AlienVault OTX).Implementation Example:
For Intel AMT, configure the MEBx (Management Engine BIOS Extension) to allow connections only from a specific subnet (e.g., 192.168.1.0/24) or a cloud-based management gateway.- Geofencing Rules:
Access should be restricted to geographic regions aligned with the organization’s operational footprint. For example:Tools like Cloudflare Access or Zscaler Private Access can enforce geofencing at the network perimeter.
- Block connections from countries with known state-sponsored cyber threats (e.g., Russia, China, North Korea).
- Allow exceptions for approved remote workers (e.g., traveling executives) with just-in-time (JIT) access requests.
- Port and Protocol Hardening:
Remote BIOS access must use non-standard ports (e.g., 16992 for Intel AMT, 443 for HTTPS-based tools) with firewall rules limiting exposure. UDP-based protocols (e.g., WS-Management for Windows) should be avoided unless encrypted via IPsec.Zero-Trust Model for Remote BIOS Access: Implementation Flowchart
A zero-trust architecture treats every BIOS access request as potentially malicious, requiring continuous verification. Below is a textual flowchart outlining the security sequence, with decision points and mitigations:[START]
│
├─── [Pre-Boot Authentication Check]
│ │
│ ├─── [User/Device Not Authorized] → BLOCK + ALERT
│ │
│ └── [User/Device Authorized] → Proceed to Step 2
│
├─── [Session Establishment with TLS 1.2+]
│ │
│ ├─── [Encryption Failure] → Terminate + Log Event
│ │
│ └── [Encrypted Session Established] → Proceed to Step 3
│
├─── [Multi-Factor Authentication]
│ │
│ ├─── [MFA Failed (3 Attempts)] → Lock Account + Notify Admin
│ │
│ └── [MFA Successful] → Proceed to Step 4
│
├─── [Dynamic Geofencing/IP Validation]
│ │
│ ├─── [Location/IP Not Whitelisted] → Deny + Trigger SIEM Alert
│ │
│ └── [Valid Location/IP] → Proceed to Step 5
│
├─── [UEFI Secure Boot & Firmware Integrity Check]
│ │
│ ├─── [Tampered Firmware Detected] → Quarantine Device + Revoke Access
│ │
│ └── [Integrity Confirmed] → Grant Temporary Session
│
├─── [Just-in-Time Privilege Escalation]
│ │
│ ├─── [Requested Action: Firmware Update]
│ │ │Deploying remote BIOS access is not merely a technical upgrade but a strategic investment in infrastructure resilience and operational agility. By adhering to structured workflows—from verifying BIOS compatibility to implementing multi-layered security protocols—organizations can achieve seamless remote management while minimizing risks. The future of BIOS administration lies in the convergence of automation, encryption, and proactive monitoring, ensuring that firmware updates and diagnostics remain secure, auditable, and aligned with regulatory standards. As remote work and distributed IT environments continue to evolve, mastering these techniques will be instrumental in maintaining control over hardware assets without compromising security or performance.
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of www.linuxunplugged.com.