This requires people to play by the rules. I’ve yet to play a game that actually follows the written rules.
This is a secondary account that sees the most usage. My first account is listed below. The main will have a list of all the accounts that I use.
Personal website:
This requires people to play by the rules. I’ve yet to play a game that actually follows the written rules.
I think the driver is up to date because I’m on the latest 6.8 kernel. Firmware, TP-Link offers none for their junk.
Is there a way I can check if it’s a driver or a firmware issue? I took a look at the driver code to TBF I’m not enough of an expert to understand how it actually talks to the device.
My network adapters send corrupted packets unless I disable RX/TX offloading with ethtool
(this feature is turned on by default). Is this normal? Should I be able to do checksum and TCP session offloading?
Like I needed another reason with this guy.
It’s astounding how one person manages to be so deeply unlikable.
It is highly unlikely that you have malware sophisticated enough to do something like compromise installation media (already exceedingly rare) yet not sophisticated enough to bypass secure boot.
The purpose of secure boot is to verify that the boot loader and kernel are approved by the manufacturer (or friends of such). There are certainly ways to inject software into a system that doesn’t reside in those locations. It just makes boot sector viruses and kernel mode rootkits slightly more technically challenging to write when you can’t simply modify those parts of the operating system directly. If malware gets root on your installation it’s game over whether or not you have secure boot enabled. Much of the software on a computer is none of those things protected by secure boot.
Plus, take another wager: most systems today ship with secure boot enabled. If you were a malware author, would you still be writing malware that needs secure boot turned off to run? Of course not! You would focus on the most common system you can to maximize impact. Thus, boot sector viruses are mostly lost to time. Malware authors moved on.
Overall, it’s a pretty inconsequential feature born of good intentions but practically speaking malware still exists in spite of it. It’s unlikely to matter to any malware you would find in the wild today. Secure boot keys get leaked. You can still get malware in your applications. Some malware even brings its own vulnerable drivers to punch into the kernel anyway and laugh in the face of your secure boot mitigation. The only thing secure boot can actually do when it works is to ensure that on the disk the boot loader and kernel look legit. I guess it kind of helps in theory.
This is good advice in general. Think of it like penetration testing. You really should verify what you can actually access remotely on a device and not assume you have any level of protection until you’ve tried it.
Log files can also contain signs of attack like password guessing. You should review these on a regular basis.
I was hoping for FreeBSD.
This is awesome! I didn’t know this was a thing.
It’s beautiful.
That’s a tough nut to crack. Even as a video game platform, they don’t write most of the software that they sell today. They would need to find some way to convince developers to write software for something that’s not the platform nearly all users are running.
I’m not sure that Microsoft ever did halt going down that path. My wife recently bought a PC that came locked down by default and required some fiddling to allow running unsigned apps. This was Windows 10, not sure about 11.
I think it could be more that broad compatibility with everything is their main selling point, and by doing so they were undermining their own ecosystem.
However, this is mere speculation on my part.
Valve is a Titan doing incredible work for the open source community and making money while doing so.
Successful open source software business model at work. Way to go.
But we continued to use the substances anyway because it was cost-effective.
Page break.
Chapter 6: The First Mutant
Loads of complex code exposed to an assumed trusted network is the model of printers. They’re going to be full of security issues.
This stuff should be sandboxed and then never, ever exposed to the Internet.
Entirely personal recommendation, take it or leave it: I’ve seen and attacked enough of this codebase to remove any CUPS service, binary and library from any of my systems and never again use a UNIX system to print. I’m also removing every zeroconf / avahi / bonjour listener. You might consider doing the same.
Great advice. It would appear these developers don’t take security seriously.
The most reliable way I know is to seek documentation for the board. It’s up there with PCI lanes in that the board designer will know what has been configured to work with that physical connector. This kind of info is definitely part of your motherboard documentation.
I’m not familiar with dmidecode
so unfortunately I cannot comment on that.
Looks like one to me. Remember that M.2 is a form factor. You can have an M.2 slot that does not support SSD storage for example. I have one that is only intended to work with wifi adapters.
Based on the wifi designation on the board I’ll bet it only works with wifi cards.
M.2 is a form-factor. It talks about the shape only, it says nothing about what the device you are using can do. Many boards have restrictions on supported devices for the physical slot.
It’s almost like they know they’re doing something morally reprehensible.
I appreciate the positive and constructive outlook and for that I value your contribution. Your wife seems like she’s being the change we want to see in less-than-stellar HR departments, but I think to consider the benefits of HR from the employee POV just isn’t safe unless you’re absolutely certain where the priorities lie for your local HR team.
The phrase “cops of the company” is an even more accurate term in the sense that while some cops may actually believe in serving their community, many perhaps most do not, and trusting one is hazardous to your health. A good HR department does care about employees and the company, but how does an employee know that they have one of the good ones? I feel like this is something you don’t really know until you lean upon it such as when disagreements occur, and then either the rickety post will hold or you fall flat on your face. Me? I’m not leaning on that rickey post any more than I would willingly speak to a “friendly” neighborhood police officer. Your job isn’t a place for trust. It’s business. That HR person could be your wife, or they could be the kind to shoot first and ask questions later.
I don’t have a problem with my local PD nor do I have any issues with my HR, but I definitely don’t want a visit from either.
True, but you gotta give Linux some slack. All of this driver work is reverse engineered. It would be so much easier if the vendor just published information about their hardware.