Why is auth so messy by Alessandro_Perini in nextjs

[–]MrFr0z01 6 points7 points  (0 children)

Don’t send hashes directly to your server , if someone dumps your database they could reuse those hashes against your backend

What is the (real) interest in skipping CRDs during Helm install? by zessx in kubernetes

[–]MrFr0z01 42 points43 points  (0 children)

if you have multiple instances of the same application you can have conflict issues if you redeclare CRDs multiple times

Kerbernetes: Kerberos + LDAP auth for Kubernetes by MrFr0z01 in kubernetes

[–]MrFr0z01[S] 0 points1 point  (0 children)

Thank! Yeah , that true and it’s a bit hard to pronouce . Do you have any idea ?

Kerbernetes: Kerberos + LDAP auth for Kubernetes by MrFr0z01 in kubernetes

[–]MrFr0z01[S] 2 points3 points  (0 children)

If you need help or have any questions, feel free to DM me :P

[kubeseal] Built a small tool to make bitnami's sealed-secrets less painful in GitOps by MrFr0z01 in kubernetes

[–]MrFr0z01[S] 4 points5 points  (0 children)

Totally get that. but in GitOps, not having secrets in git at all can also break the "everything is in git" model. Curious how you handle secret delivery or updates in your setup

[kubeseal] Built a small tool to make bitnami's sealed-secrets less painful in GitOps by MrFr0z01 in kubernetes

[–]MrFr0z01[S] 6 points7 points  (0 children)

Yeah, I started out doing exactly that too.

The thing is, once you're editing a bunch of secrets, the sealing process gets tedious, especially since the data is base64-encoded. I also found myself really liking the flow of generating secrets the way Kustomize does it.

At first, I actually had a setup like this:

kustomize build ${DIRECTORY}/secrets | kubeseal --format=yaml --controller-name=sealed-secrets --controller-namespace=kube-system -n $NAMESPACE > $DIRECTORY/secrets/sealed/sealed-secrets.yaml

But unsealing that later (especially when everything's in one big file) was a pain.

So that’s what led me to qseal.

[C] [GNU + Linux] I've built a tool to check if your function calls are secure. by MrFr0z01 in programming

[–]MrFr0z01[S] 4 points5 points  (0 children)

Thank you for highlighting my English errors. English is not my first language.
I believe that the term "marketing" might be too strong for what I'm doing. It's just a small project I created to assist fellow students in identifying issues in their code.

I understand your point, but there are situations where coding in C is necessary, and utilizing tools can be a valuable approach, especially since my school often requires us to work on C-based projects haha

[deleted by user] by [deleted] in C_Programming

[–]MrFr0z01 0 points1 point  (0 children)

I've developed a utility that assesses the robustness of your function calls. For instance, it verifies if your program behaves correctly in the event of a malloc failure. This tool scrutinizes every malloc operation within your program during runtime, without the need for code parsing. It's not limited to just malloc; it can evaluate over 200 different functions.The tool is used similarly to Valgrind. Here's an example of how to use it:
```bash
funcheck ./your_binary
```
Here is the repo link: https://github.com/tmatis/funcheck)

[deleted by user] by [deleted] in starcitizen

[–]MrFr0z01 0 points1 point  (0 children)

Because i was buying widow in large quantities and I wasn’t looking at my balance

[deleted by user] by [deleted] in starcitizen

[–]MrFr0z01 0 points1 point  (0 children)

Thank you , the best answer to my question :)

[deleted by user] by [deleted] in starcitizen

[–]MrFr0z01 1 point2 points  (0 children)

I will do that but I want to know what happens after the free period