News for hackers. Stuff that matters.
Re:Systemd needs official documentation on best practices by tharne on Friday November 08, 2019 @03:07PM (#21486176)
Here are some best practices:

- Small is beautiful.

- Make each program do one thing well.

- Build a prototype as soon as possible.

- Choose portability over efficiency.

- Store data in flat text files.

- Use software leverage to your advantage.

- Use shell scripts to increase leverage and portability.

- Avoid captive user interfaces.

- Make every program a filter.

Re:Systemd needs official documentation on best practices by beefhash on Friday November 08, 2019 @03:24PM (#21486332)
I know this is only tangentially related, but when you're bringing up UNIX philosophy...

> - Store data in flat text files.

Storing encryption keys or the like in flat text files is surprisingly hard, at least in C. I don't think it's even possible to use sscanf(3) without unexpected explosions, and otherwise you get to hand-roll your hex parsing code yourself (Base 64? Get yourself a library).

Re:Systemd needs official documentation on best practices by avar on Friday November 08, 2019 @03:52PM (#21486607)
Then don't do it the hard way and store something like a password in some general text file that needs to be parsed, just have the password in its own file. This is also good practice when that's otherwise a sane idea because you can apply separate permissions to that password file.

Working with that sort of file in C is trivial, you either open() and read() from that file, or mmap() it.

Re:Systemd needs official documentation on best practices by akira2501 on Friday November 08, 2019 @04:54PM (#21487239)
> Storing encryption keys or the like in flat text files is surprisingly hard, at least in C.

Storing keys (or other binary) data is _exceptionally_ easy with C. What's hard is _multiplexing_ it with other data in the same file, but you probably don't need to:

some.config:

keyfile=/some/path/to/just/the/key

Re:Systemd needs official documentation on best practices by marcosdumay on Friday November 08, 2019 @03:53PM (#21486610)
The GP is probably more focused on textual logs.

But yes, C is very weak on converting data from one encoding into another. You end-up always having to write your own encoder/decoder.

You should be able to convert between binary and base64 on memory more easily than during IO, and for encryption keys the buffers all have known size limits. As a rule sscanf will add security vulnerabilities to your code, so one should better avoid it if you do not trust your inputs.

Re:Systemd needs official documentation on best practices by derekp7 on Friday November 08, 2019 @03:32PM (#21486421)
> - Use software leverage to your advantage.

openssl's libcrypt has Base 64 routines in it.

Re:Systemd needs official documentation on best practices by pojzon on Friday November 08, 2019 @05:34PM (#21487641)
Storing data in text files is the biggest con pointed at proc. Store data in binary, so that its easier to read by everything.