• 2 Posts
  • 208 Comments
Joined 3 years ago
cake
Cake day: June 7th, 2023

help-circle

  • This is it exactly. I made a hard cut with Reddit, but I’ll admit to missing the sysadmin subreddit. The place was full of very smart, helpful people and also cranky. The PowerShell subreddit was another great resource. I haven’t been willing to go back, but those sorts of communities only exist when you hit a certain mass of people on a platform.




  • Yes, and you can probably get better performance with different block sizes. This is just what I used to fix drives as it was fast enough and I couldn’t be arsed to do any real testing to find the right speed. Also, my stash of drives was no where near homogeneous, so the right size for one type of drive may not have worked for a different type of drive. I also used the 4MB block size when imaging drives to have an ok-ish speed while not losing too much data if there were read errors.





  • You could try using Autopsy to look for files on the drive. Autopsy is a forensic analysis toolkit, which is normally used to extract evidence from disk images or the like. But, you can add local drives as data sources and that should let you browse the slack space of the filesystem for lost files. This video (not mine, just a good enough reference) should help you get started. It’s certainly not as simple as the photorec method, but it tends to be more comprehensive.


  • relevant XKCD.

    That aside, I think the book I am Legend handled the initial outbreak in one of the best ways to actually make it stick. There was a worldwide dust storm which infected everyone. A large fraction of the population succumbed to the infection and died or became “zombies” (more vampires really, they retained a lot of intelligence. The Will Smith movie really fucked the plot.). It’s one of the few ways to get past the problem of the various world militaries just curb stomping the initial zombie outbreak. Sure, there would be some confusion and some losses while people figured out the various rules for the zombies, but WWI is kinda instructive here. Massed charges into machine gun fire didn’t go well for the soldiers in the charge. As another historic example, the Banzai Charge employed by Imperial Japanese soldiers during WWII was not only suicidal by nature, it was worthless against a well armed, organized line. Yes, zombies might be more resilient and less prone to morale breaking, but they’d still be mowed down en masse. And that’s before we consider air strikes, artillery and napalm. A combined arms assault against a mass of zombies wouldn’t be pretty. Especially considering that zombies wouldn’t have the strategic thinking to attack supply lines and depots.

    Zombie outbreaks are fun in media. I’m currently playing 7 Days to Die, again. And I’m having lots of fun. I also don’t spend too much time thinking about what the backstory might be. There’s zombies, and it’s my job to survive. That’s all the setup I need to enjoy the catharsis of zombie heads exploding in gore.




  • I can think of a couple of reasons off the top of my head.

    You don’t say, but I assume you are working on-site with your work system. So, the first consideration would be a firewall at your work’s network perimeter. A common security practice is to block outbound connections on unusual ports. This usually means anything not 80/tcp or 443/tcp. Other ports will be allowed on an exception basis. For example, developers may be allowed to access 22/tcp outbound, though that may also be limited to only specific remote IP addresses.

    You may also have some sort of proxy and/or Cloud Access Security Broker (CASB) software running on your work system. This setup would be used to inspect the network connections your work system is making and allow/block based on various policy settings. For example, a CASB might be configured to look at a domain reputation service and block connections to any domain whose reputation is consider suspect or malicious. Domains may also be blocked based on things like age, or category. For this type of block, the port used won’t matter. It will just be “domain something.tld looks sketchy, so block all the things”. With “sketchy” being defined by the company in it’s various access policies.

    A last reason could be application control. If the services you are trying to connect to rely on a local program running on your work system, it’s possible that the system is set to prevent unknown applications from running. This setup is less common, but it growing in popularity (it just sucks big old donkey balls to get setup and maintain). The idea being that only known and trusted applications are allowed to run on the system, and everything else is blocked by default. This looks like an application just crashing to the end user (you), but it provides a pretty nice layer of protection for the network defenders.

    Messing with the local pc is of course forbidden.

    Ya, that’s pretty normal. If you have something you really need to use, talk with your network security team. Most of us network defenders are pretty reasonable people who just want to keep the network safe, without impacting the business. That said, I suspect you’re going to run into issues with what you are trying to run. Something like SyncThing or some cloud based storage is really useful for businesses. But, businesses aren’t going to be so keen to have you backing their data up to your home server. Sure, that might not be your intention, but this is now another possible path for data to leave the network which they need to keep an eye on. All because you want to store your personal data on your work system. That’s not going to go over well. Even worse, you’re probably going to be somewhat resistant when they ask you to start feeding your server’s logs into the businesses log repository. Since this is what they would need to prove that you aren’t sending business data to it. It’s just a bad idea all around.

    I’d suspect Paperless is going to run into similar issues. It’s a pretty obvious way for you to steal company data. Sure, this is probably not your intention, but the network defenders have to consider that possibility. Again, they are likely to outright deny it. Though if you and enough folks at your company want to use something like this, talk with your IT teams, it might be possible to get an instance hosted by the business for business use. There is no guarantee, but if it’s a useful productivity package, maybe you will have a really positive project under your belt to talk about.

    FreshRSS you might be able to get going. Instead of segregating services by port, stand up something like NGinx on port 443 and configure it as a reverse proxy. Use host headers to separate services such that you have sync.yourdomain.tld mapped to your SyncThing instance, office.yourdomain.tld mapped to your paperless instance and rss.yourdomain.tld mapped to FreshRSS. This gets you around issues with port blocking and makes managing TLS certificates easier. You can have a single cert sitting in front of all your services, rather than needing to configure TLS for each service individually.





  • I run Pi-Hole in a docker container on my server. I never saw the point in having a dedicated bit of hardware for it.
    That said, I don’t understand how people use the internet without one. The times I have had to travel for work, trying to do anything on the internet reminded me of the bad old days of the '90s with pop-ups and flashing banners enticing me to punch the monkey. It’s just sad to see one of the greatest communications platforms we have ever created reduced to a fire-hose of ads.



  • This sort of thing is just awesome. I really wish there was more information on repairing these sorts of electronics out there and accessible to non-electricians. I do get that sometimes it really does take someone with a lot of specialized knowledge and training to troubleshoot and fix things like this. But, even basic, “look for X and try Y” type stuff for us plebes to make the attempt. Sure, we’ll fail as often as we succeed, but even that would save a lot of electronics from the scrapheap.