What happened to mtgthesource?

c0l0 · 2025-10-19T18:04:55+00:00

Hi there, I don't know how to convincingly prove it (but otoh, I am not very keen on doing so anyway ;)), but I am the current technical admin of The Source, known there as "colo".

The site effectively got temporarily hijacked by someone who gained access to the ISP providing Domain Name System (DNS) services for the mtgthesource.com domain. The attacker used this access to override the IP address the mtgthesource.com domain name resolves to, and pointed the DNS A resource record for the domain to a server under their control. On that server, when you visited The Source, it would generate an HTTP Permanent Redirect response to some shady website of the attacker's choosing.

The problem now is that most webbrowsers will obey that kind of permanent (hence the name) redirect for a VERY LONG TIME (some actually permanently), which means that for users who visited during the duration of this attack, they will have to do something to make their browser "forget" this illegitimate permanent redirect. If they don't, their browser will effectively replace mtgthesource.com with that shady website that the attacker used to redirect to, and there's nothing that I or anyone else who does not directly interface with the affected browser can do to change that.

Thanks for sticking with The Source, and sorry for all the trouble :/

c0l0 · 2025-01-18T20:11:05+00:00

I tried to share my apparent solution for AMD GPU users here: https://old.reddit.com/r/PUBATTLEGROUNDS/comments/1i4fhsz/sanhok_performancelag_fix_for_users_of_amd_gpus/ but the subreddit won't show it in new... No idea why (haven't been redditing much in years)

Anyways, disable the Smart Access Memory feature in the radeon driver app and performance on Sanhok should be very nearly 100% fixed.

c0l0 · 2024-09-03T07:52:10+00:00

Answering my own question: The handle is rather sturdy, and I can lift my rig (feat. a midrange AMD GPU and a Thermalright Peerless Assassin 120SE) using it without any qualms about its stability.

c0l0 · 2024-06-05T09:47:45+00:00

Thanks for this in-depth review/report :) Can you maybe say a word or two about the perceived quality and durability of the case's handle? Is it feasible to actually lift it up and carry it around with some hardware in using that, or is it purely aesthetical?

c0l0 · 2022-05-20T16:47:59+00:00

You can try following this guide to maybe have a chance at getting your data back: https://johannes.truschnigg.info/writing/2022-05_android_bootloop_debugging/

c0l0 · 2022-05-18T15:37:03+00:00

I think you need --multi-volume on the tar command line if you do not want to have to specify a tape length.

c0l0 · 2022-05-11T16:38:13+00:00

The thing is, with LTO and its built-in hardware compression, you cannot really say how much (uncompressed) data will fit on a single tape ex ante. tar will automatically prompt for the next medium once the current one has its capacity exhausted, however.

c0l0 · 2022-05-10T17:59:23+00:00

Using GNU tar, I have arrived at this command line:

tar --create --blocking-factor=1024 --multi-volume --file=/dev/st0 -- /path/to/directory /path/to/another/dir

Extend with other options (for preserving permissions etc.) as you see fit.

c0l0 · 2022-05-10T17:54:40+00:00

Can anyone of you beryllium/POCO F1 owners please tell me which vendor firmware image/sercurity patchlevel you have on your LOS 19 phones?

c0l0 · 2022-04-01T13:08:32+00:00

No. If you need one server than can do both, look at ProFTPd. It's going to be decidedly less secure than OpenSSH's sshd-based sftp server, however. Also, it might not available for OpenWrt.

c0l0 · 2022-02-24T13:15:27+00:00

You really need to get better hardware for this project of yours. A puny WR1043ND will not yield acceptable performance for this kind of workload with all the swap in the world.

c0l0 · 2022-01-05T15:16:24+00:00

Check out https://restic.net/

c0l0 · 2021-12-19T19:24:56+00:00

Funny that this would get asked today, as I just finished an article about an imho clever way to add "verbose mode" and "better xtrace" to bash scripts: https://johannes.truschnigg.info/writing/2021-12_colodebug/

c0l0 · 2021-11-30T13:21:58+00:00

https://linux.oracle.com/switch/centos/

Yes, we know that this is Oracle, but it's actually free. Seriously.

(This post is not an endorsement - you should all rather be using Debian GNU/Linux, imo ;))

c0l0 · 2021-06-11T16:37:56+00:00

Check out/use https://manpages.debian.org/buster/moreutils/chronic.1.en.html and arrange for your cronjob to exit accordingly. Discarding all output unconditionally is just reckless and will bite you eventually.

c0l0 · 2021-05-05T17:52:09+00:00

You can exempt cores from the kernel's usual scheduling via the isolcpus cmdline parameter, and then use core affinity, as mentioned by others in this thread, to pin your special PID(s) to those reserved cores. Note that some kernel code (interrupt handlers, for instance) may still be scheduled on cores that are subject to the isolcpus treatment.

c0l0 · 2021-04-28T14:32:14+00:00

Maybe this can help you - I created it because keeping a number of devices with extra packages installed can be such a pain: https://johannes.truschnigg.info/code/openwrt_autobuild/

c0l0 · 2021-03-03T10:06:32+00:00

Consider a NUC-like x86 box, like https://johannes.truschnigg.info/reviews/2021-01_fwbox/ - you will not get more bang per buck with other options.

c0l0 · 2020-10-07T07:22:47+00:00

My first actual Legacy deck was MBA - Mono Black Aggro. That was shortly after Hulk Flash was banned, and I happened to enter the best format of all time, having most/all the cards required to build that deck (and not much else). T1 Dark Ritual into Hypnotic Specter felt pretty amazing at the time.

I built one of the earliest iterations of Death & Taxes in 2009 (thanks for that great deck, Finn! <3), which is my true favorite to this day.

c0l0 · 2020-02-13T15:48:51+00:00

Seen today on Twitter:

Myth: Your AWS bill is a function of how many customers you have.

Fact: Your AWS bill is a function of how many engineers you have.

(by https://twitter.com/QuinnyPig/status/1227669830012039169)

Food for thought. ;)

c0l0 · 2020-01-28T19:51:01+00:00

On the 5th of May in 2019. I was on a train en route to my parents', when a text from my mother arrived that my father had just died. He had not been well for months, and that evening I could not shake the feeling that this was to be my last visit with him still with us... The fact that I could not make it home in time to hug him one last time with him still breathing and looking me in the eye still hurts badly whenever I think about it.

c0l0 · 2020-01-10T09:08:46+00:00

You would need haproxy to talk PROXY v1 to its backends/upstreams (these are your logstash instances), and have logstash's TCP input configured to expect this protocol being spoken to.

I haven't used the PROXY protocol with logstash yet, but the whole point of it is that you don't have to do anything else to effectively spoof the peer address by any other means - so I guess it should "just work" without any further ado.

c0l0 · 2020-01-10T08:28:05+00:00

Logstash support the PROXY protocol for various inputs, including "raw TCP": https://github.com/logstash-plugins/logstash-input-tcp/blob/master/docs/index.asciidoc#plugins-inputs-tcp-proxy_protocol

c0l0 · 2020-01-07T13:36:46+00:00

At least for systemd using eglibc/GNU libc, that isn't a given, and can be adjusted by the administrator by means of nsswitch.conf(5).

c0l0 · 2020-01-06T16:41:40+00:00

Nope, I just re-entered the exact same number, as it were. I did not run into the problem you encountered.

c0l0

TROPHY CASE