Baixar AeroFTP 4.0.0 per a Windows

[4.0.0] - 2026-05-27
Shaped Graph Transfer (DAG) and Multi-User Account Partition
v4.0.0 lands two architectural shifts in the same release.
The first is the promotion of the ready-frontier DAG transfer engine introduced in v3.8.4 to the single production path for every transfer surface. The three rollout flags that gated the engine during the v3.8.x cycle are gone, the hand-rolled JoinSet batch orchestrator has been deleted, and the shaped builders are now the single source of truth for every graph the executor schedules: single-file leaves, multi-file batches, sync sessions, intra-file segmented downloads, and cross-bucket copies. The release introduces a principled trait expansion on StorageProvider so the engine can dispatch the right shape per call from a provider's TransferCapabilities, ships the wiring + integration tests that prove the shapes work against live S3, B2, WebDAV, Azure, ImageKit, Google Drive, Dropbox, OneDrive, Box, MEGA, pCloud, kDrive, OpenDrive, Yandex Disk, Jottacloud, Drime, Uploadcare, Cloudinary, and Filen, and pairs the architectural shift with a power-user CLI surface that exposes 25+ runtime knobs over the same engine.
The second is the Multi-User Account Partition: the vault splits into per-user partitions while remaining fully backward-compatible with single-user installs. A boot-time Account Lock Screen presents the configured users, the vault is partition-aware end-to-end (server profiles, AeroSync settings, CLI --user flag), and an admin role with a self-or-admin gate plus an admin reset-passphrase backend rounds out the surface. Migration from a v3.8.x single-user keystore is automatic and idempotent, the admin role is opt-in with a last-admin guard, and the unlock prompts use honest crypto-stack labels (Argon2id key derivation, AES partition encryption). Sixteen commits cover the partition foundation, the boot picker, the CLI --user flag across profile and transfer commands, the cross-user dedup probe with HMAC keying, the migration of every existing keystore consumer (ConnectionScreen, SettingsPanel, IntroHub, ExportImport, KeystoreWizard, Cloud, SavedServers, App.tsx), the admin role, and the UX polish (logout, perceptible unlock spinner, refined L2 picker).
What's new
Capability-aware shape per transfer
The shaped graph builder picks the transfer-core shape per call from the provider's capability snapshot:
- Native multipart upload fan-out on S3, Backblaze B2, Google Drive, Dropbox, OneDrive, and Box: an upload above one preferred chunk now produces N UploadPart graph nodes (one per chunk). The runner orchestrates the lifecycle end-to-end. Per-provider live validation: Drive 500 MiB in 34.6 s (63 parts x 8 MiB), Dropbox 500 MiB in 54.2 s (63 parts x 8 MiB concurrent), OneDrive 500 MiB in 63.8 s (50 parts x 10 MiB sequential), Box 100 MiB in 24.6 s (13 parts x 8 MiB, SHA-1 per chunk + whole-file SHA-1 commit).
- Server-side copy on every backend that advertises the capability: S3 x-amz-copy-source, B2 b2_copy_file, WebDAV RFC 4918 COPY, ImageKit copyFile, plus 14 other native providers. The shaped-copy graph collapses to a single ServerSideCopy node that reserves only an api_slot: no file slot, no disk I/O, no local host bytes. The server moves the data. S3 sources above the 5 GiB CopyObject limit fan out into parallel UploadPartCopy requests (T-DEBT-08).
- Intra-file segmented downloads through the shared shaped_ranges builder: when a provider proves it honours HTTP Range, the segmented download fans out into N DownloadRange nodes with no inter-segment dependencies, governed by the shared chunk / HTTP / disk-write budget.
For users on backends that advertise none of these capabilities the engine degrades honestly to the same single-transfer-core path that shipped pre-v4.0.0, byte-identical with the legacy provider.upload / provider.download.
Provider trait expansion
Five new methods extend StorageProvider:
- begin_multipart_upload(remote_path, total_size, content_type, local_source_path)
- upload_part(handle, part_number, data)
- complete_multipart_upload(handle, parts)
- abort_multipart_upload(handle)
- server_side_copy(from, to) (alongside the existing supports_server_side_copy() capability gate).
Default implementations return NotSupported, so a provider that never advertises a capability never reaches the new methods. Nineteen native backends already implement them: S3 (multipart + server-side copy), B2 (multipart + 5 GB-capped server-side copy), Azure Blob (Put Block / Put Block List), WebDAV (Nextcloud chunked v2 + RFC 4918 COPY), ImageKit (copyFile / copyFolder), Google Drive (resumable session), Dropbox (concurrent upload_session + explicit close), OneDrive (Microsoft Graph createUploadSession), Box (chunked v2 with per-chunk SHA-1 + whole-file SHA-1 commit), MEGA (gfs* canonical chunk ramp), pCloud (chunked upload session), kDrive (upload-session API), OpenDrive (chunked upload session), Yandex Disk (upload-target API), Jottacloud (allocate API), Drime (S3 multipart), Uploadcare (multipart API), Cloudinary (chunked upload), Filen v3 (chunked AES-GCM encrypted upload). ImageKit / Internxt / MEGA / 4shared / FileLu document the trait as NotSupported-by-design for cases where the protocol does not offer a real multipart surface.
Power-user CLI knob expansion (PR #261)
Twenty-five new flags expose the same DAG engine to scripted workflows and CI pipelines without touching code:
- Generic (Sprint K1 Pacchetto A): --sftp-concurrency, --checkers, --tpslimit / --tpslimit-burst, --no-traverse, --order-by.
- S3 surface (KE-B1): --s3-upload-concurrency, --s3-no-check-bucket, --s3-disable-checksum, --s3-acl, --s3-storage-class.
- Retry-After parsing extensions (KE-E): S3, Azure and Filen now parse and honour server-issued Retry-After on 429 / 503 throttle responses (joining Google Drive, Dropbox, OneDrive and Box from T-DEBT-05).
- Drive non-AIMD knobs + AIMD config (KE-B2): pacer / abuse acknowledgement / copy-related runtime settings for Google Drive.
- OneDrive (KE-B3): --onedrive-no-versions, --onedrive-list-chunk, --onedrive-link-scope.
- Azure (KE-B4): --azure-upload-concurrency, --azure-disable-checksum, --azure-access-tier, --azure-archive-tier-delete.
- AIMD adaptive concurrency (KE-D): --aimd-disable kill switch, --aimd-min / --aimd-max / --aimd-step-window overrides + per-class TOML configuration, hint table propagation through the executor.
- FUSE mount surface (Sprint K3 / T-DEBT-13): --cache-mode={off|minimal|writes|full} policy preset, polling / timeout knobs, --write-back-cache via Filesystem::init capability negotiation, --fuse-threads multi-threaded session loop. fuser bumped 0.16 to 0.17.
AeroCloud catch-up (PR #262)
- Koofr background sync dispatch fix. Koofr was already a stable provider in the AeroCloud wizard but cloud_provider_factory.rs did not route it to the background sync path, so a Koofr profile selected from the wizard would surface "provider not implemented" at first scheduled sync. One-line factory dispatch fix.
- Four providers exposed in the AeroCloud wizard: ImageKit, Uploadcare, Cloudinary, Backblaze B2. They were already wired through the factory since v3.x but never appeared as selectable presets in the wizard UI, leaving them reachable only by hand-rolled config.
Convergence cleanup
- The three AEROFTP_TRANSFER_ENGINE_DAG_* environment-variable flags are removed.
- The matching dag_single_file_enabled() / dag_batch_enabled() / dag_sync_enabled() functions are removed.
- should_route_sync_to_dag(dry_run) collapses to !dry_run.
- The four engine-routing shims in provider_commands, the CLI, the batch orchestrator and the sync path drop their flag check.
- The hand-rolled JoinSet sliding-window orchestrator in transfer_orchestrator::execute_batch (130+ lines including spawn_transfer_task) is removed: execute_batch_dag is the entire body.
Multi-User Account Partition (PR #279)
A second architectural pillar that splits the vault into per-user partitions while keeping single-user installs fully backward-compatible:
- Encrypted partition foundation with per-user data isolation, Argon2id key derivation, and AES partition encryption.
- Boot-time Account Lock Screen that presents the configured users and accepts a per-user passphrase, with honest crypto-stack labels in the unlock prompts.
- Partition-aware vault wiring end-to-end: SavedServers, App.tsx, ConnectionScreen, SettingsPanel, IntroHub, ExportImport, KeystoreWizard, Cloud, favicon.
- Per-user AeroSync settings CRUD on top of the partition layer.
- Admin role with a self-or-admin gate and an admin reset-passphrase backend, last-admin guard so an installation cannot lock itself out.
- CLI --user flag across profile and transfer commands; optional everywhere, defaults to the active profile.
- Cross-user dedup probe with HMAC keying.
- UX polish: logout flow, perceptible unlock spinner, refined L2 picker, account avatars with emoji/color customization.
- Migration from a v3.8.x single-user keystore is automatic, idempotent, and preserves all existing data; the admin role is opt-in.
Fixed
DAG engine
- Per-provider chunk size honoured verbatim: the runner consumes the provider's advertised multipart_part_size as the per-part length verbatim (last part takes the remainder); the legacy div_ceil distribution stays as the fallback. Fixes Google Drive 256-KiB alignment and OneDrive 320-KiB alignment that previously hit HTTP 503 mid-stream.
- Serial chain for max_chunk_slots = 1 providers: the builder chains UploadPart nodes serially whenever the cap is one, preserving Drive's monotonic Content-Range contract; providers with parallel chunk fan-out (S3, B2, Dropbox concurrent, Box chunked v2) keep the unconstrained shape.
- Dropbox concurrent session explicit close: complete_multipart_upload now emits the no-op upload_session/append_v2 with close: true before the finish call, so Dropbox no longer returns HTTP 409 concurrent_session_not_closed.