brainw0rms [they/them]

  • 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: August 31st, 2023

help-circle


  • clearly, freedom and easy access to information has nothing to do with the issue at hand, which is enforcement of copyright law.

    so long as they don’t plan on violating russian or chinese (or whatever country’s) copyrights (and other applicable laws), why should those countries care at all? archive.org is hosting material copyrighted in a country where said copyright can be enforced (the US). it’s really that simple. while china or russia may not be the most suitable option (I imagine they also host plenty of content that those countries would find to be inflammatory or illegal but not for copyright reasons), they’d be an improvement overall.



  • At the risk of sounding contrarian/lame, you should probably not be doing any of this especially if you don’t own the hardware you’re using (as mentioned by another commenter).

    You don’t specify if this is university or middle/high school, but either way you are not entitled to and should not expect any privacy on a network you don’t control. Even if you are able to set up a VPN to mask your internet activity, your school’s network administrators almost certainly can tell that you are using a VPN, which itself sounds like it would be a violation of your school’s network policy and will most likely land you in trouble. Indeed, your repeated attempts to access blocked sites have likely already raised some flags.

    Even the workarounds that others here have mentioned (like routing VPN traffic over port 443) are inadequate for a network that is being actively monitored. Believe me, it is very easy to tell when someone is connecting to a VPN this way.

    I would quit while you’re ahead until you can afford your own hardware/internet connection, and then maybe worry about any notion of privacy. Use your school’s internet for what it was intended.









  • I guess it depends on your threat model, but if you’re dealing with mission critical proprietary code then it should really never be leaving your own companies infrastructure, imo. If for some reason it is necessary to use enterprise cloud hosting, established actors like Github, Gitlab or even Bitbucket still seem like the obvious choice.

    The issue is this “Gitea Ltd.” company (or is it “CommitGo Inc.” now? honestly pretty confusing…) which appears to have been created with the singular purpose of monetizing Gitea, appeared out of thin air with no input from the community that actually develops Gitea. They’re basically saying “you can’t trust those other smelly hosts that have existed for years and have contracts with tons of huge companies, but you should definitely trust us with your stuff bro!”. Seems off to me.






  • When the source of a crack/patch isn’t trusted, I’d do like you said and install it in a VM, then compare the patched files with their unpatched copies using diffing software (Beyond Compare’s hex compare feature is useful for this). If there are a huge amount of changes, like completely different size and content, or it is protected with a packer (typically will be a several MB larger), I would definitely steer clear of it. If it’s just a few changed bytes (and maybe the digital signature overlay is stripped off), then it’s most likely safe and you can just copy the patched files out of the VM and overwrite your main install.

    Edit: Also, always prefer official installers directly from the developer’s site if they are available; “pre-cracked” installers are always a red flag to me.