Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Pgsodium Alternatives
Similar projects and alternatives to pgsodium
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
libsodium-xchacha20-siv
Deterministic/nonce-reuse resistant authenticated encryption scheme using XChaCha20, implemented on libsodium.
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
wiz-packet-map
Wizard101 tool that dynamically dumps packet data and decrypts packets to and from the server that use aes-gcm encryption
-
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better pgsodium alternative or higher similarity.
pgsodium reviews and mentions
Posts with mentions or reviews of pgsodium.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-31.
-
Macaroons Escalated Quickly
I like the "solve the now" perspective here, and having code examples is very helpful to understand some of the rational behind the approach. Having read your previous "tedious survey"[0] post on various token formats, I generally agree with a lot of your conclusions. Curious though about your thought process wrt macaroons vs biscuits.
To me the one major downside of macaroons has always been the single shared root symmetric key. Many use cases are addressed by third party attenuation, but then there are the problems like key rotation, having to do online verification, no built in encryption, no peer-to-peer support through an "untrusted" fly.io, and no third party token verification without decryption like in signcryption[1] schemes. Of course this is traded off by having to do PK issuance and management so I can see the simplicity of it.
Is fly.io scoping this pretty hard to just auth tokens with third party attenuation, or do you see further development and maybe moving to other token systems like biscuit when/if the need arises to address those known issues?
fwiw I've done a bit of research work myself on a token format using signcryption [2] where I explored addressing some of these ideas (but not the attenuation side of it yet, which I get is a big deal here).
[0] https://fly.io/blog/api-tokens-a-tedious-survey/
[1] https://github.com/jedisct1/libsodium-signcryption
[2] https://github.com/michelp/pgsodium/blob/feat/signcryption-t...
-
PostgreSQL Encryption: The Available Options
pg_sodium [1] is another great options for transparent (column level!) encryption. Its integrated with Supabase [2] if you want to give it a try
[1] https://github.com/michelp/pgsodium
-
Update - I built an app that analyses your worries and challenges your thoughts, looking for feedback
Yes! Concerning privacy: The entries are saved in Supabase and encrypted with pgsodium. I think there's a lot more to privacy, though – currently working on other safety measures like anonymization that I'll include before scaling. What sets the app apart: I have built the app specifically to integrate therapy tactics into your daily life and to make them a habit (e. g. if you talk to ChatGPT or Wysa it tells you what tactics to integrate and learn about them, with my app you actually integrate them) => less about learning, more about doing.
-
I built an app that helped me move on by teaching me how to react differently to my thoughts.
Valid concern. The entries are saved in Supabase and encrypted with pgsodium. I think there's a lot more to privacy, though – currently working on other safety measures like anonymization that I'll include before scaling and releasing the app to the broader public. Still looking for testers; sent you a DM. Let me know if you're in!
- pgsodium- Modern cryptography for PostgreSQL using libsodium.
-
Supabase secrets management available in beta
> Is Vault something that can handle this without getting into my app code? Basically, if i gave a someone root access to my supabase instance is that encrypted data safe?
The answer is slightly offset from your question, so let me start by pointing out that the Vault is about Encrypted Data At Rest. This is mentioned in the docs and in the blog and video, but it's something that I like to always mention first in discussions. The main purpose of the Vault is to store your data encrypted, so that it's encrypted on disk, and in backups. In SQL the decrypted secrets are available to you, because that's where you are using them and encrypted data must be decrypted to be useful.
If someone roots access to your database, then yes they can access the decrypted secrets through the view. This is by design, the secrets must be decrypted to be useful in query code. This risk is similar to someone rooting your application code, they will see decrypted secrets via your environment key, so no it won't protect you against anyone rooting processes in your stack that need useful access to secrets and it's not meant to. Like all security you must take a layered approach, the Vault is just one storage level layer strategy.
One big difference from the env var approach though is that the key Supabase uses to encrypt your secrets with the Vault is stored outside the database, it is inaccessible to SQL, which is an enhancement over sticking the raw key into an environment variable or a table that is accessible to your application. Instead of revealing the raw key, pgsodium has a feature called [Server Key Management](https://github.com/michelp/pgsodium#server-key-management) where you do not have access to the raw key, but instead reference keys by an key identifier. It is safe to store this identifier alongside the data it encrypts. The raw key itself is never stored. I'm very intentionally overusing the word "store" here, because that's specifically the layer of security that the Vault provides.
-
Supabase Vault
The article links directly to here, which may answer your question:
https://github.com/michelp/pgsodium#server-key-management
- Encrypting data for a Finance App
- How do I encrypt data before sending it to the database?
-
Show HN: Pgsodium – A Crytographic PostgreSQL Extension
Hey HN, I shared an earlier prototype version of pgsodium but I just released 2.0 and felt this could be a good opportunity to share some updates!
[pgsodium](https://github.com/michelp/pgsodium) 2.0.0 is a postgres extension that uses the [libsodium](https://doc.libsodium.org/) library to provide high-performance, modern cryptography support for PostgreSQL 10+.
2.0.0 includes a ton of new feature and a few bug-fixes:
* Support for [XChaCha20-SIV](https://github.com/jedisct1/libsodium-xchacha20-siv) deterministic nonce-free encryption, this is useful for one-time workflows sacrificing a bit of speed and larger key size without worrying about nonce-handling issues.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 25 Apr 2024
Stats
Basic pgsodium repo stats
15
508
5.4
6 months ago
michelp/pgsodium is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of pgsodium is C.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com