• 4 Posts
  • 66 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • Thanks Sagifurious, this person knows his trucks. But provides little to the conversation with their straw man fallacies, and troll like rebuttals.

    A great example of a blockable account.

    Look at this users profile, review their post contribution. Click the three dots to open the actions, and select block this user.

    Blocking doesn’t happen instantly because of cached data in your browser, but it is very effective.

    And that’s how we keep this space enjoyable to use.







  • I used awk to migrate users from one system to another. I created template scripts for setting up the user in the new system, I dumped the data from the old system, then used awk to process the dump and create scripts for each user in the new system. That was a fun project.



  • Yeah, I’m sorry to say that is a result of good marketing. I work at a university and we have experience with a good number of XPS laptops.

    We saw at least a 60% problem rate, and Dell’s support was dog slow. Batteries being the weak spot. Because it’s thin it is more fragile, we saw a number of broken screens, and keyboards. One survived a Gatorade spill, but another failed after a water spill. Go figure

    A three year warranty helped, but we were out of a laptop for months at a time, more than once on the same laptop.






  • Yes that’s the right way to block root login. An added filter you can use the ‘match’ config expression to filter logins even further.

    If you’re on the open network, your connection will be heavily hit with login attempts. That is normal. But using another service like Fail2Ban will stop repeated hits to your host.

    Ssh listens on port 22, as soon as a connection is made the host moves the connection to another port to free up 22 for other new connections. Btw: I wasn’t thinking clearly here. Out going connections won’t be using port 22, but the listening incoming port is always 22.