Posted by jpluimers on 2021/07/26
–jeroen
Posted in Amazon.com/.de/.fr/.uk/..., Cloud, Infrastructure, Power User | Leave a Comment »
Posted by jpluimers on 2021/07/02
Having it accidentally made it to the CBL (Composite Blocking List – Wikipedia) a long time ago, I discovered the page started with (WayBack link mine):
IMPORTANT: Many CBL/XBL listings are caused by a vulnerability in Mikrotik routers. If you have a Mikrotik router, please check out the [WayBack] Mikrotik blog on this subject and follow the instructions before attempting to remove your CBL listing.
It wasn’t one of my Mikrotik devices, as first of all they had all being patched out of the box from a really empty internal network before being externally exposed to the internet or more busy internal networks, and second because the CBL entry was a one off on one specific day where someone used our guest network.
Some CBL entries in the range where it was displayed, quite a while after CVE-2018-14847 became public:
Posted in Firewall, Hardware, Infrastructure, Internet, MikroTik, Network-and-equipment, Power User, routers, SPAM, WinBox | Leave a Comment »
Posted by jpluimers on 2021/07/01
[WayBack] Maggs on Twitter: “Had to get a bucket to catch all the dropped packets.… “
To me it seemed the bitbucket was the final destination of /dev/null, but others chimed in as well:
Apart from my [WayBack] Jeroen Pluimers on Twitter: “Is that where /dev/null ends?… “, it totally reminded me of the below Dilbert strip which I could not find at first. So I was glad with [WayBack] David Sheryn Twitter: dilbert.com/strip/1996-05-02.
Posted in Development, Fun, Infrastructure, Software Development | Leave a Comment »
Posted by jpluimers on 2021/06/22
I originally posted this in a docker on docker thread, but I think it holds universally:
[WayBack] Jeroen Pluimers on Twitter: “Not having done docker, but having developed enough software to have the impression that as soon as things get hierarchical, things eventually end up in a mess. Somewhere down the road something won’t cope with depth/breadth/size and break badly.”
This despite the cool gif in the reply:
[WayBack] Duffie Cooley on Twitter: “… “
I found the below video files by searching for zzzz
Original thread start:
[WayBack] Duffie Cooley on Twitter: “When you hear Docker in Docker what do you think of? docker socket: Mounting in the underlying docker.sock and allowing a container to make new containers. kernel privs: Giving enough privs to a new container that it can make new containers cause it shares a kernel.”
–jeroen
Posted in Algorithms, Cloud, Containers, Development, Docker, Infrastructure, Kubernetes (k8n), Software Development | Leave a Comment »
Posted by jpluimers on 2021/05/05
A while ago I wrote about Helping the WayBack ArchiveTeam team: running their Warrior virtual appliance on ESXi.
Since it was scheduled before my cancer treatment started and got posted when still recovering from it, I missed that version 3.2 of the [Wayback] ArchiveTeam Warrior appliance appeared in the [Wayback] Releases · ArchiveTeam/Ubuntu-Warrior at [Wayback] Release v3.2 · ArchiveTeam/Ubuntu-Warrior. You can download it form these places:
These two sites have not yet been updated, so they contain the older versions:
The source code now has been moved three times:
Posted in *nix, *nix-tools, ArchiveTeamWarrior, Cloud, Containers, diff, Docker, ESXi5, ESXi5.1, ESXi5.5, ESXi6, ESXi6.5, ESXi6.7, ESXi7, Infrastructure, Internet, InternetArchive, Kubernetes (k8n), KVM Kernel-based Virtual Machine, patch, Power User, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation, WayBack machine | Leave a Comment »
Posted by jpluimers on 2021/04/16
[WayBack] Ryan James Spencer on Twitter:
“I wrote a quick Dockerfile so people who purchase Bite Size Networking from @b0rk can quickly have access to the tools. You can slim the image down to do debugging on docker networks once you get comfortable with which tools are most useful to you.”
He is planning to do more, so maybe a few of [WayBack] wizard zines get encapsulated into dockerfiles as well.
–jeroen
PS: [WayBack] Dockerfile | Docker Documentation
| # N.B. The only tool missing here that is mentioned in the document is `zenmap` | |
| # purely because this image is intended to be run via a CLI and `zenmap` is a GUI | |
| # to `nmap` i.e. one can play around with the tools by running: | |
| # | |
| # $ docker build –name bite_size_networking:latest . | |
| # $ docker run –rm -d –name bsn_test bite_size_networking:latest | |
| # $ docker exec -it bsn_test bash | |
| # | |
| # Alternatively, one can change the `ENTRYPOINT` to `["bash"]` and run: | |
| # | |
| # $ docker run -it –name bsn_test bite_size_networking:latest | |
| # | |
| # then later (after exiting the shell): | |
| # | |
| # $ docker start bsn_test | |
| # $ docker attach bsn_test | |
| # | |
| # One can also run this image on a docker network to capture packets and so | |
| # forth for debugging purposes. Once you've found the tooling that best suits | |
| # your needs, it may make sense to make a slimmed down version of this | |
| # Dockerfile and, if wireguard isn't needed, base this image off | |
| # `debian:stable` instead. | |
| # | |
| # Lastly, you can purchase Bite Size Networking or Julia's other fantastic | |
| # zines over at https://wizardzines.com/ | |
| # We use `unstable` here since we install `wireguard` below | |
| FROM debian:unstable | |
| RUN apt update && \ | |
| DEBIAN_FRONTEND=noninteractive apt install -y \ | |
| dnsutils \ | |
| curl \ | |
| nmap \ | |
| tcpdump \ | |
| ngrep \ | |
| mitmproxy \ | |
| iptables \ | |
| ethtool \ | |
| stunnel \ | |
| hping3 \ | |
| lsof \ | |
| ipcalc \ | |
| p0f \ | |
| iperf \ | |
| apache2-utils \ | |
| wget \ | |
| python3 \ | |
| iftop \ | |
| nethogs \ | |
| iptraf \ | |
| httpie \ | |
| nload \ | |
| aria2 \ | |
| nftables \ | |
| tcpflow \ | |
| telnet \ | |
| openvpn \ | |
| links \ | |
| wireguard \ | |
| tshark | |
| ENTRYPOINT ["sh", "-c", "while true; do sleep $(( 60 * 60 * 24 )); done"] |
Posted in *nix, *nix-tools, Cloud, Containers, Docker, Infrastructure, Power User | Leave a Comment »
Posted by jpluimers on 2021/03/19
The [WayBack] Archiveteam helps the WayBack machine with feeding new content.
You can help that team by running one or more “warrior” virtual machine instances. The VM is distributed as a virtual appliance in an ova file according to the Open Virtualization Format.
That format sounds more generic than it actually is, so the (at the time of writing) archiveteam-warrior-v3-20171013.ova file at [WayBack] Index of /downloads/warrior3/ was created for VirtualBox.X
This meant running it on VMware ESXi or VMware vSphere takes a few steps for patching it, then uploading it to your VMware host.
Since I might want to run the appliance on multiple places or multiple instances, I wanted to have a ready-to-go solution, I created a git repository with both the patch instructions and the update at [WayBack] wiert.me / public / ova / archiveteam-warrior-v3-20171013.ESXi · GitLab.
Posted in ArchiveTeamWarrior, Cloud, Containers, Docker, Infrastructure, Internet, InternetArchive, Kubernetes (k8n), Power User, WayBack machine | Leave a Comment »
Posted by jpluimers on 2021/02/26
Doing full stack development and operations requires one to think about compromises too. Randall Munroe did just that and created an OSI 7 layer like [WayBack] xkcd: Stack episode 2166:
Title text: Gotta feel kind of bad for nation-state hackers who spend years implanting and cultivating some hardware exploit, only to discover the entire target database is already exposed to anyone with a web browser.
And of course there is also a [WayBack] ExplainXKCD 2166
–jeroen
Posted in Development, DevOps, Software Development | Leave a Comment »
Posted by jpluimers on 2021/02/17
If your company manages your own infrastructure, be sure you have monitoring on all levels.
It saves you from customers discovering issues like this: [WayBack] Thread by @jpluimers: “The @EmbarcaderoTech docwiki is down due to an error in duobook2.[…]”:
The @EmbarcaderoTech docwiki is down due to an error in duobook2. URLs pointing to wiki content fail, no matter the product. Examples for Rio and XE2 grabbed from docwiki.embarcadero.com/Libraries/Rio/… and docwiki.embarcadero.com/Libraries/XE2/…
This is the #1 reason for allowing archival of all your product documentation web-content in the @internetarchive, even for non-current products, as now only parts that have been allowed to save in the past are available.Apart from nobody noticing the outage yet, which is bad in it’s own way, I hope the cause is not somebody fiddling with duobook (3 year old and unmaintained) without testing the consequences. As that would make the cause of the outage embarrassing.
[WayBack] https://github.com/ElectricVersion/DuoBook
Finally it is rather odd to get a HTTP 200 SUCCESS code on a failure. A HTTP 500 or 503 would be far more appropriate.
I wonder if that is a @mediawiki thing; maybe they could shed some light on that.
References en.wikipedia.org/wiki/List_of_H… and en.wikipedia.org/wiki/List_of_H….
The cool thing is that the stack traces teach you a lot about how a framework is structured.
Related:
Exception encountered, of type "ArgumentCountError" [6a5b64d3a502a9acff148fe1] /Libraries/Rio/en/Main_Page ArgumentCountError from line 420 of /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php: Too few arguments to function DuoBook2Template::displayPrefs(), 0 passed in /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php on line 99 and exactly 1 expected Backtrace: #0 /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php(99): DuoBook2Template->displayPrefs() #1 /var/www/html/shared/BaseWiki27/includes/skins/SkinTemplate.php(248): DuoBook2Template->execute() #2 /var/www/html/shared/BaseWiki27/includes/OutputPage.php(2335): SkinTemplate->outputPage() #3 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(743): OutputPage->output() #4 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(509): MediaWiki->main() #5 /var/www/html/shared/BaseWiki27/index.php(43): MediaWiki->run() #6 {main}
Exception encountered, of type "ArgumentCountError" [d3d353581c3915881b976ab6] /Libraries/XE2/en/Main_Page ArgumentCountError from line 420 of /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php: Too few arguments to function DuoBook2Template::displayPrefs(), 0 passed in /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php on line 99 and exactly 1 expected Backtrace: #0 /var/www/html/shared/BaseWiki27/skins/DuoBook2/DuoBook2.php(99): DuoBook2Template->displayPrefs() #1 /var/www/html/shared/BaseWiki27/includes/skins/SkinTemplate.php(248): DuoBook2Template->execute() #2 /var/www/html/shared/BaseWiki27/includes/OutputPage.php(2335): SkinTemplate->outputPage() #3 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(743): OutputPage->output() #4 /var/www/html/shared/BaseWiki27/includes/MediaWiki.php(509): MediaWiki->main() #5 /var/www/html/shared/BaseWiki27/index.php(43): MediaWiki->run() #6 {main}
–jeroen
Posted in Development, DevOps, Infrastructure, Power User, Software Development, Web Development | Leave a Comment »
Posted by jpluimers on 2021/01/15
In case I ever need to setup shipment tracking: [WayBack] The multi-carrier platform for future-proof delivery.
We believe delivery is the biggest game changer in e-commerce. So you need software that makes shipping easy and your customer happy. We do just that.
–jeroen
Posted in Cloud, Infrastructure, LifeHacker, Power User | Leave a Comment »
The Wiert Corner - irregular stream of stuff 