RFE: Support for ssh and scp/sftp

[sunetfreitag]

Specific inclusion of ssh, including scp and/or sftp, into the ocm specification could be beneficial for many uses cases. This could include ocm account linking, where a receiving party then is identified by one or multiple public keys.

[ocm-mail-bot]

Maybe we should add or reference a "protocol registry" to avoid collisions between protocol identifiers and links to specs of protocol integrations outside of OCM? I don't think adding specifying all protocol integrations within ocm would scale. E.g. also with my OGC API based map sharing. Am 24. September 2025 20:11:27 MESZ schrieb sunetfreitag ***@***.***>:

…

sunetfreitag created an issue (cs3org/OCM-API#277) Specific inclusion of ssh, including scp and/or sftp, into the ocm specification could be beneficial for many uses cases. This could include ocm account linking, where a receiving party then is identified by one or multiple public keys. -- Reply to this email directly or view it on GitHub: #277 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[glpatcern]

Maybe we should add or reference a "protocol registry" to avoid collisions between protocol identifiers and links to specs of protocol integrations outside of OCM? I don't think adding specifying all protocol integrations within ocm would scale.

"All" protocols definitely not, but the subset of protocols that make sense to specify so far is just a handful. Also, OCM allows the use of custom protocols without further specifications, which are then left to the implementations.

IMHO ssh/scp and its asymmetric key - at variance with the current shared secret model of webdav - makes sense to have in the spec as a "first class citizen", so to ensure implementations follow a given schema and are compatible.

@sunetfreitag would you draft a PR for this?