axross 0.4.1__tar.gz

axross-0.4.1/CONTRIBUTING.md

@@ -0,0 +1,98 @@
+# Contributing to Axross
+
+Thanks for considering a contribution. Axross is an Apache-2.0 licensed
+multi-protocol file manager; the ground rules below keep the project
+sustainable and predictable for everyone.
+
+## Licensing of contributions
+
+By submitting a pull request, you agree that your contribution is provided
+under the terms of the Apache License 2.0 (see [LICENSE](LICENSE)) and that
+you have the right to submit it. Per Apache-2.0 §5, every contribution is
+automatically licensed under the same terms as the project — no separate CLA
+is required for normal contributions.
+
+If your contribution includes code you did not author (vendored snippets,
+translated code, etc.), flag it in the PR description with the original
+source and its license so we can verify compatibility with Apache-2.0 before
+merge.
+
+## What's in scope
+
+- Fixes for any backend listed in the protocol table.
+- New backends that follow the `FileBackend` protocol in `core/backend.py`.
+- UI / UX improvements (keyboard shortcuts, dialog ergonomics, accessibility).
+- MCP tool additions that compose cleanly with the existing surface.
+- Hardening tests (`tests/test_hardening_regressions.py`) that cover a real
+  attack class; generic "it doesn't crash" tests are lower priority.
+- Translation updates for README and user-facing messages.
+
+## What's out of scope
+
+- Features that require bundling additional heavy SDKs by default. Put them
+  behind a new optional extra in `pyproject.toml` and keep the base install
+  slim.
+- Changes that degrade the safe-extraction guards in `core/archive.py`,
+  the MCP root-traversal guard, or the profile-field keyring routing
+  without explicit justification.
+- Telemetry / phone-home / auto-update code of any kind.
+
+## Development setup
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e ".[all]"
+pip install -r dev-requirements.txt
+```
+
+For the protocol lab:
+
+```bash
+cd tests/docker && docker compose up -d --build
+```
+
+See [INSTALL.md](INSTALL.md) for the canonical install flow.
+
+## Running tests
+
+Host suite (no Docker required):
+
+```bash
+QT_QPA_PLATFORM=offscreen .venv/bin/pytest -q \
+    tests/test_hardening_regressions.py tests/test_regressions.py \
+    tests/test_new_features.py tests/test_backend_regressions.py \
+    tests/test_pane_layout_regressions.py tests/test_e2e.py
+```
+
+Protocol lab (needs `docker compose up -d --build` first):
+
+```bash
+.venv/bin/pytest tests/test_protocols.py tests/test_network.py
+```
+
+PRs must pass the host suite. Lab tests are best-effort because not every
+reviewer has the lab stood up — your PR description should state which
+lab sections you ran locally.
+
+## Code style
+
+- Python: `ruff` is the only style gate. `ruff check .` must pass.
+- Line length 100 (configured in `pyproject.toml`).
+- Keep dependencies minimal. New runtime deps need a justification; new
+  optional extras are preferred over base-install additions.
+- Tests: mirror the module layout, one test file per module where
+  reasonable. Use `QT_QPA_PLATFORM=offscreen` for any UI test.
+
+## Commits and PRs
+
+- One commit per logical feature. Rebase before opening the PR.
+- Subject line: imperative, under 72 chars. Body wraps at 72.
+- Reference the issue number in the body if applicable (`closes #123`).
+- PR description states: what changed, why, how it was tested, and any
+  follow-up items you deliberately deferred.
+
+## Security issues
+
+Do not open a public issue for anything with exploit potential — email
+[SECURITY.md](SECURITY.md) has the disclosure contact and timeline.

axross-0.4.1/INSTALL.md

@@ -0,0 +1,227 @@
+# Installation
+
+This is the single canonical install reference. The top-level READMEs
+(EN/DE/ES) link here instead of duplicating these steps in each language.
+
+## Prerequisites
+
+- **Python** ≥ 3.10
+- **Linux**: `apt install python3-venv` or the equivalent on your distro so
+  `python3 -m venv` is available.
+- **Linux GUI / containers**: PyQt6 ships Qt itself, but minimal images still
+  need the system loader libraries used by Qt plugins. On Debian/Ubuntu slim
+  images install:
+
+  ```bash
+  apt-get update
+  apt-get install -y --no-install-recommends \
+      libglib2.0-0 libgl1 libegl1 libfontconfig1 libxkbcommon0 libdbus-1-3
+  ```
+
+  Headless modes such as `axross --help`, `axross --script`, and
+  `axross --mcp-server` do not need those GUI libraries.
+- Optional system tools (only needed for protocols that call out via
+  `subprocess`):
+  - `rsync` binary — Rsync backend.
+  - `mount.nfs`, `umount` (root/sudo) — NFS backend.
+  - `iscsiadm`, `mount`, `blkid` (root/sudo + `open-iscsi`) — iSCSI backend.
+  - `pkexec` + polkit rules — "Open as root…" action
+    (`core.elevated_io`).
+
+## PyPI install
+
+Once a release is published:
+
+```bash
+python3 -m venv .venv
+source .venv/bin/activate
+pip install "axross[all]"
+axross        # launches the GUI
+```
+
+Use `pip install axross` for the smallest base install and add
+protocol extras as needed.
+
+## Source install
+
+```bash
+git clone <repo-url>
+cd axross
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -e .
+axross        # launches the GUI
+```
+
+Base install pulls only what the always-available protocols need:
+
+| Package         | Version  | Purpose                                        |
+|-----------------|----------|------------------------------------------------|
+| PyQt6           | ≥ 6.6    | GUI framework                                  |
+| paramiko        | ≥ 3.4    | SSH / SFTP / SCP                               |
+| PySocks         | ≥ 1.7    | SOCKS4 / SOCKS5 proxy                          |
+| keyring         | ≥ 25.0   | OS secret store for passwords                  |
+
+FTP, Telnet, IMAP use only the Python standard library — no extra deps.
+
+## Optional protocol extras
+
+Install just the ones you need. Unavailable backends appear greyed out
+in the Connection Manager with an inline `pip install` hint.
+
+```bash
+pip install "axross[smb]"       # SMB / CIFS + DFS-N (smbprotocol)
+pip install "axross[webdav]"    # WebDAV (requests + defusedxml — pure-Python)
+pip install "axross[s3]"        # S3-compatible (boto3)
+pip install "axross[azure]"     # Azure Blob + Azure Files (azure-storage-*)
+pip install "axross[onedrive]"  # OneDrive + SharePoint (msal, requests)
+pip install "axross[gdrive]"    # Google Drive (google-api-python-client)
+pip install "axross[dropbox]"   # Dropbox (dropbox SDK)
+pip install "axross[winrm]"     # WinRM / PowerShell-Remoting (pywinrm)
+pip install "axross[wmi]"       # WMI / DCOM read-only (impacket)
+pip install "axross[exchange]"  # Exchange Web Services (exchangelib)
+pip install "axross[fuse]"      # FUSE mount any backend (fusepy, Linux/macOS)
+```
+
+From a source checkout, use the editable equivalent, for example
+`pip install -e ".[smb]"`.
+
+### Install light extras at once
+
+```bash
+pip install "axross[all]"
+```
+
+`[all]` covers SMB, WebDAV, S3, Azure, OneDrive/SharePoint, GDrive,
+Dropbox. It deliberately **excludes** `winrm`, `wmi`, `exchange`, and
+`fuse` because each of those pulls a heavy dep (impacket brings in
+~50 MB of crypto code; exchangelib pulls lxml; fusepy needs matching
+kernel FUSE support). Add them explicitly when you need them.
+
+### One-shot sanity check
+
+```bash
+.venv/bin/python -c 'import main; print("axross ok")'
+```
+
+## Cloud services (OAuth)
+
+OneDrive, SharePoint, Google Drive, and Dropbox require OAuth app
+registration before first use. Client IDs are not shipped with the
+repo — every user needs their own.
+
+See [OAUTH_SETUP.md](OAUTH_SETUP.md) for each provider's step-by-step
+recipe.
+
+## Building a wheel
+
+```bash
+pip install build twine
+python -m build
+python -m twine check dist/*
+# dist/axross-<version>.tar.gz
+# dist/axross-<version>-py3-none-any.whl
+```
+
+Install on another machine:
+
+```bash
+pip install dist/axross-<version>-py3-none-any.whl
+# Or with extras:
+pip install "dist/axross-<version>-py3-none-any.whl[all]"
+```
+
+Smoke-test the built artifact without the source tree:
+
+```bash
+tmpdir="$(mktemp -d)"
+python3 -m venv "$tmpdir/venv"
+"$tmpdir/venv/bin/pip" install --no-deps dist/axross-<version>-py3-none-any.whl
+"$tmpdir/venv/bin/python" -c 'import axross; print(axross.__version__)'
+"$tmpdir/venv/bin/python" -m axross --help
+"$tmpdir/venv/bin/axross" --help
+```
+
+## Publishing to PyPI
+
+Build from a clean, tagged checkout and always validate on TestPyPI first:
+
+```bash
+rm -rf dist
+python -m build
+python -m twine check dist/*
+python -m twine upload --repository testpypi dist/*
+python -m twine upload dist/*
+```
+
+Authentication should use PyPI/TestPyPI API tokens, either from
+`~/.pypirc` or environment variables consumed by `twine`.
+
+## Versioning
+
+The package version has one source of truth: `axross/_version.py`.
+`pyproject.toml` reads it via `tool.setuptools.dynamic`, so do not
+duplicate the version in project metadata.
+
+Use PEP 440 versions:
+
+```text
+0.4.1        # patch release
+0.5.0        # feature release
+1.0.0        # stable major release
+0.5.0rc1     # release candidate
+0.4.1.post1  # post-release metadata/docs fix
+```
+
+Release bump checklist:
+
+```bash
+python - <<'PY'
+from axross._version import __version__
+print(__version__)
+PY
+rm -rf dist
+python -m build
+python -m twine check dist/*
+```
+
+Tag releases as `v<version>`, for example `v0.4.1`.
+
+## Development setup
+
+```bash
+source .venv/bin/activate
+pip install -e ".[all]"
+pip install -r dev-requirements.txt
+```
+
+`dev-requirements.txt` covers pytest, coverage, ruff, build, twine, plus
+`cryptography` and `jsonschema` that some MCP tests exercise directly.
+
+Run the host test suite (no Docker required):
+
+```bash
+QT_QPA_PLATFORM=offscreen .venv/bin/pytest -q \
+    tests/test_hardening_regressions.py tests/test_regressions.py \
+    tests/test_new_features.py tests/test_backend_regressions.py \
+    tests/test_pane_layout_regressions.py tests/test_e2e.py
+```
+
+Expected: ~925 pass, 5 skip (three FUSE tests gated on `fusepy`,
+one GDrive-refresh test gated on `google-auth`, one end-to-end test
+that needs the docker lab).
+
+For the Docker protocol lab see the **Development / Testing** section
+in [README.md](README.md) — the protocol coverage matrix there spells
+out exactly which backends are cleanly tested and which aren't.
+
+## Uninstall
+
+```bash
+pip uninstall axross
+rm -rf .venv
+rm -rf ~/.config/axross ~/.local/state/axross  # settings + logs
+# Keyring entries — the "Forget Password" option in the Connection
+# Manager removes individual entries; wholesale cleanup depends on
+# your OS keyring front-end (Seahorse, kwallet-query, security).
+```

