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.
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:
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.
I just want to say thank you for your take. I’m not smart enough to intelligently discuss these issues, but it pleases me greatly to see great minds thinking hard about Lemmy.
👏👏 nicely done! Bravo!
My IP is in this photo and I don’t like it.
The number of comments is inversely proportional to the size of the pull request.
It would have to be written by sane people.
Surprised not to see meta-classes or package management in the meme.
EDIT: clarification
You don’t even need to scrape Wikipedia. Simply download all of Wikipedia text only and you could match on articles. It’s only like 20 GB or even less for certain database dumps.
RIP.
Don’t recommend using that register to store your variables.
Try assembly language! You have registers, and they are named for you with highly memorable names like R17.
This is certainly an interesting feature, though my one use case has become much less relevant now that systems boot so quickly.
Perhaps if you have long running jobs and no implementation of state saving it could find applications.
2 Duo. I remember when those came out and how multicore was still a novelty. Now my economy chip in my home desktop has 16 threads.
I think it’s a combination of factors:
I’ve worked on ground systems and it’s actually come in handy two times in five years, usually where we had a hard-to-reproduce bug. Getting the info when the problem happens can occasionally be all the difference.
Addendum: And usually we didn’t care about performance. Basically never.
When I left my last job they were using the zip file method for version control and one creative developer managed to link two versions of libc at the same time.
Software is so useful that the standard for utility is extremely low.
We test AND develop in production. Get on my level.
Way cool! Might actually try it sometime.
With KVM performance will be quite good, but when you need to emulate cross architecture? I don’t think there are many alternatives that support the entire VM. I only know of user space tools that are focused on emulating a binary.
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.