[Rust] descriptor-encrypt: Encrypt any descriptor such that only authorized spenders can decrypt

The discussion focuses on the development of a library that intentionally omits the integration of a storage solution for encrypted data. This decision underscores the library's specialized approach, concentrating its functionality on encryption without delving into data storage complexities. This separation of concerns highlights an architectural choice aimed at maintaining the library's focus and efficiency in its core domain.

The inquiry about the future vision for the storage layer of encrypted blobs raises important considerations, particularly regarding long-term data management and inheritance scenarios. It suggests an interest in understanding how encrypted data could be effectively stored, accessed, and transferred across generations or different users, which is crucial for planning the library's applicability in real-world use cases. The question reflects a forward-looking perspective, seeking to address the broader lifecycle management of encrypted information beyond its creation and immediate use.

This aspect of the conversation opens up avenues for exploring potential integrations with existing storage solutions or the development of new mechanisms tailored to securely manage encrypted data over time. It also touches upon the need for strategic planning around data inheritance, ensuring that encrypted content remains accessible and transferable according to predefined protocols or user intentions. This indicates an awareness of the practical challenges and complexities involved in encrypted data management, emphasizing the importance of designing a versatile and user-centric library.