🚨 Seald is now on GitHub!!
Open-source isn't just a competitive advantage,
It’s a necessity!
And what’s the foundation of cybersecurity? Trust.
How do we build trust? Through transparency.
That’s why Seald has taken the leap.
Our code is now transparent, inviting experts worldwide to contribute to the most advanced end-to-end encryption SDK on the market.
Check it out on GitHub and let’s build a more secure world together! 💪🔒
github.com/seald/#OpenSource#CyberSecurity#Encryption#Seald#ZeroTrust#E2EE
I had a fantastic discussion with @SealdPrivacy about implementation details when implementing End-to-end Encryption #e2ee
The devil is in the details, as often in security and cryptography 😅
Thank you so much @ReboursT and Mehdi, you rock 🤘
#TipOfTheDay 💡: Allow users without Seald identity to encrypt data.
The anonymous encryption SDK enables your application to provide a way for users without Seald identity (unregistered users or users who are not logged-in) to encrypt data for users with a Seald identity.
#TipOfTheDay 💡: How Seald ensures that no-one can perform a man-in-the-middle attack?
Seald created the "Sig-Chain" technology, an immutable register that records all activities such as adding an identity, joining a group, renewing keys, and more.
This signature chain is unique to each user, safeguarding against the possibility of a man-in-the-middle attack.
The "Sig-Chain" serves as a mechanism that enables the verification of a user's entire set of public keys simultaneously.
#TipOfTheDay 💡: Accelerate the creation of sub-identities.
To accelerate the creation of sub-identities, you can pre-generate the private keys by calling the seald.preGenerateIdentityKeys() function in advance.
#TipOfTheDay 💡: Improve the speed of a Seald identity instantiation.
To improve the speed of instantiation, you can use « databaseRawKey » instead of « databaseKey ».
This avoids deriving the « databaseKey » with « scrypt » which is CPU intensive, especially on mobile devices.
That's often how it goes 🤦
Before a data breach -> Not the budget, not the time, not the priority!
After a data breach -> We don't want it to happen to us again, we do what's necessary. Get over here 💰
"We'll do a pentest at the end to secure the app."
No.
It's like building a building in Japan, and only looking at the end, if what we did is seismically secure 😅
Security in an app, it's thought out from the beginning.
No ?
"I don't have time for cybersecurity."
Stop ✋
You'll spend more time repairing the damage after a cyberattack than you've saved by skipping cybersecurity.