Right. Except that there is no such thing as a trusted network. The old idea that we don't have to worry about security once you are inside the moat is just that: old. It has also been proven wrong time and again.

Internet keylogger? I'm not sure what that is, but the chances of either of those happening is nil when I never use clear text authentication for anything.

I'm glad you trust every single person who works for your ISP to be nice, competent, and to never make mistakes. Can I assume that this trust also extends to all the folks running servers in your ISP's facility (or the datacenter where they rent space)?

I'm not sure how noticing something in your logs has anything to do with your clear ignorance of security best practices, but whatever.

In all seriousness, thanks. It is this kind of foolish thinking (yes, please keep using clear text authentication), that keeps us real security professionals in business.

That is really the heart of the matter. "Security" is not some end state that can be reached, so it can not be there by default. Computer security is an ongoing process involving practices, procedures, and policies. It requires ongoing maintenance. Organizations that understand this have information security teams working full time. The rest have undetected compromised hosts that people are ignoring because last year they installed something to make it "secure."

I would argue that putting ssh on some arbitrary high port is in fact a bad idea. If for no other reason than you have given yourself the false sense that you have added some level of security. If you can't run ssh on port 22 and keep it secure, you are not making the situation better by moving to another port.

Are you really defending the use of plain text authentication as an acceptable practice?

You might want to do a little reading up on network security before making such preposterous statements.

...and you were doing so well, too! Why do people assume that "the lan" is some magical secure place? There is no such place. Treat all traffic leaving your machine as if it is on a public network. Otherwise, any vulnerable computer on your lan makes all the rest of the computers vulnerable as well.

Wow, you clearly know nothing of the history of the VCD. HINT: VCDs, while never very popular in the USA, continue to enjoy great popularity in other parts of the world, especially most parts of Asia (with the exception of Japan).

Real men don't need a file system to write data to a usb thumb drive.

tar cf /dev/sdb /stuff

No it doesn't and it wasn't sold. Back then all domain names were free for the asking. The title should be "The first registered .com domain name was just sold."

Unless you define the internet as the .com name space. The .edu name space is older and was just as much the internet.

Makes me wonder about your security policy...

While I don't agree with the parent's tone, I do agree with the sentiment. Most people don't want to learn anything. They don't care how it works. And yes, the Ubuntu forums are full of bad advice.

Also, I don't think the parent is talking about people like you or me. I like to learn how it all works and then use the easy automated tools. That way I can fix it when it breaks. You, I, and most slackware users are the people others will pay to fix things.

Instead of bashing Slackware, I just think of it as a distro for people who like manual transmissions, so to speak. ;)

I don't know what you do in your "environment" but I don't have a single server in the data center with less than 16g of ram and that right there requires a 64bit distro to use effectively.

I don't know about you, but from the earliest days the "box" was called "the computer." The computer + the monitor + the keyboard + the mouse, etc is called "the computer system."