Sometimes we need to patch packages on OS distributions which are close or past EOL. If upstream updates are still available, it saves us a lot of effort patching dependencies from binary. To verify if an upstream update is available (e.g. curl), you can search in the security-tracker website like below: Information on source package curl An information disclosure vulnerability exists in curl <v8.1.0 when do ...security-tracker.debian.org

Below is a test I performed to understand how Kubernetes allocates resources. Test Plan In a K8S sandbox, add a few deployments with varying requests and limits Generate a fake high CPU load/high memory usage in the pods Expected outcome K8S does not allow over allocation (i.e. total resources requested…

I have RO filters installed under kitchen sink over the past 7 years. I have replaced many filters (stage 1–3 filters every few months, membrane every year or two). Sharing some tips after years of hands-on experience. The model I have is this one: APEC Water Systems ROES-50 Essence Series Top Tier 5-Stage Certified Ultra Safe Reverse Osmosis Drinking Water Filter System, 50 GPD https://www.amazon.com/APEC-5-Stage-Reverse-Drinking-Water/dp/B00I0ZGOZM

Here’s a write up for https://tryhackme.com/room/templates Recon After starting up the machine, as per instruction there’s a website running on port 5000. In my case: http://10.10.33.8:5000/ Click on the Convert to HTML button, it’ll convert the template to HTML. To make it easier to visualize the request, I replaced the…

This turns out to be my command line error. The arguments of docker run need to follow the right order. i.e. This will ignore the port mapping: docker run 09dad155f3cc -d -p 8080:8080/tcp and this will work as expected: docker run -p 8080:8080/tcp 09dad155f3cc -d

When building a Dockerfile from my MacBook: > docker build . Sending build context to Docker daemon 123kB Step 1/8 : FROM debian:jessie jessie: Pulling from library/debian no matching manifest for linux/arm64/v8 in the manifest list entries A quick search of the error “no matching manifest for linux/arm64/v8 in the manifest list entries” indicates it has to do with Apple M1 Chip. Workaround Pull the image with the platform specified:

In sshd_config, there’s a configuration parameter for MaxStartups. The man page: MaxStartups Specifies the maximum number of concurrent unauthenticated connections to the SSH daemon. Additional connections will be dropped until authentication succeeds or the LoginGraceTime expires for a connection. The default is 10:30:100. Alternatively, random early drop can be enabled…

Below is my ‘quick fix’ (bandaid) solution to the following errors/exceptions. The errors Error: Execution of '/usr/bin/gem install --no-rdoc --no-ri cowsay' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption) invalid option: --no-rdoc Did you mean? no-force A reference article https://github.com/puphpet/puphpet/issues/2838 The ‘quick fix’ W.r.t. the reference article, I searched for the file ‘gem.rb’. Since ‘locate’ was not installed in the OS, I used the ‘find’ command to look for the file:

Continued from the previous post. As I am making full use of my 30-days free account in Azure, I have setup a pair of Puppet servers to test (with respect to the reference article at the bottom). A problem In the Puppet master, I have: /etc/puppet/manifests/site.pp with content file {'/tmp/example-ip'…