I made a rebuild and modify the Cspace code.
Get rid of ncrypt library, now it is using pyOpenSSL and python-crypto instead.
Ncrypt library is no longer supported and unit tests was failed on Ubuntu machines.
So I decided to replace it with another OpenSSL wrapper. I am using pyOpenSSL in my project so this was my choice.
I can not understand yet how to make Diffie-Hellman key exchange in pyOpenSSL so this stuff was disabled, however old CSpace code has it.
Also set_session_cache_mode and set_mode for SSL.Context is not yet supported in pyOpenSSL so I cant use it. All other things seems to be working correctly.
The new public keys location is placed on our Identity server:
I wish to use this library to improve peer to peer communications in my project called DataHaven.NET. Going to build another transport protocol using CSpace to transfer encrypted files between users, CSpace seems to be very smart library to do that.
Not sure yet how to organize public keys for CSpace users. Because DataHaven.NET users will need to have own keys too and they will be mixed with CSpace users.
I think would be smarter to make another public key store for CSpace users only.