Klaus Vink Slott

As stated above I agree with Uwe: I see no reason why/how the storage method should improve security. If you want improved security at the server level, you would need to store store the files encrypted in SeedDMS. You could actually store the files visible to the public outside SeedDMD (why I mentioned IPFS). Anyway, at some point the files must be visible to the end user. Thus the user must be given the key to decrypt the file or SeedDMS would have to facilitate reencryption with the receivers...

Now I am not the developer, just a previus user .. lurking around on the mailing list awaiting version 6 :-) But I dont see how the storage method affects security. At one point or another you want to give some - or everybody - access to the content. I.e. feed the document to the authorized user in some format which he can interpret. If the storage method should be discussed, I would rather consider placing all documents on IPFS in some encrypted format, and then let SeedDMS release the key for unencryption...

+1 Same problem. Installing from scratch on VMware ESXi. Only "non default" action during install was escaping the DHCP phase - to set up networking manualy. Networking is still up and working though, - as I can still ping the server at this moment. It has been stuck at appx 43% for 12 hours now.

EDIT: After messing around, an apt-get upgrade and a reboot, problem disapeared....

I have the same problem as described above. Connections times out and the remote...

Thanks. Ill give 5.0.x a try then.

Hi Just to be sure: Which is the current stable version. Website says "Latest Version...

You should not feel embarrassed, I could imagine many scenarios in where you want...