• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: August 19th, 2023

help-circle

  • Adobe used to house all the licensing mechanisms in a single file named amtlib.dll. The people who cracked it just nulled out the function. And since it was the same for every piece of software, just repeat the null process for each one. Bam, the entire suite for free.

    When Adobe switched from CS to CC subscription, it was cracked in 24 hours. Largely because they didn’t change much.

    Adobe then axed the crippling DLL file and baked the mechanism right into the executable. A patcher tool was released that could crack each one. The upside is you could install and keep them updated from the CC Desktop and just run the patcher each time. Sometimes you had to wait for an update to the patcher. So before you clicked “update” you had to double check to make sure it worked.

    To stop the free trial abuse (which is how people installed anyway) Adobe started requiring billing information during setup before you even get to downloads.

    Later on, Adobe prevented users from updating apps if there wasn’t an active subscription.

    The patcher eventually stopped working because it was abandoned (this around 2019 when I gave up using it because Resolve and Affinity were more affordable and met my needs.) Months later someone else picked up the patcher development. There’s also pre-cracked versions you can download and install.

    I’ve not touched Adobe since and find Resolve to be significantly more stable and at $300, much more affordable. The Affinity Photo and Designer apps are great and affordable too at $170 for the bundle.










  • Your entire statement here stems from not knowing what you’re talking about. That’s OK. I’ll provide some insight.

    Secure Boot is a security feature of UEFI that only allows trusted, cryptographically signed operating systems to boot. The nature of this prevents rootkits. Software that runs before the OS and injects itself. BIOS has many hard limitations and disadvantages over the modern standard that is UEFI. Your comparison going from 32 to 64 bit architecture is quite fitting. It’s not that different. There are many hard limitations and disadvantages to 32 bit. It’s unfit for today’s standards due to lack of features and security. All aspects of technology have to move forward.








  • Once you agree to letting friends and family access your hosted services, you become the tech support for any problems. Whether that be your fault, user error, etc. You should absolutely limit who you give access to. In my case, only three people can and that’s immediate family. No friends, no extended family. I don’t wanna deal with all that mess when I deal with it at work. Don’t over extend yourself by being nice.

    Using Cloudflare is against the ToS when used for services like Jellyfin. Your account can be limited, closed, or find yourself getting a several hundred dollar bill for data usage because you’ve breached the terms of service. Additionally, streaming content on free accounts incurs higher latency which I’ve confirmed myself Argo smart routing massively reduces. https://github.com/jellyfin/jellyfin/issues/9295 - Don’t abuse what’s free or you may lose it.

    Google shouldn’t be indexing your domains anyway. If it’s flagged your domain, it’s been indexed and scanned. Alternatively, it could indicate you have a weak point somewhere on your server and you’ve been breached. Google’s scan picked up whatever it was. Though I doubt this is the case and just a false positive. Double check your robots.txt files and disallow everything. Most index bots respect this. You can use a community sourced bot blocker. https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker

    I’ve been running my own self hosted services for almost a decade. Though I have a background in IT directly doing this kind of stuff daily at work. As long as you have a strong firewall, modern TLS, relevant security headers, automatic tools like fail2ban, and have a strong grasp on permissions, you should be fine. Before I moved everything to non-root docker, it was given its own service user and SELinux policy. Using direct DNS isn’t so much of a problem. You shouldn’t have any issues. Feel free to reach out if you have any questions.