Skip to main content
SQLOZ
Funcționalități Documentație Prețuri Foaie de parcurs Blog Povestea noastră Disponibil în Mac App Store
Chapter 16 OzSuite™ AI & Advanced Tools

Chapter 16: OzTeam - Encrypted Profile Exchange

Info: This chapter explains securely exporting and importing database connection profiles as AES-256-GCM encrypted .sqlozprofile capsules, and the cryptographic security architecture.

In this chapter:

16.1 Overview

Sharing database connection details (host, port, database name, vendor, user, and optionally a password) with teammates carries two main risks:

  1. Plaintext password leakage: Sending information as plaintext over Slack, Teams, email or WhatsApp, where it remains in the platform’s history.
  2. Complex setup: The effort of placing SSH Jump Host and CA certificate files correctly in each environment.

OzTeam converts the supported connection profile fields into a single .sqlozprofile capsule using 256-bit AES-GCM encryption. SSH and certificate material is not part of the exported profile payload.

16.2 Exporting a Profile

To share one or more connection profiles:

  1. Right-click the connection profile in the left sidebar.
  2. Choose Export Profile (OzTeam)….
  3. In the dialog that opens:
    • Master Password: Set a strong key password for the recipient to open the file.
    • Include Passwords: Choose whether to embed passwords in the file:
      • Checked: The database password is encrypted with 256-bit AES and embedded; the recipient can connect with one click.
      • Unchecked: The password is not included; the recipient enters their own after opening.
  4. Create the file with Export Profile and send the .sqlozprofile file. Send the master password through a different channel.

Important: Sending the master password through the same channel as the file defeats the purpose of encryption. Always deliver the password through a separate, secure channel.

16.3 Importing a Profile

To receive a .sqlozprofile file:

  1. Double-click the file (or use File → Import Connection Profile).
  2. Enter the Master Password set by the sender.
  3. Click Import Profile.
  4. The cryptographic lock is released; the supported profile fields become ready in the connection list. SSH private keys and certificate material are not included in the capsule and must be configured separately on the recipient Mac.

16.4 Cryptographic Security Architecture

OzTeam uses the following cryptographic standards:

  • 256-bit AES-GCM: Galois/Counter Mode encrypts the data and protects file integrity against tampering.
  • PBKDF2 SHA-256: The master password is converted into a 256-bit encryption key using 600,000 iterations and a random salt. Imported envelopes are accepted only within the implementation’s bounded iteration range.
  • Wrong-password protection: If the wrong password is entered or the file is corrupted in transit, AES-GCM authentication refuses immediately and shows the “Master Password Invalid or File Corrupted” warning.