It's that time of the year again and, since it appears that the Maya spared us, I want to share with you a couple of gists that I came up with recently that could be generally useful. Btw, there are lots of other gists on my gist.github.com profile, check them out.
If you find these script useful star them on github, drop me a comment or just share them. Once again, Merry Christmas everyone!
The first one is for Java people and is a HttpServletRequestWrapper that supports:
injection of the principal: for those cases when you use trust authentication and you are rolling your own SSO solution and/or you need to integrate with an existing SSO solution (I used it with for CAS)
supports reading of the InputStream multiple times. We all know that in a POST the request input stream can only be read once, so this will definitely help you if you need to access the post body or a request parameter in a Filter and make sure the upstream servlets/filters still work
The second gift gist is for Windows admins and is written in vbs (I even do VBS when it is necessary, now you get my twitter handle, don't you?). It is a login script that can be used in a Windows Domain to recreate Desktop links on each user logon. The configuration for each link is stored in the script as a dictionary of dictionaries and link-to-user assignment is done by adding the user to an AD group. The source is heavily commented and should be easy enough to understand for anyone who's ever programmed, even if not in vbs.
Since I could not find a quickstart to run opengrep with the full set of rules from their fork I thought I'd document what I found out. Setup Download the opengrep binary from github and make it executable with chmod +x . Clone the rules repo: git clone git@github.com:opengrep/opengrep-rules.git and clean it up to make it usable to opengrep: cd opengrep-rules rm -rf ".git",".github",".pre-commit-config.yaml", "elixir", "apex" find . -type f -not -iname "*.yaml" -delete rm -rf .github rm -rf .pre-commit-config.yaml Ensure opengrep can load the rules with: opengrep_manylinux_x86 validate . The same can be done for custom rules maintained in a separate repository. AFAIU Multiple repositories can be specified by repeating -f option as needed, see below. We are now ready to scan a repo, from the repo root directory run: opengrep_manylinux_x86 scan \ -f <path_to>/opengrep-rules \ --error \ --exclude-rule=VAL some ti...
The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive. Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive from the same removable disk.
A technique I use often with LLMs is meta-prompting Meta-prompting essentially uses the LLM to generate the prompt for the specific task that I require. This can be one shot or conversational, in any case I always ask for options so I can use the LLM to fully explore the space as opposed to constrain myself to whichever corner the LLM tuck itself into the first time. I might then choose one of the prompt exactly or mix them up. Example of one shot: write 5 prompts to produce a summary of <topic> so that I can gain a broad understanding of it Conversational instead takes more than one turn, for example: my goal is to have a broad understanding of <topic>. I want you to generate 5 prompts that help me achieve this task. I want you to ask me all the questions that you can come up with and use the answers to fine tune the prompts