axross-0.4.1/LICENSE

@@ -0,0 +1,200 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may accept support,
+      warranty, indemnity, or other liability obligations and/or rights
+      consistent with this License. However, in accepting such obligations,
+      You may act only on Your own behalf and on Your sole responsibility,
+      not on behalf of any other Contributor, and only if You agree to
+      indemnify, defend, and hold each Contributor harmless for any
+      liability incurred by, or claims asserted against, such Contributor
+      by reason of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Marco Lux
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

axross-0.4.1/MANIFEST.in

@@ -0,0 +1,7 @@
+include LICENSE NOTICE README.md README_PYPI.md README_de.md README_es.md INSTALL.md
+include dev-requirements.txt
+include OAUTH_SETUP.md SECURITY.md CONTRIBUTING.md THIRD_PARTY_LICENSES.md
+recursive-include docs *.md
+recursive-include resources/logo *.png *.svg
+recursive-include resources/scripts *.md *.py
+recursive-include resources/wordlists *.txt

axross-0.4.1/NOTICE

@@ -0,0 +1,30 @@
+Axross
+Copyright 2026 Marco Lux
+
+This product includes software developed by Marco Lux.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+================================================================================
+THIRD-PARTY COMPONENTS
+================================================================================
+
+Axross is source-distributed under Apache-2.0 and dynamically imports the
+runtime dependencies listed in pyproject.toml and THIRD_PARTY_LICENSES.md.
+These dependencies are NOT bundled in the source tree; users install them via
+`pip install`.
+
+IMPORTANT: Pre-built PyInstaller bundles (dist/axross-slim, dist/axross-full,
+the AppImage) produced from this source tree statically include PyQt6, which
+is distributed by Riverbank Computing under the GNU General Public License,
+Version 3 (GPL-3.0) or a separate commercial license. When distributing those
+bundles, the combined binary is therefore redistributed under GPL-3.0 terms.
+The Axross source itself remains available under Apache-2.0, and users who
+wish to produce non-GPL binaries may rebuild against PySide6 (LGPL-3.0)
+instead of PyQt6.
+
+Per-dependency license attribution is maintained in THIRD_PARTY_LICENSES.md.

axross-0.4.1/OAUTH_SETUP.md

