Show threadKevin Karhan Jan 10

@F3715H @ellie @4censord not really practical for 16kB, espechally since most Punch Sets only come with Uppercase letters & numbers, so you'd have to encode it with #base32hex...

https://en.wikipedia.org/wiki/Base32

4censord :nfp: (@[email protected])

i need something qr-code like for visually storing about 16kb of data. it should be resonably well known and expected to be decodable for the next 10 years. does something like that exist? otherwise i'm just gonna split my data into chunks and put them into normal qrcodes

UnFUG Mastodon
Show threadKevin Karhan Apr 25, 2025

@landley @jschauma @ryanc @0xabad1dea I think #IPv6 would've gotten more acceptance if it was merely a 4x long #IPv4 annotation instead of doing hexadecimals.

Kevin Karhan Jul 23, 2023

@jhwgh1968 @cendyne depends on the OS...

OFC /dev/urandom will not block unlike /dev/random when it runs out of entropy, but unless you're generating thousands of large passwords in a short amount of time and don't have any hardware crypto acceleration, that should never be an practical issue.

OFC you could also pipe the raw output through several hashing functions before outputting as #Base64hex or #Base32hex, but I prefer #KISS principle in those functions.

https://unix.stackexchange.com/questions/324209/when-to-use-dev-random-vs-dev-urandom/324210#324210

When to use /dev/random vs /dev/urandom

Should I use /dev/random or /dev/urandom? In which situations would I prefer one over the other?

Unix & Linux Stack Exchange