diff options
| author | Your Name <you@example.com> | 2025-04-02 23:37:49 -0600 |
|---|---|---|
| committer | Your Name <you@example.com> | 2025-04-02 23:37:49 -0600 |
| commit | 46e780b004309f675f93d01a551cd27b8fd161ed (patch) | |
| tree | 3c2e053d7702c71f759484a1251399b52c34360a /feed.html | |
| parent | c15160c18fb09f0342f4102f080b30d64799d99c (diff) | |
moar feed testing
Diffstat (limited to 'feed.html')
| -rw-r--r-- | feed.html | 426 |
1 files changed, 26 insertions, 400 deletions
@@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> -<!-- 2025-04-02 Wed 23:29 --> +<!-- 2025-04-02 Wed 23:36 --> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <title>My Feed</title> @@ -197,20 +197,32 @@ <body> <div id="content" class="content"> <h1 class="title">My Feed</h1> -<div id="outline-container-org60c4b51" class="outline-2"> -<h2 id="org60c4b51">Prepping for v2 of my salt repo   <span class="tag"><span class="note">note</span></span></h2> -<div class="outline-text-2" id="text-org60c4b51"> +<div id="table-of-contents" role="doc-toc"> +<h2>Table of Contents</h2> +<div id="text-table-of-contents" role="doc-toc"> +<ul> +<li><a href="#org96860f2">1. Prepping for v2 of my salt repo   <span class="tag"><span class="note">note</span></span></a></li> +<li><a href="#orgaae5c46">2. Methods of installing software in QubesOS w/ Saltstack   <span class="tag"><span class="post">post</span></span></a></li> +<li><a href="#org92315cc">3. Website update   <span class="tag"><span class="note">note</span></span></a></li> +<li><a href="#org7f08ec2">4. Convenient torrenting with qBittorrent   <span class="tag"><span class="post">post</span></span></a></li> +<li><a href="#org500c073">5. QubesOS Saltstack configuration v1   <span class="tag"><span class="post">post</span></span></a></li> +</ul> +</div> +</div> +<div id="outline-container-org96860f2" class="outline-2"> +<h2 id="org96860f2"><span class="section-number-2">1.</span> Prepping for v2 of my salt repo   <span class="tag"><span class="note">note</span></span></h2> +<div class="outline-text-2" id="text-1"> <p> I’ve massively restructured my salt repo and added enough features that I’m going to make a new repository and release it again in full, as a 2.0 version. This should be done within the next week or two. </p> </div> </div> -<div id="outline-container-org8698157" class="outline-2"> -<h2 id="org8698157"><a href="org:../website/posts/installing-software-salt-qubes.org">Methods of installing software in QubesOS w/ Saltstack</a>   <span class="tag"><span class="post">post</span></span></h2> +<div id="outline-container-orgaae5c46" class="outline-2"> +<h2 id="orgaae5c46"><span class="section-number-2">2.</span> <a href="org:../website/posts/installing-software-salt-qubes.org">Methods of installing software in QubesOS w/ Saltstack</a>   <span class="tag"><span class="post">post</span></span></h2> </div> -<div id="outline-container-org6dc4776" class="outline-2"> -<h2 id="org6dc4776">Website update   <span class="tag"><span class="note">note</span></span></h2> -<div class="outline-text-2" id="text-org6dc4776"> +<div id="outline-container-org92315cc" class="outline-2"> +<h2 id="org92315cc"><span class="section-number-2">3.</span> Website update   <span class="tag"><span class="note">note</span></span></h2> +<div class="outline-text-2" id="text-3"> <p> I’ve changed a few things about the website: </p> @@ -228,401 +240,15 @@ I’ve figured out how to create an RSS feed using <code>ox-rss</code>, whic </p> </div> </div> -<div id="outline-container-orgfbca32a" class="outline-2"> -<h2 id="orgfbca32a"><a href="org:../website/posts/qbittorrent.org">Convenient torrenting with qBittorrent</a>   <span class="tag"><span class="post">post</span></span></h2> -</div> -<div id="outline-container-org5da6f1e" class="outline-2"> -<h2 id="org5da6f1e"><a href="org:../website/posts/qubes-salt-v1.org">QubesOS Saltstack configuration v1</a>   <span class="tag"><span class="post">post</span></span></h2> -</div> -<div id="outline-container-org08f20c8" class="outline-2"> -<h2 id="org08f20c8">Create an anonymous Whonix environment with KVM + NixOS   <span class="tag"><span class="post">post</span></span></h2> -<div class="outline-text-2" id="text-org08f20c8"> -</div> -<div id="outline-container-org7f5739f" class="outline-3"> -<h3 id="org7f5739f">The why</h3> -<div class="outline-text-3" id="text-org7f5739f"> -<p> -I’ve spent significant time using QubesOS on various computers, and I’ve been thoroughly spoiled by the VM magic Zen and the Qubes team have enabled. For a few reasons though, I’ve recently switched my main laptop from running QubesOS to NixOS. NixOS is great: it’s declaratively managed, fast, stable, has tons of fresh packages, but I can’t help but feel like my trust in the system has decreased a little bit due to the lack of isolation via virtualization that QubesOS provides. -</p> - -<p> -(3/1/2025 update: I’m using QubesOS again) -</p> - -<p> -Luckily, while VMs are fantastic to use especially with QubesOS, it’s very much possible to get some of the benefits of QubesOS on a host Linux system like NixOS. -</p> - -<p> -To demonstrate this, I’ll be going through a Whonix installation on NixOS using KVM, nix.configuration, and home-manager. I’ll talk a bit about the security trade-offs of using KVM over VirtualBox or on QubesOS, and how Whonix can be a useful tool for elevating your secure posture, protecting your host from malware and your activity from being deanonymized. -</p> -</div> -</div> -<div id="outline-container-org71bfc86" class="outline-3"> -<h3 id="org71bfc86">What’s Whonix?</h3> -<div class="outline-text-3" id="text-org71bfc86"> -<p> -Whonix is a 2-VM setup for compartmentalizing your computing, and uses the Tor Network to keep your activity anonymous. It runs on KickSecure (hardened Debian). -</p> - -<p> -The Whonix “Gateway” VM creates, maintains, and makes available a ’Tor-ified’ network connection for the Workstation. -</p> - -<p> -The Whonix “Workstation” VM is where you’ll do your actual computing. It comes with a graphical XFCE desktop with a suite of applications. You can use the build-in Tor Browser to browse anonymously, or use any of the other included applications and have all of it routed through Tor. -</p> -</div> -</div> -<div id="outline-container-orga47096c" class="outline-3"> -<h3 id="orga47096c">KVM vs VirtualBox</h3> -<div class="outline-text-3" id="text-orga47096c"> -<p> -Whonix supports 2 type-2 hypervisors: KVM and VirtualBox. KVM is build into the Linux kernel, and is thus fully <a href="https://www.gnu.org/philosophy/free-sw.en.html">Free Software</a>. VirtualBox is developed and maintained by Oracle, and is not Free software. I’ll be using KVM for these examples, but there’s a <a href="https://www.whonix.org/wiki/VirtualBox">convenient guide for VirtualBox</a>. -</p> -</div> -</div> -<div id="outline-container-org33aa7b2" class="outline-3"> -<h3 id="org33aa7b2">KVM vs QubesOS Zen</h3> -<div class="outline-text-3" id="text-org33aa7b2"> -</div> -<div id="outline-container-org6116770" class="outline-4"> -<h4 id="org6116770">Hypervisor simplicity</h4> -<div class="outline-text-4" id="text-org6116770"> -<p> -KVM is part of the Linux kernel, meaning that the virtualization is being done by a larger, monolithic program than a type-1 hypervisor like Zen, with a larger attack surface. -</p> -</div> -</div> -<div id="outline-container-org68b4140" class="outline-4"> -<h4 id="org68b4140">Type-1 vs type-2 hypervisor</h4> -<div class="outline-text-4" id="text-org68b4140"> -<p> -KVM runs on a host Linux system, and therefor the contents of the VM are only as secure as the host system. This is perhaps the biggest downside to running this KVM setup over Qubes in terms of security. I’d recommend delegating any risky activity to VMs like Whonix to try to mitigate the risk of malware running on your host system. -</p> -</div> -</div> -<div id="outline-container-orgf2bdbc2" class="outline-4"> -<h4 id="orgf2bdbc2">No sys-net/firewall/usb/audio/etc.</h4> -<div class="outline-text-4" id="text-orgf2bdbc2"> -<p> -QubesOS uses VMs to compartmentalize the hardware, and running Whonix on a Linux host keeps those in the domain of the large Linux kernel. -</p> -</div> -</div> -<div id="outline-container-org2e01a85" class="outline-4"> -<h4 id="org2e01a85">Performance</h4> -<div class="outline-text-4" id="text-org2e01a85"> -<p> -Whonix on KVM performs about as well as on QubesOS (varying based on how much virtual CPU/memory you allocate of course), but a big benefit of having a Linux host is that the applications ran in it won’t be slowed down by virtualization. Risky activities can be compartmentalized while keeping the main system fast and convenient to use. -</p> -</div> -</div> -<div id="outline-container-orge8d6502" class="outline-4"> -<h4 id="orge8d6502">Relevant Whonix security documentation</h4> -<div class="outline-text-4" id="text-orge8d6502"> -<p> -The advantages QubesOS has over KVM listed above are just a few basic examples. QubesOS has a much more robust security model in many ways, and if your security is <b>essential</b>, you should understand the downsides: -</p> -<ul class="org-ul"> -<li><a href="https://www.whonix.org/wiki/Qubes/Why_use_Qubes_over_other_Virtualizers">https://www.whonix.org/wiki/Qubes/Why_use_Qubes_over_other_Virtualizers</a></li> -</ul> -</div> -</div> -</div> -<div id="outline-container-org344058d" class="outline-3"> -<h3 id="org344058d">Installing Whonix on KVM</h3> -<div class="outline-text-3" id="text-org344058d"> -<p> -Make sure to check the relevant NixOS and Whonix documentation to ensure these examples are up-to-date. Always be weary of executing commands from a random blog on the internet, and go to the source whenever possible. -</p> - -<ul class="org-ul"> -<li><a href="https://nixos.wiki/wiki/Virt-manager">https://nixos.wiki/wiki/Virt-manager</a></li> -<li><a href="https://www.whonix.org/wiki/KVM">https://www.whonix.org/wiki/KVM</a></li> -</ul> - -<p> -Some of this setup (packages, user groups, dconf settings, the actual virtualization setup) is declaratively configured, but many of the commands to set up Whonix are not. On a fresh NixOS system build with your configuration.nix, you’ll still need to download the Whonix images and set them up with the commands outlined below. It’s possible more (or even all?) of this could be done declaratively with more NixOS knowledge. -</p> -</div> -<div id="outline-container-orgafc3071" class="outline-4"> -<h4 id="orgafc3071">Installing KVM + Virt-manager</h4> -<div class="outline-text-4" id="text-orgafc3071"> -<p> -Enable libvirtd and virt-manager -</p> - -<div class="org-src-container"> -<pre class="src src-nix"> # /etc/nixos/configuration.nix - virtualisation.libvirtd.enable = true; - programs.virt-manager.enable = true; -</pre> -</div> - -<p> -Add user to the libvirtd group -</p> - -<div class="org-src-container"> -<pre class="src src-nix"> # /etc/nixos/configuration.nix - # Replace USER with your username - # extraGroups will likely be populated, just add libvirtd to whatever's already there - users.users.USER = { - extraGroups = [ "libvirtd" ]; - }; -</pre> -</div> - -<p> -Enable qemu connection by adding dconf settings through home-manager -</p> - -<div class="org-src-container"> -<pre class="src src-nix"> # /etc/nixos/configuration.nix - # Replace USER with your username - home-manager.users.USER = { pkgs, ... }: { - # Point virt-manager to qemu as a source for virtualization - dconf.settings = { - "org/virt-manager/virt-manager/connections" = { - autoconnect = ["qemu:///system"]; - uris = ["qemu:///system"]; - }; - }; - }; -</pre> -</div> - -<p> -Start qemu’s virtual networking, allowing VMs to communicate -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Start qemu networking</span> -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-autostart default -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-start default -</pre> -</div> -</div> -</div> -<div id="outline-container-org7dd7a41" class="outline-4"> -<h4 id="org7dd7a41">Download the Whonix XFCE .qcow archive</h4> -<div class="outline-text-4" id="text-org7dd7a41"> -<ul class="org-ul"> -<li>You can the most up-to-date versions directly from their website: -<ul class="org-ul"> -<li><a href="https://www.whonix.org/wiki/KVM#Download_Whonix">https://www.whonix.org/wiki/KVM#Download_Whonix</a></li> -<li>You can optionally append ’.torrent’ to the direct download URL on their site to download the torrent file. This can be used in any BitTorrent client to download with faster speeds and without using as much of the project’s bandwidth. If you have a BitTorrent client I recommend this method.</li> -</ul></li> -</ul> -</div> -</div> -<div id="outline-container-org1a59180" class="outline-4"> -<h4 id="org1a59180">Extract the archive</h4> -<div class="outline-text-4" id="text-org1a59180"> -<p> -Make sure your working directory and archive are both in your home directory. (You may need to <code class="src src-sh"><span style="color: #fabd2f;">mv</span> ~/Downloads/Whonix* ~/</code>) -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Unpacking archive with gnu tar</span> -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ tar -xvf Whonix*.libvirt.xz -</pre> -</div> -</div> -</div> -<div id="outline-container-orga618405" class="outline-4"> -<h4 id="orga618405">Agree to the Whonix Binary License Agreement</h4> -<div class="outline-text-4" id="text-orga618405"> -<p> -To read the agreement, use: -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Prints the license agreement</span> -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ more WHONIX_BINARY_LICENSE_AGREEMENT -</pre> -</div> - -<p> -Assuming you agree: -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Creates an empty file "..._accepted" that tells Whonix you agree</span> -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ <span style="color: #fabd2f;">touch</span> WHONIX_BINARY_LICENSE_AGREEMENT_accepted -</pre> -</div> -</div> -</div> -<div id="outline-container-org8830cfa" class="outline-4"> -<h4 id="org8830cfa">Setup Whonix virtual networks</h4> -<div class="outline-text-4" id="text-org8830cfa"> -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Add virtual networks</span> -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-define Whonix_external*.xml -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-define Whonix_internal*.xml - -<span style="color: #928374;"># </span><span style="color: #928374;">Activate the networks</span> -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-autostart Whonix-External -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-start Whonix-External -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-autostart Whonix-Internal -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system net-start Whonix-Internal -</pre> -</div> -</div> -</div> -<div id="outline-container-org8b5033f" class="outline-4"> -<h4 id="org8b5033f">Import Whonix Gateway and Workstation images</h4> -<div class="outline-text-4" id="text-org8b5033f"> -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Creates two qemu profiles for the Whonix VMs</span> -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system define Whonix-Gateway*.xml -<span style="color: #fabd2f;">sudo</span> virsh -c qemu:///system define Whonix-Workstation*.xml -</pre> -</div> -</div> -</div> -<div id="outline-container-org8e9b87b" class="outline-4"> -<h4 id="org8e9b87b">Image File Installation</h4> -<div class="outline-text-4" id="text-org8e9b87b"> -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Assigns those qemu VMs to the Whonix .qcow2 images</span> -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ <span style="color: #fabd2f;">sudo</span> <span style="color: #fabd2f;">mv</span> Whonix-Gateway*.qcow2 /var/lib/libvirt/images/Whonix-Gateway.qcow2 -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ <span style="color: #fabd2f;">sudo</span> <span style="color: #fabd2f;">mv</span> Whonix-Workstation*.qcow2 /var/lib/libvirt/images/Whonix-Workstation.qcow2 -</pre> -</div> -</div> -</div> -<div id="outline-container-org7a7d46a" class="outline-4"> -<h4 id="org7a7d46a">Remove Whonix home clutter</h4> -<div class="outline-text-4" id="text-org7a7d46a"> -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">WARNING: running this command will delete every file that starts with "Whonix" or "WHONIX" in your working directory.</span> -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ <span style="color: #fabd2f;">rm</span> Whonix* -<span style="color: #fe8019;">[</span>~/<span style="color: #fe8019;">]</span>$ <span style="color: #fabd2f;">rm</span> -r WHONIX* -</pre> -</div> -</div> -</div> -</div> -<div id="outline-container-org1ddf6ae" class="outline-3"> -<h3 id="org1ddf6ae">Post-installation</h3> -<div class="outline-text-3" id="text-org1ddf6ae"> -<p> -Use the virt-manager application to start Whonix-Gateway, and open its terminal. We’ll use setup-dist to create your Tor connection and otherwise prepare Whonix for use. -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Whonix Gateway VM</span> -<span style="color: #fe8019;">[</span>gateway user ~<span style="color: #fe8019;">]</span>% <span style="color: #fabd2f;">sudo</span> setup-dist -</pre> -</div> - -<p> -Upgrade the system to pull the latest packages: -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Whonix Gateway VM</span> -<span style="color: #fe8019;">[</span>gateway user ~<span style="color: #fe8019;">]</span>% <span style="color: #fabd2f;">sudo</span> apt-get dist-upgrade -</pre> -</div> - -<p> -Start the Whonix Workstation, and repeat the upgrade step: -</p> - -<div class="org-src-container"> -<pre class="src src-sh"><span style="color: #928374;"># </span><span style="color: #928374;">Whonix Workstation VM</span> -<span style="color: #fe8019;">[</span>workstation user ~<span style="color: #fe8019;">]</span>% <span style="color: #fabd2f;">sudo</span> apt-get dist-upgrade -</pre> -</div> -</div> -</div> -<div id="outline-container-org8d03dd6" class="outline-3"> -<h3 id="org8d03dd6">Using Whonix</h3> -<div class="outline-text-3" id="text-org8d03dd6"> -<p> -Assuming the VMs are booting properly and can receive updates, you should be good to go! You now have a compartmentalized environment where your traffic will be anonymized, and any malware should generally be contained to the VM (sophisticated enough malware could theoretically jump the KVM hypervisor, but if that’s part of your threat model you probably shouldn’t be getting security advice from this blog :P) -</p> -</div> -<div id="outline-container-org1aef1e0" class="outline-4"> -<h4 id="org1aef1e0">Some tips</h4> -<div class="outline-text-4" id="text-org1aef1e0"> -</div> -<ul class="org-ul"> -<li><a id="orgaf75173"></a>Basic applications<br /> -<div class="outline-text-5" id="text-orgaf75173"> -<ul class="org-ul"> -<li>Tor Browser: Fingerprinting-resistant browser made for anonymous internet use</li> -<li>VLC: Video player capable of playing almost media file you throw at it</li> -<li>KeePassXC: Offline password manager</li> -<li>GPA (Gnu privacy assistant): Graphical manager GPG/crypto functions</li> -<li>Electrum: Bitcoin wallet</li> -<li>Thunderbird: Mozilla email/calendar/RSS client</li> -<li>and more!</li> -</ul> -</div> -</li> -<li><a id="org0d79d33"></a>Staying secure and anonymous<br /> -<div class="outline-text-5" id="text-org0d79d33"> -<p> -Think before you act! Whonix gives you a good platform for staying anonymous, but you can absolutely de-anonymize yourself if you’re not careful. -</p> - -<ul class="org-ul"> -<li>If you’re signing into a service over Tor, understand that the service can tie your actions to your current Tor identity. You can’t sign into your personal Facebook over Tor and expect that Facebook won’t know exactly who you are.</li> -<li>If you’re talking in some IRC channel, be skeptical about sharing information about yourself.</li> -<li>If you’re using Electrum wallet to manage Bitcoin, understand the privacy implications of Bitcoin and where you’re sending/receiving from.</li> -<li>Installing extra extensions in the Tor Browser can affect your footprint and make you stand out from other Whonix users</li> -<li>etc, etc, etc</li> -</ul> - -<p> -There are an uncountable number of ways you could de-anonymize yourself, so <b>stay vigilant</b>. Understand the technology you’re using, the information you’re putting out, and put yourself in the perspective of an adversary trying to de-anonymize you. -</p> -</div> -<ul class="org-ul"> -<li><a id="org1144945"></a>Use a live system when possible<br /> -<div class="outline-text-6" id="text-org1144945"> -<p> -When you’re booting the Workstation VM, you can select the option to run it ’live’. This means that when you shutdown the VM, everything you did during the session is erased. -</p> - -<p> -This can be useful, if say, you’re vising a sketchy site and end up installing malware. Just reboot the VM and you’re back to a clean state. -</p> - -<p> -Ideally, you should only use Whonix persistantly for updating and installing packages from the Whonix repositories. You may want to also use a persistant session for setting up credentials in your KeePassXC database or setup GPG keys, but keep as much sporatic browsing as possible in the live mode. -</p> -</div> -</li> -<li><a id="org0bd9a32"></a>Optionally disable Javascript in Tor Browser<br /> -<div class="outline-text-6" id="text-org0bd9a32"> -<p> -Javascript adds a massive attack surface to your browser, and disabling it can remove entire categories of browser-based malware. But, many many sites rely on Javascript for basic functionality. -</p> - -<p> -Personally, I keep Javascript on because I trust KVM to contain malware relatively well, and I only use the Tor Browser in live mode so any potential malware will be wiped on reboot. -</p> - -<p> -If you care about further hardening the setup, and are willing to break many websites, Javascript can easily be disabled by setting the Tor Browser security level to the highest option. -</p> -</div> -</li> -</ul> -</li> -</ul> -</div> +<div id="outline-container-org7f08ec2" class="outline-2"> +<h2 id="org7f08ec2"><span class="section-number-2">4.</span> <a href="org:../website/posts/qbittorrent.org">Convenient torrenting with qBittorrent</a>   <span class="tag"><span class="post">post</span></span></h2> </div> +<div id="outline-container-org500c073" class="outline-2"> +<h2 id="org500c073"><span class="section-number-2">5.</span> <a href="org:../website/posts/qubes-salt-v1.org">QubesOS Saltstack configuration v1</a>   <span class="tag"><span class="post">post</span></span></h2> </div> </div> <div id="postamble" class="status"> -<p class="date">Created: 2025-04-02 Wed 23:29</p> +<p class="date">Created: 2025-04-02 Wed 23:36</p> </div> </body> </html> |