jgiraldo29

4 ms·

1. 1.▲
   by jgiraldo29 1y ago

   Hello! Thank you for your question. To start with, yes. Originally the project was going to be decentralized to exactly stop that from happening, but as time went on I realized how it quickly became overcomplicated. So it was either impleme
2. 2.▲
   Show HN: GiralNet – A Privacy Network for Your Team (Not the World)(github.com)

   6 points by jgiraldo29 1y ago|2 comments
3. 3.▲
   Teaching a kernel to optimize itself through machine learning(vekos.org)

   2 points by jgiraldo29 2y ago|0 comments
4. 4.▲
   Show HN: Europa – A self-hosted, encrypted file sharing service(github.com)

   2 points by jgiraldo29 2y ago|0 comments
5. 5.▲
   by jgiraldo29 2y ago

   Thank you so much. I really like the idea of the hypervisor-based verification approach as it would provide stronger isolation for the verification chain than the current in-kernel approach. It also aligns really well with some of VEKOS&#x2
6. 6.▲
   by jgiraldo29 2y ago

   Thanks for your question. Currently, VEKOS runs in single-core mode - SMP support is planned but not yet implemented. The challenge with SMP in VEKOS isn't just synchronization, but maintaining verifiable operation chains across cores.
7. 7.▲
   by jgiraldo29 2y ago

   Thank your question. The OS does have currently some limitations in the signature area, as this is one of those things that is still a work in progress due to trying to focus in many common threats first before expanding on the verification
8. 8.▲
   by jgiraldo29 2y ago

   Thank you so much. Now let me break this questions down: Key Security Benefits: 1. Cryptographic Verification: - Prevents silent corruption of system state - Makes tampering with system logs cryptographically difficult - Provides verifiable
9. 9.▲
   by jgiraldo29 2y ago

   Good observation about the threat model. The verification system actually serves multiple purposes: 1. Hardware integrity: Yes, it helps detect hardware faults, but that's not the primary focus. 2. Attack detection and auditing: The sy
10. 10.▲
    by jgiraldo29 2y ago

    I've put a lot of thought into managing the storage growth, the chain grows proportionally to system activity, but I've implemented several optimizations to keep it manageable: 1. Efficient proof encoding: Each proof is typically
11. 11.▲
    by jgiraldo29 2y ago

    Thank you for your questions. The primary target users would be systems where integrity verification and auditing are critical requirements, such as: - Financial/banking systems that need cryptographic proof of all operations - Medical
12. 12.▲
    Show HN: Vekos – a Rust OS with Built-In Cryptographic Verification(github.com)

    82 points by jgiraldo29 2y ago|15 comments