Is there a way to do this without the use of rclone? is is a Standards based encryption or proprietary?
The use case is sending some files to a DMZ server, and having them encrypted at rest, and using some C# web code to decrypt them in memory, we don't really want to call the rclone client as that would then require saving the un-encrypted one to disk
"rclone uses nacl secretbox which in turn uses XSalsa20 and Poly1305 to encrypt and authenticate your configuration with secret-key cryptography. The password is SHA-256 hashed, which produces the key for secretbox."
on the server, what type of file server protocol will be used for copying from the client?
you can encrypt any server at rest in many different ways. on windows, you can use bitlocker, you can use a hard drive that has hardware encryption, many whole disc encryption options
use a vpn to copy files from client to dmz server.
so you plan to decrypt the files in ram via c#? so for whatever amount of ram you would dedicate to c# code, create a temp ramdisk and decrypt rclone files to that ramdisk. no need to decrypt rclone to hard disk
The documentation is mostly about that yes, but the section I quoted there does give a quick rundown of how rclone crypt is composed. I do not think the whole crypt construct used for rclone is "a standard", but as you see it uses mostly standard components.
If you need a higher level of detail then that because you are tying to make your own program capable of reading rclone crypted files then you should probably just go look at the crypt code on github. Rclone's code is open after all
And for really spesific implementation questions - you probably have to ask @ncw
I don't know if perhaps C# would be capable of calling a library that has the native go code? ... if so then you might be able to rip out the relevant section that decrypts and stick it in there for your C# program to use without having to port the code. That said - go and C# are not that different, so that should be quite doable too if you are reasonably proficient.
I would check to make sure NCW is ok with it before re-purposing large sections of code though. I have no idea about the legal stuff in licenses ect. but it seems like a common courtesy thing to do