Skip to main content
Minerva’s SFTP endpoint gives you a standard file-transfer interface to the same per-organization data area the SDK uses. Files you upload via SFTP appear in mc.storage.list(...), and anything Minerva delivers to Outgoing/ is available via the SDK too — one data area, two interfaces.

Connect

Quick connect (macOS / Linux):
Once connected:

Directory layout

Client compatibility

All modern SFTP clients connect successfully — this table lists the versions that negotiate post-quantum key exchange (mlkem768x25519-sha256). Older clients still connect over strong classical KEX (Curve25519, ECDH); the only difference is “store-now-decrypt-later” resistance.

Supported algorithms

Published so you can cross-check your client’s supported algorithms against ours. Server preference order: Key exchange
  • mlkem768x25519-sha256 (PQ hybrid — typically negotiated with modern clients)
  • mlkem768nistp256-sha256
  • mlkem1024nistp384-sha384
  • ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521
  • curve25519-sha256, curve25519-sha256@libssh.org
  • diffie-hellman-group18-sha512, diffie-hellman-group16-sha512
  • diffie-hellman-group-exchange-sha256
Ciphers
  • aes128-gcm@openssh.com (typically negotiated)
  • aes256-gcm@openssh.com
  • aes128-ctr, aes192-ctr, aes256-ctr
MACs (used with CTR ciphers; GCM has built-in integrity)
  • hmac-sha2-256-etm@openssh.com (typically negotiated)
  • hmac-sha2-512-etm@openssh.com
Host key: RSA-2048 Not accepted: SHA-1 MACs, non-ETM MACs, CBC ciphers, 3DES, Blowfish, RC4, SSH v1. To see what your session negotiated: