• 1 Post
  • 285 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle
  • My personal preference is to use FOSS whenever it’s practical. For home use, I’ve switched to FOSS for the vast majority of my computing needs. I run Linux on both my server and desktop. Most of the software on my server is FOSS, with the one exception being a container using the Splunk free license. My desktop is running Linux, and I use LibreOffice for documents and the like. I do run Visual Studio Code, which is technically Open Source, though I would not put it past Microsoft to do a rug-pull on that eventually. And I have an extensive library of games with Steam, basically nothing of which is Open Source.

    I have reached a point, financially, that piracy is not morally defensible. And I’m not willing to get into the mire of if, or where such a line would be. I believe that creators should be rewarded for their work. Though, I also agree that the limits on copyright are way out of whack with the changes Disney has purchased through the years. So, piracy as a moral question is a murky subject, with no clear answers to me. But, the end result is that I buy games, movies or TV shows. For other software, I usually look to FOSS projects (e.g. Gimp vs Photoshop, FreeCAD/OpenSCAD vs Autodesk), free licenses (e.g. Splunk) or just do without. For TV Shows/Movies, if it’s not on one of the streaming services I subscribe to, I may buy it via a digital service; or, I do without.


  • No, if you open a terminal and run:
    sudo dmesg

    You should get a long output which is the kernel log. Assuming the crash happened recently, there may be something in the last few lines (bottom of the output) which could indicate why the process died (or was killed). Keep in mind that this is a running log; so, if it’s been a while since the crash, the entries for it may be higher up in the log. It’s often best (if you can) to trigger the problem then immediately go run the sudo dmesg command and look at the output. With luck, there will be useful logs. If not, you may need to look elsewhere.



  • The person who authored the cheat(s) the other person is using. Because clearly, if I lost they must be cheating. /s

    For many games, I’d argue that you are to blame for your loss. Assuming the game is based purely on skill, then your ability to execute said skills is the only factor which matters. Consider something like Chess, where the game is solved and one’s ability to win is really down to your ability to memorize board positions and recognize the optimal move. If you lose, it’s likely because you failed to pick the optimal path.

    This is mitigated, to a greater or lesser extent in games where chance plays some role. It’s entirely possible to chose an optimal path, but have RNGesus decide that you get to lose today. Some games provide some ability to manage the risks created by randomness, but you often have some reliance on “luck”. Obviously, the more luck dependent a game is, the less control you have over winning/losing.

    And then there is the issue of other players who can affect the outcome. If you play a game where there are more than two players, the other players may be able to change the course of the game enough that, no matter how well optimized your choices, you cannot win. This leads to the classic “kingmaker” problem in board games. It may be that someone who is themselves unable to win is in a position to directly effect the outcome of the game in such a way as to make another player win or lose. So, maybe you played a very good game, but the kingmaker decides that you lose.

    Ultimately, the answer to the original question is, “it depends”. And there are a lot of factors one must look at to come to an answer. And that answer is unlikely to be whole one thing or the other.


  • It’s a matter of circumstance. Authoritarianism is only useful in situations where time pressures make the slow, deliberate decisions of democracy unworkable. Combat is a good example of this. When the shells are raining down around you, there isn’t really time to hold a vote on how to proceed. So, in such situations there is usually a chain of command which is given authoritarian control. Other emergent situations will also often require similar levels of top-down control. The person in charge may not make the best or fairest decisions in the heat of the moment. But, inaction will almost certainly be a worse choice.

    The other side of this is, when the situation isn’t emergent, a democratic (well, really semi-democratic, but I’m going to use “democratic”) system is likely the best choice. And those democratic systems would be wise to prepare for the emergent situations by identifying and designating the people who will be handed dictatorial control when the fecal matter hits the air circulator. And the system for identifying when the emergency has ended, how dictatorial power is unwound and how the performance of the person handed that power is to be judged.

    The reason I hedged with “semi-democratic” is that a truly democratic system can have issues too. The classic “tyranny of the majority” problem. As any majority could override the rights of a minority in a truly horrible fashion. The solution being things like constitutional democracies, where the power of the majority is limited in specific ways (e.g. unrevokable rights).


  • No, but the country has problems. It’s always had problems. Even with all of the economic hardship and political strife we have today, most people are safer, healthier and have better prospects today than they have had in most of US history. It’s by no means perfect and we have a lot of work to do. But, giving up and checking out has never improved anything. It also doesn’t help that we have a steady drip-drip-drip of negative information fed to us by our phones and algorithms. We are also facing one of the largest Constitutional Crises in US History, with the President pushing the boundaries of his Constitutional powers. Even if nothing breaks, we are likely to see many changes from all this. Hopefully, those changes result in better guardrails on the Presidency. And maybe even a repudiation of the Roberts Supreme Court. But, such a future is hard to see when we are in the middle of the storm.

    I even have hope for the slight voting majority which put Trump back in power. It’s easy to dismiss those folks as a bunch of <insert invective terms here>. And some of them almost certainly fit those descriptions. However, there are a lot of them which are just scared and confused by the FUD sandwich being fed to them by the 24-hour news cycle, social media algorithms and politicians looking for easy votes. It’s going to be hard work to pull them back off the brink. And if you’re not up to that work, I understand. It’s hard to want to put in the effort for folks who seem so far gone. I’ve spent a lot of hours arguing with folks with whom I disagree wholeheartedly. It’s tiring and I can only take so much before I decide it’s time to move on for a while. But, I would rather keep up the argument than let the country slide into full blown autocracy.

    So ya, I have hope. It’s a grim hope and one which recognizes that we could lose. But, giving up now feels premature.




  • At most organizations I have worked at (both IT and cybersecurity), decryption keys will be centrally managed. With some technologies (e.g. Bitlocker), it’s possible to have multiple passwords which can be used to decrypt the drive, and it could be possible for the user to have one only they know. However, there isn’t a logging mechanism to verify which password was used to unlock the drive, leaving the issue of non-repudiation. This could probably be fixed by having some sort of system which logs which user unlocked the drive, but that would be a very hard thing to do securely. Any such log would need to be in a space the bootloader can reach and write to, and now that location needs to be secured in a way which prevents a malicious actor from modifying the log. At that point, we’re quickly arriving at having TPM and we might as well go whole hog and just do TPM and secure boot. Which is a great bit of technology; but, now only proves that the system hasn’t been tampered with.

    As a tangent, the reason most organizations centrally manage drive encryption keys is the need to unlock the drive, in the event the user is no longer able to. If you win the lottery, turn your laptop in and run off to parts unknown, the organization may want to unlock the laptop to recover anything you were working on. So, they need access to the decryption key.

    Ultimately the problem is that the encryption password and your user account password are solving different security problems and there isn’t a lot of good overlap between the two.



  • If the device is encrypted and single-user there is no good reason to require further login after the first.

    The reason is non-repudation. Ignoring the fact that the drive’s encryption should have been handled by TPM and not be bothering the user, the drive encryption password does not establish who is using the laptop, only that they know the unlock password. Unfortunately, those unlock password are usually centrally assigned and managed, which means that they are not something that only the user knows. Also, it doesn’t have a good second factor. If the laptop is stolen, there is nothing keeping an attacker out, if they know the password. Their account, on the other hand, should have a password only the user knows. Yes, central IT can reset the password, but this creates logs which show the reset and can be used to prove that the password was reset, and who reset it. And the user’s password can be backed up with a second factor. So, a stolen laptop isn’t an easy on-ramp to the organization’s network.

    As for logins after that, it gets harder to justify. OS, email and most web portal logins should be handled via SSO. For most users, this should mean that their drive gets decrypted via TPM, they type their password into the OS login prompt, deal with 2FA and that’s it. For users with admin access to stuff, there will be a separate login step when they need to elevate permissions, but that should largely be limited to IT staff and developers. For the original poster, it sounds like their organization’s IT is being run on a shoestring by someone who either doesn’t know or isn’t allowed to do it well.




  • I just want to stop feeling imposter syndrome. I’m nearing 50, at work everyone seems to think I am one of the most competent people they have met in my field. I get the hard problems, get dragged into lots of projects as a technical consultant. And yet internally, I forever feel like I’m “faking it until I make it”. Like I’m one question away from being unmasked as a kid playing at knowing what I am doing. Consciously, I know I am not and that I’m actually pretty good at this. But, every time I get a meeting request from my boss, I still get a moment of panic thinking, “this is it, I’m about to be fired”. That’s what I want from “growing up”, to just not feel that feeling constantly.

    Also, I want to be independently wealthy when I grow up. Fuck this whole work thing.



  • So much this. I was having a discussion with one religious zealot and he kept insisting, “he’s your god too” when I referred to yahweh as “his god”. No asshole, I don’t subscribe to your fairy tales. Though, in a nod to keeping the discussion civil, I limited my responses, to “no, I don’t subscribe to your beliefs.” Getting upset, yelling or insulting only plays to their ability to project victim-hood. So, it’s important to stay calm and keep the conversation rational and focused on the failures of their explanations. You will never convince the delusional to give up their delusions, but you can convince the other people around, who aren’t fully delusional, to question the delusions.



  • Step one: Document, Document, Document.
    Step Two: Did we cover documentation yet?
    Step Three: Complain, with documentation, to the apartment management.
    Step Four: Document.

    Recordings such as video and audio are useful. Just keeping a log of all such interactions can help as well. But, you want to have the documentation to prove your side of things. If things go really sideways and you end up in court, the judge won’t give a fuck about what you say, only what you can prove. Be ready to prove your claims. As we say in the DFIR world, “logs or it didn’t happen”. Then, start complaining to management. And document (keep a written log, you probably won’t be able to record) your interactions with management. All logs should include date, time, who you spoke with, what you spoke about and any actions which management said they would take or actions you said you would take. If it’s an option, keep your communications with management in email. Both the sending and received emails will be timestamped and the headers will provide a reasonable record showing that the emails were to or from management controlled email servers and addresses. And they log what was talked about quite nicely.

    Ultimately, the goal is to move this from being your problem to management’s problem. And it’s possible that your problem neighbor is also someone else’s problem. If management has three tenants all complaining about the same neighbor, they have more impetus to take action against the problem. Of course, this assumes a neutral management, which can be an open question. But, this is likely the least costly way to resolve the issue.


  • Not humming, but I do make noise intentionally. I’m a big guy and understand that I could be threatening to women in the wrong circumstance. I also walk fairly quietly just as a matter of the way I walk; so, I’ve scared folks on more than one occasion by “sneaking” up on them unintentionally. So, if I think I am doing that, I’ll land a few footfalls hard and flat to make my foot slap the ground and alert the person of my presence before I get too close. I also try to give space to strangers while walking. Things like moving to the other side of the sidewalk/street, slowing down or speeding up to pass. Basically, trying to not look like I’m stalking them.