@@ -0,0 +1,105 @@
+# OAuth App Registration Guide
+
+Axross supports cloud storage services that require OAuth2 authentication.
+You need to register your own app with each provider to get Client IDs/Secrets.
+
+## Google Drive
+
+1. Go to [Google Cloud Console](https://console.cloud.google.com/)
+2. Create a new project (or select existing)
+3. Enable the **Google Drive API**:
+   - Navigate to *APIs & Services > Library*
+   - Search for "Google Drive API" and click **Enable**
+4. Create OAuth credentials:
+   - Go to *APIs & Services > Credentials*
+   - Click **Create Credentials > OAuth client ID**
+   - Application type: **Desktop app**
+   - Name: `Axross` (or any name)
+   - Click **Create**
+5. Copy the **Client ID** and **Client Secret**
+6. Configure the OAuth consent screen:
+   - Go to *APIs & Services > OAuth consent screen*
+   - User type: **External** (or Internal for Workspace)
+   - Fill in app name, support email
+   - Add scope: `https://www.googleapis.com/auth/drive`
+   - Add your email as a test user (while in "Testing" status)
+
+Enter the Client ID and Client Secret in the Axross connection dialog.
+
+## Microsoft OneDrive / SharePoint
+
+1. Go to [Azure Portal - App registrations](https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade)
+2. Click **New registration**
+   - Name: `Axross`
+   - Supported account types: **Accounts in any organizational directory and personal Microsoft accounts**
+   - Redirect URI: **Public client/native (mobile & desktop)** → `http://localhost`
+3. After creation, note the **Application (client) ID**
+4. Set the **Tenant ID**:
+   - For personal OneDrive: use `common`
+   - For organization-only: use your Azure AD tenant ID
+5. Configure API permissions:
+   - Go to *API permissions > Add a permission > Microsoft Graph*
+   - Delegated permissions:
+     - `Files.ReadWrite.All`
+     - `User.Read`
+     - For SharePoint also add: `Sites.ReadWrite.All`
+   - Click **Grant admin consent** (if you have admin rights)
+6. Under *Authentication*:
+   - Ensure **Allow public client flows** is set to **Yes**
+
+Enter the Client ID and Tenant ID in the Axross connection dialog.
+For SharePoint, also enter the Site URL (e.g. `https://company.sharepoint.com/sites/MySite`).
+
+## Dropbox
+
+1. Go to [Dropbox App Console](https://www.dropbox.com/developers/apps)
+2. Click **Create app**
+   - Choose **Scoped access**
+   - Choose **Full Dropbox** access type
+   - Name: `Axross` (must be unique)
+3. In the app settings:
+   - Note the **App key** and **App secret**
+4. Under *Permissions* tab, enable:
+   - `files.metadata.read`
+   - `files.metadata.write`
+   - `files.content.read`
+   - `files.content.write`
+   - `account_info.read`
+5. Click **Submit** to save permissions
+
+Enter the App Key and App Secret in the Axross connection dialog.
+
+## Token Storage
+
+OAuth tokens are cached locally at:
+- Google Drive: `~/.config/axross/gdrive_token.json`
+- OneDrive/SharePoint: `~/.config/axross/onedrive_token.json`
+- Dropbox: `~/.config/axross/dropbox_token.json`
+
+Tokens are automatically refreshed when they expire. Delete the token file to force re-authentication.
+
+## Security Notes
+
+- **Client IDs** (and Dropbox App Keys) live in your profile file at
+  `~/.config/axross/profiles.json`. These are not secret on their own —
+  Google / Microsoft / Dropbox treat them as public identifiers for the
+  registered app. The profiles file is still written with `0o600`
+  permissions via `tempfile.mkstemp` followed by `os.replace`, so only
+  your user account can read it.
+- **Client Secrets** (Google's `client_secret`, Dropbox's `app_secret`)
+  plus Azure SAS tokens and Azure connection strings are **never** stored
+  in the profiles file. They go to the OS keyring (GNOME Keyring / KDE
+  Wallet / macOS Keychain / Windows Credential Manager) via the
+  `SENSITIVE_PROFILE_FIELDS` mechanism in `core/profiles.py`. If no
+  desktop keyring is available, axross logs a warning and does NOT
+  persist them — you re-enter on next launch rather than risk a plaintext
+  leak.
+- **OAuth refresh tokens** are written atomically to
+  `~/.config/axross/*_token.json` with `0o600` via
+  `core.secure_storage.write_secret_file`. The file is 0o600 from birth
+  (`fchmod` on the temp fd before the rename) — no TOCTOU window where
+  a world-readable version exists.
+- **What to protect from yourself and others:** the token files under
+  `~/.config/axross/` and your OS keyring entries. Losing those → drop
+  the file and re-auth. Leaking them → revoke the OAuth app's access in
+  the provider's console immediately and regenerate.