privatize

I partially encrypt/decrypt a file based on the presence of special HEREDOCs (ie <<PRIVATE) so I can keep a public daily journal and keep some notes private. The tool is still a WIP as it isn't portable between machines -- https://github.com/higgins/privatize more on it here: https://encapsulate.me/writing/Privatize.html

Yes! I keep a daily log tracked in git. All of it public although some information is encrypted with my privatization tool (https://github.com/higgins/privatize). The log itself is a simple org file but I parse and render it in html here so that I can share important event dates (eg: my wedding) with my family and friends. Here is what I did yesterday: https://encapsulate.me/log.html?date=07-18-2022 Here is my wedding date: https://encapsulate.me/log.html?date=03-04-2022

ooo, good call out. thanks! currently i only have one warning in place if I forget to close there heredoc: https://github.com/higgins/privatize/blob/main/index.js#L168 but could add some more error checking. added to TODOs: https://github.com/higgins/privatize/commit/9696f30576897898...

hey, thanks! added to my TODOs: https://github.com/higgins/privatize/commit/53f62483f943112e...

Thanks for taking a look! Yeah, I should cleanup the wording in here a bit: The IV is a sha1 hmac of the content to be encrypted. The 16B that are stored with the key is used to initialize the sha1 hmac: https://github.com/higgins/privatize/blob/0.1.1/index.js#L20...

I might not have properly understood this tool, but is the encryption key and iv getting reused? If so, it's usually quite unsafe to reuse IVs (but consult a cryptographer, YMMV). Feels weird to stuff the IV with the key, it should live with the ciphertext. (I only glanced at the code for a few minutes, so I could be wrong: https://github.com/higgins/privatize/blob/0.1.1/index.js#L73)

Yikes, do all filters do that? https://github.com/higgins/privatize/blob/0.1.1/index.js#L98 Also, it's 2022 and I still have to remind people not to commit binary assets into git repos, as the repo will grow without bound: https://github.com/higgins/privatize/tree/main/release That's the very problem that GitHub Releases were designed to address, and has the extra awesome benefit of using (currently) AWS S3 for distribution, which is almost certainly going to be faster and place less load upon github.com than .../raw/main/release/whatever.exe Also, while the Brew tap indicates your code is ISC, there is no license file in your repo: https://github.com/higgins/homebrew-privatize/blob/main/Form...

Hi HN! I wrote a tool that partially encrypts files based on the presence of a HEREDOC. Check it out: https://github.com/higgins/privatize When added to a git repo, it will automatically transparently encrypt/decrypt files you want privatized. For example if you configured your repo to privatize the file `example.txt`, you could write: ``` Today I a burrito. <<PRIVATE I was on the toilet for hours. PRIVATE I got a lot of reading done. ``` but when git-commit'ed would become: ``` Today I a burrito. <<PRIVATE xuJ0fld2vmNWaVLogTIufmWsiFso PRIVATE I got a lot of reading done. ``` Diffing works as you expect (on the unencrypted source) and only those with the `privatize` symmetric key would be able to unlock and decrypt these files. Why did I do this? I keep a public log of what I plan