PQE-369 Repository Documentation

Complete Repository Documentation

Everything you need to get started with PQE-369 Maximum Security OS packages

Client Setup

Step-by-step instructions to configure your system to use the PQE-369 repository

Repository Endpoints

Learn about available repositories and their purposes

Security & Verification

Understand how package signing and verification works

📋 Client Setup Guide

Follow these steps to add the PQE-369 repository to your Debian-based system:

Import the signing key:
```
wget -qO - https://repo.ross-developers.com/keys/pqe369.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/pqe369.gpg > /dev/null
```
This command downloads and imports the GPG public key used to verify package signatures.

Add repository sources:

sudo tee /etc/apt/sources.list.d/pqe369.list > /dev/null << EOF
deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/pqe369.gpg] https://repo.ross-developers.com/pqe369/release stable main
deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/pqe369.gpg] https://repo.ross-developers.com/pqe369/security security main
EOF

Adds both release and security repositories to your APT sources.

Update package lists:
```
sudo apt update
```
Refreshes the package database from all configured repositories.
Install packages:
```
sudo apt install <package-name>
```
Install packages from the PQE-369 repository as you would from any Debian repository.

📦 Repository Endpoints

The PQE-369 repository consists of multiple endpoints, each serving a specific purpose:

Release Repository

https://repo.ross-developers.com/pqe369/release

Stable release packages for production use

Security Repository

https://repo.ross-developers.com/pqe369/security

Security updates and patches for PQE-369 systems

Verification & Security

All packages in this repository are:

✓ Cryptographically signed with GPG
✓ Distributed over TLS/HTTPS only
✓ Regularly updated and maintained
✓ Tested for compatibility with PQE-369 Maximum Security OS

The repository uses strong cryptographic signatures to ensure package integrity and authenticity. Never bypass GPG verification when adding the repository.

❓ Troubleshooting

GPG Key Import Issues

If you encounter errors importing the GPG key:

# Check if key file exists
ls -la /etc/apt/trusted.gpg.d/pqe369.gpg

# Verify key format
file /etc/apt/trusted.gpg.d/pqe369.gpg

Package Not Found

If packages aren't found after adding the repository:

# Update package lists
sudo apt update

# Check repository configuration
cat /etc/apt/sources.list.d/pqe369.list

# Verify repository is accessible
curl -I https://repo.ross-developers.com/pqe369/release/

Signature Verification Failures

If you see signature verification errors:

# Re-import the GPG key
wget -qO - https://repo.ross-developers.com/keys/pqe369.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/pqe369.gpg > /dev/null

# Update and clean APT cache
sudo apt update
sudo apt clean

PQE-369 Secured OS Packages Repository