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...
I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in...
This post concludes my 2000-2025: 25 years in ICT series with a bit of a shameless plug: I've made it to Director! The 9 years at Proemion have been a breathtaking climb: from part-time software developer, to devops, to Team lead devops, to Group head devops and datacenter, Head of R&D, and now Director of Product of Engineering. To celebrate this, I decided to reflect on how I got here, perhaps it will be useful to others too. I did it Not to sound ungrateful or arrogant, but the first thing I should acknowledge is that I did this. I got help and support but it was ultimately me who put in the hours, went for the uncomfortable challenge ad asked for the additional responsibilities. I'm very proud of what I've accomplished, and I'd like to remind all of you that you should be too. Always! The only question I sometimes ask myself is where would I be if I started sooner. Since I don't have a time machine, I'm just content I got where I am right now and also...