Post-quantum cryptography is a subset of cryptography designed to be secure against quantum computers. Some currently used cryptography is quantum-safe, meaning it is secure even if adversaries can use quantum computers. However, new post-quantum algorithms (especially Latticed-based cryptography) are designed to be quantum-safe or quantum-proof.
Most symmetric encryption schemes are considered quantum-safe if they use sufficiently large key sizes. The same is said for most hash functions. However, it is essential to note that no cryptography can ever be guaranteed to be secure forever. Cryptography is constantly being tested and analyzed to make reliable assumptions about its security.
Code Siren implements the post-quantum algorithms submitted and accepted by the National Institute of Standards and Technology (NIST) standardization process. We believe they are promising long-term candidates for post-quantum cryptography standards.
From the Windows desktop application, click the settings (gear) icon in the toolbar. When the 3rd pane opens, click your Graphatar to reveal Manage Identites. This will list all your identites. Right-click the Graphatar you want to export, and choose Export. Please use a secure password. This export file contains the private keys for your identity.
In Android, tap your Graphatar's image from the main navigation page. This will open the Edit User page. From there, tap the 3-dot menu on the top right corner. There is an Export option in the bottom-up popup menu. Please use a secure password. This export file contains the private keys for your identity.
This assumes you have exported your Graphatar previously, and it has been saved in a password protected file such as User.nom
From the Windows desktop application, click the settings (gear) icon in the toolbar. When the 3rd pane opens, click Import Identity.
From the Android application, click the settings (gear) icon in the toolbar. Then click Identities. From there, tap the 3-dot menu on the top right corner. There is an Import option in the bottom-up popup menu.
Many linux distros do not have appindicators enabled by default.
Install the appindicator extension
sudo apt install gnome-shell-extension-appindicator
reboot or log out/in, then run the following command:
gnome-extensions enable [email protected]
Install and then run the Extension Manager:
flatpak install flathub com.mattjakeman.ExtensionManager
flatpak run com.mattjakeman.ExtensionManager
Enable the Appindicator & KStatusNotifierItem Support extension
The polynom icon and menu should now appear on the system tray.
There are over 15 Decillion possible Graphatars. That's 15,576,890,575,604,480,000,000,000,000,000,000 for those who like things spelled out. This is why somtimes it takes a while to scroll past a lot of not-so-interesting Graphatars until you find one that you love.
Polynom is Beta software. Until Polynom 1.0 is released, it is almost guaranteed that your Graphatar image will change as we update the Graphatar engine with improvements. Sorry about that! These updates can in no way alter the private encryption key that your Graphatar represents - your data is still secure.
VBR makes VoIP calls more efficient, because your client will broadcast smaller packets when you are making quieter sounds in a call. This is the default setting. If you have reason to believe that your encrypted calls are likely to be sniffed, turn VBR off in your client and it will always transmit the same size VoIP packets, making it impossible to sniff when you're speaking out loud or just breathing on the call.
In short, yes. Every single call on Polynom is end-to-end encrypted. This is facilitated by the server. But what if the server is compromised? The answer is simple. Use Social Encryption as another layer of security, and even the server will have no knowledge of the call's content. With Social Encryption in your VoIP call, you have a user owned and controled layer of end-to-end encryption wrapped inside the server controlled end-to-end encryption. The call is still crystal clear. Our cryptography is future proof, DPI resistant, and quantum proof.
Self-hosting is running and maintaining a private server instead of using a cloud or service outside your control. This means you are responsible for your server's hardware, software, and security. Self-hosting is the foundation of data sovereignty and self-governance because it gives you control over your data.
Personal and enterprise data sovereignty is the right of individuals and businesses to control their private data, including where it is stored, how it is used, and who has access to it. Self-hosting provides several technical benefits, including data sovereignty, security, and compliance. Enterprises that self-host Polynom have full control over their work product, including where it is stored and how it is managed. Self-hosting can also help to increase security, as users can control the underlying infrastructure and security measures. Additionally, self-hosting can help teams to comply with regulations, such as those related to data privacy and legally mandated security.
Polynom offers self-hosting as an option for teams that require administrative control over their data and infrastructure. Self-hosted Polynom will be able to be installed on various operating systems, including Windows, Linux, and iOS. Currently Polynom-CE is Linux only.
Polynom also offers several resources to help teams self-host, including documentation, tutorials, and an FAQ.
Polynom Server uses port 1337 by default. That can be changed on startup using -p xxxx at the command prompt. It is important to make sure that port 1337 is open in your host firewall and forwards from your router.
A private server is only accessible to a specific group of people, while a public server is accessible to anyone. Polynom Server allows server owners to restrict access by "whitelisting" users. Whitelisting can be used to restrict access to the server to members of a specific organization or enterprise. This can help to protect the server's resources and data from unauthorized access or to conserve resources (i.e., bandwidth).
Server owners in high security environments should mark their server as "Untrusted" and then provide the server's public key to all their users for manual input. This forces the user's clients to verify they are on the right server before connecting. This prevents Man-In-The-Middle (MITM) attacks.
When a server is listed as "Trusted" it means that the client will accept the server's public key (and any changes to it) at face value, and continue to communicate. For most public facing communities this setting is fine, as it would be very resource intensive to try and spoof a server instance.
Server Admins and users with the manage_server permission can add or remove an ID hash from both the whitelist and the blacklist. This change takes place immediately. No restart of servers or clients is required. A user must be whitelisted in order to join a private server. If an ID is blacklisted, they will never be able to access the server again.
If I am a Server Admin or have the manage_roles permission, I can see all the invisible roles. I will always be able to see an invisible role if it has been assigned to me. If I am not a Server Admin or do not have manage_roles, I will see the highest visible role that others have, but I will not see any invisible roles.
Polynom uses the very latest and strongest encryption recommended by NIST and the US NSA's Commercial National Security Algorithm (CNSA) Suite.
For further information, see: The Commercial National Security Algorithm Suite 2.0 FAQ.
Polynom deploys: