node-seccomp VS tealdeer

I was exploring the actual implementation[0] of a capabilities feature in Nodejs and was utilising seccomp (via libseccomp) on Linux at least to achieve a greater degree of security than might otherwise be possible by remaining in userland code. The idea is that you'd write your code, import whatever you like and define your capabilities upfront at initialisation. The problem is there's quite a big disconnect between what you are doing in JavaScript and what's happening with system calls in v8, libuv and the other native parts that it's difficult to predict what you need to block and what's actually going to happen. So I don't think my approach is really viable in a general sense, although capabilities in general I think would improve the situation if the wider community were to adopt the approach.

[0]. https://github.com/roryrjb/node-seccomp

Not really. 😉

There's also a cli program called tealdeer that does this kind of thing and uses a local cache. And there's a fuzzy search interactive cli cheatsheet program called navi that's also pretty cool (and you can write your own cheatsheets).

man command & -h/--help flags & tealdear

My new found love is tealdeer + fzf and this alias:

This is a nice tool for shortened man pages.

I use the rust implementation since I have cargo installed anyway. https://github.com/dbrgn/tealdeer

TeelDeer Github & Docs

tealdeer (loosely pronounced TLDR) provides example-based and community-driven man pages https://github.com/dbrgn/tealdeer

tealdeer for commandline cheatsheets