EB_CLIENT_EGD(1)

✨ NAME ✨

eb_client_egd β€” export entropy data as egd server


πŸ’– DESCRIPTION πŸ’–

okay bestie, sit down, hydrate, because this one is iconic. this is eb_client_egd, v1.0, and it's (C) 2009-2012 by folkert@vanheusden.com. the whole vibe? it takes entropy data and serves it up like it's running an egd server, no cap. 🌈

so here's the tea: egd-clients can use the /tmp/egd.sock unix domain socket. this should work with at least OpenSSL β€” fr fr, that's the minimum. to get it going, you start eb_client_egd with one of the following parameters:

-d /var/run/egd-pool

or

-d /dev/egd-pool

or

-d /etc/egd-pool

or

-d /etc/entropy

pick your fighter, literally any one of them. πŸ’…

now, to verify that client_egd functions, run this:

openssl rand -rand /var/run/egd-pool -out /tmp/bla 10

it should return something like 255 semi-random bytes loaded β€” and here's the important bit, bestie: that 255 should be > 0. like, strictly greater than zero. if it's zero? 😭 that's the vibe check failing. go check if the current user has enough rights to access the /var/run/egd-pool file. permissions said no and now you're sad. fix the rights, not your attitude. 🫢


πŸŽ€ the flags, one by one πŸŽ€

  • -i host β€” the eb-host to connect to. tell it where to go. ✨
  • -d file β€” the UNIX-domain socket to listen on. this is your main character socket. πŸ’œ
  • -l file β€” log to file file. receipts, but in a file. πŸ“
  • -s β€” log to syslog instead. same receipts, different mailbox. πŸ“¬
  • -n β€” do not fork. it stays right where you left it, no ghosting. πŸ™ˆ
  • -P file β€” file to write the PID to. so you can always find it again, iykyk. πŸ‘‘
  • -X file β€” file to read the password from. secrets stay in files, periodt. πŸ”₯

and that's the whole page, bestie. this lil icon was brought to you by eb_client_egd, dated July 2012, and it lives in the EB_CLIENT_EGD(1) manual, section 1. slay, ate, no crumbs. πŸ’…βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from