jsoncrack.com VS libsodium

They are used in Editor component. Part 4 explains about Editor component.

useGraph has a lot going on, but we will look for setGraph as this is the side effect performed in setJson explained above.

In this post, let's understand the editor's Panes component used in jsoncrack.com.

Open src/pages/editor.tsx in a new tab and let’s take the top down approach. Let’s first look into the components used.

Visit GitHub

https://github.com/AykutSarac/jsoncrack.com As far as I can see they don't use any package to visualize, but I also need that package, if you find it please let me know!

looks a lot like JSON Crack with added support for additional formats and not being open-source

As we've seen in this article, there are many different tools available to help us work with JSON data. From visualizing and exploring data with JSON Crack, formatting it with JSON Formatter & Validator, converting it to other formats like CSV with Konklone.io, and validating it against a schema with JSON Schema — these tools can help make working with JSON data much easier and more efficient.

Libsodium has been around for a while, so probably the reason it was posted is that version 1.0.19 was just released: https://github.com/jedisct1/libsodium/releases/tag/1.0.19-RE...

Updated NuGet and Swift packages are going to be uploaded soon.

AEGIS-128X and 256X are not there yet, but if you need them, they are available in libaegis: https://github.com/jedisct1/libaegis

All the code from libaegis will eventually be merged into libsodium, including the incremental update API which is especially useful for TLS.

To version the dependency you can check the current stable tree in git and save the date and git hash.

To address both of these vulnerabilities, you should instead use a library that handles these sharp edges for you. A well received library in the security and cryptography communities is libsodium. It has high level functions that handle password hashing and data encryption for you, reducing the risk that you introduce vulnerabilities in your code, such as you have here.

In general, cryptography is really hard. So for example, an attacker could construct a message that if you signed would leak information, ie it reduces the space of possible keys such that it can be brute forced. I’m not entirely sure if you could do that with a transfer function. But it’s certainly possible. That said, there are a ton of smart devs trying to prevent that as well so I’m not assuming anything here. But prudent practices are likely good to follow. Be very careful calling anything from your cold wallet etc. Use disposable keys for anything a bit risky. I took a sec to google an example and this is the closest I could find. https://github.com/jedisct1/libsodium/issues/170

Hi everyone! I'm learning Rust while on a break between jobs, and as I'm particularly interested in interfacing Rust with C and in cryptography, I've decided to write a wrapper around libsodium (https://github.com/jedisct1/libsodium) in Rust. This is purely a hobby project and I probably won't ever release it as there are already some open-source Rust bindings available for the library.

Can anyone recommend between Librandombytes and libsodium ramdombytes?

https://github.com/jedisct1/libsodium/tree/master/src/libsod...