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

help-circle
  • I have two:

    1. Waves glowing with bioluminescence during a red tide. We didn’t know it would be going on and were just camping by the beach. Walking on it at night, we all saw the waves glowing and weren’t sure it was real. As we got closer, our footsteps in the area where the waves were rolling in and out were glowing as well. Just surreal.
    2. A house blowing up. Guy opened a natural gas valve in the house and touched it off. Insulation shot way up in the air and the house itself bowed outwards in basically every direction, stayed standing though. At least until it burned down.


  • While I don’t know the specific post you are referring to, Malware exists for Linux. Here’s a great overview from last year. If someone wants to argue, “oh it’s from a security company trying to sell a product” then let me point you at the Malware Bazaar and specifically the malware tagged elf. Those are real samples of real malware in the Linux specific ELF executable binary format (warning: yes it’s real malware, don’t run anything from this site). On the upshot, most seem to be Linux variants of the Mirai botnet. Not something you want running, but not quite as bad as ransomware. But, dig a bit and there are other threats. Linux malware exists, it has for a long time and it’s getting more prevalent as more stuff (especially servers) run on Linux.

    While Linux is far more secure than Windows by design, it’s not malware proof. It is harder for malware to move from user space into root (usually), but that’s often not needed for the activities malware gets up to today. Ransomware, crypto miners and info stealers will all happily execute in user-land. And for most people, this is where their important stuff lives. Linux’s days of living in “security through obscurity” are over. Attackers are looking at Linux now and starting to go after it.

    All that said, is it worth having a bloated A/V engine doing full on-access scanning? That depends on how you view the risk. Many of the drive-by type attacks (e.g. ClickFix, fake tech-support scams) all heavily target Windows and would fail on a Linux system. The malware and backdoors that come bundled with pirated software are likely to fail on a Linux system, though I’ll admit to not having tested that sort of thing with Wine/Proton installed. For those use cases, I’d suggest not downloading pirated software. Or, if you absolutely are going to, run those file through ClamAV at minimum.

    Personally, I don’t feel the need to run anything as heavy as on-access file scanning or anything to keep trawling memory for signatures on my home systems. Keeping software up to date and limiting what I download, install and run is enough to manage my risk. I do have ClamAV installed to let me do a quick, manual scan of anything I do download. But, I wouldn’t go so far as to buy A/V product. Most of the engines out there for Linux are crap anyway.

    Professionally, I am one of the voices who pushed for A/V (really EDR) on the Linux systems in my work environment. My organization has a notable Linux footprint and we’ve seen attackers move to Linux based systems specifically because they are less likely to be well monitored. In a work environment, we have less control over how the systems get (ab)used and have a higher need for telemetry and investigation.


  • One of the things to look at is the interest rate you would be paying for either loan and how that would effect the total cost of the loan. Also, there is the question of the utility of any money spent up front. For example, if using a loan on the existing house would result in no up front costs and a 5% interest rate over 30 years, and the standard mortgage would cost $20,000 and have an interest rate of 8%, you’re almost certainly better to use the existing house as backing and throw that same $20K in a long term interest bearing investment (e.g. government bonds). All this assuming you plan to hold onto the second property long term.

    Compounding interest is a fantastic tool and a fearful master. If you can make it work for you, then do it. If you are facing the possibility of paying it, you almost always want to lower it as much as possible.




  • 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.







  • 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.



  • The big ones for me were a frequent, sudden, urgent need to pee and getting up multiple times a night to pee. I also drank a copious amount of water. Like, the whole “eight glasses a day” thing which used to be popular was confusing to me, as I’d drink that much in the first couple hours of the day. I finally went in to the doctor and got a blood test and my A1Cs were well over the “welcome to Diabetes Land” number. With diet, exercise and drugs I’m well controlled now and caught it early enough that I still have good feeling in my feet. Given my family history, and all the shit I ate in my younger days, it’s not really a surprise. I just have to be more careful now, but I have discovered an enjoyment of climbing because of it.

    Really, if you have any family history of diabetes, start visiting your doctor on an annual basis and getting a blood test. It’s simple, and catching it earlier is good for preventing problems with neuropathy in your feet.




  • sylver_dragon@lemmy.worldtoAsklemmy@lemmy.mlDoes this really work?
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    4 months ago

    For the ones they own or have a contract with, probably. However, there are two problems with that.

    1. It will do fuck all for the AI models which are just scraping the internet and which have no contractual agreements with the blog (e.g. all the big ones).
    2. It’s a fixing a problem the blog hosting platform created. They likely have a data sharing agreement with some organizations to make the scraping easy for those organizations (e.g. direct content database access). So, they are like the mob, offering you “protection” so long as you pay them not to break your shit.

  • Location: ~87% of respondents are from Canada

    As others mentioned, this would be an interesting data point to validate. I’m not familiar with the server side of Lemmy, but does the server provide any logs which could be used with GeoIP to get a sense of the relative number of connections from different countries? While there is likely to be some misreporting due to VPN usage and the like, it’s likely to be a low enough number of connections to be ignored as “noise” in the data. Depending on the VPNs in question, it may also be possible to run down many of the IP addresses which are VPNs in the connections logs and report “VPN user” as a distinct category. This would also be interesting to see broken out by instance (e.g. what countries are hitting lemmy.world versus lemmy.ml versus lemmy.ca etc.).

    All that said, thank you for sharing. These sorts of exercises can be interesting to understand what a population looks like.


  • If the goal is stability, I would have likely started with an immutable OS. This creates certain assurances for the base OS to be in a known good state.
    With that base, I’d tend towards:
    Flatpak > Container > AppImage

    My reasoning for this being:

    1. Installing software should not effect the base OS (nor can it with an immutable OS). Changes to the base OS and system libraries are a major source of instability and dependency hell. So, everything should be self contained.
    2. Installing one software package should not effect another software package. This is basically pushing software towards being immutable as well. The install of Software Package 1, should have no way to bork Software Package 2. Hence the need for isolating those packages as flatpaks, AppImages or containers.
    3. Software should be updated (even on Linux, install your fucking updates). This is why I have Flatpak at the top of the list, it has a built in mechanism for updating. Container images can be made to update reasonably automatically, but have risks. By using something like docker-compose and having services tied to the “:latest” tag, images would auto-update. However, its possible to have stacks where a breaking change is made in one service before another service is able to deal with it. So, I tend to tag things to specific versions and update those manually. Finally, while I really like AppImages, updating them is 100% manual.

    This leaves the question of apt packages or doing installs via make. And the answer is: don’t do that. If there is not a flatpak, appimage, or pre-made container, make your own container. Docker files are really simple. Sure, they can get super complex and do some amazing stuff. You don’t need that for a single software package. Make simple, reasonable choices and keep all the craziness of that software package walled off from everything else.