0 reply
0 recast
0 reaction
2 replies
1 recast
6 reactions
2 replies
0 recast
2 reactions
For managed services where we are doing more than simply proxying requests with no visibility to the encrypted request (e.g. QStorage's public bucket functionality requires visibility to Q Inc to function, however is optional and users can run their own proxy to do this instead), if we are compelled by court order to take action with respect to a public bucket, we have to comply. The network, however, will replicate data provided nodes do not all collectively blacklist the shard. If you want documents to remain secret, however, you would not want to use the public bucket feature anyway.
Regarding 20 year security, we would advise against using verifiable encryption alone – that relies on discrete logarithm assumptions and under that timeframe you would want potential QC resistance, so a hybrid scheme should be employed, e.g. first encrypt the data using a PQC algorithm, then save it with verifiable encryption to ensure integrity of the uploaded content. 0 reply
0 recast
5 reactions
0 reply
0 recast
0 reaction
