Also -- and I apologize if this was already covered -- have yoy checked to make sure that you aren't running any firewall scripts on the host itself?
Finally ... "tcpdump -n -i eth0 port 22" will tell all.
That leaves something else on the Linux box that's preventing
incoming connections from working on that port for some reason.
ListenAddress is not set at all within sshd_config.
iptables shows an ACCEPT for tcp from anywhere to anywhere on ssh.
tcpdump is... verbose. I will probably need to perform that on the console (for sanity's sake), and access my work computer to try connecting to port 22 from remote.
Yes, I can.
is your friend
That's correct. I just have the one nic in the machine. There's another machine that's acting as a firewall (it's a hardware firewall, the kind appropriate for a small business rather than a residence, heh).
Reading databases from /usr/share/clamav
Not loading PUA signatures.
LibClamAV Error: cli_hex2str(): Malformed hexstring: This ClamAV version has
reached End of Life! Please upgrade to version 0.95 or later. For more
information see www.clamav.net/eol-clamav-094 and www.clamav.net/download
I understand why they do the warnings that the engine is old and needs to be
upgraded, but to SHUT THE WHOLE THING OFF because some newer signatures don't
work? That's STUPID!!!
But what you see here is a perfect example of the you-must-stay-in-the-game mantra that is so endemic (?) in the linux world.
You HAVE to keep up whether you want to or not. And more often than not I don't want to, I want to keep what I have working... working, but you can't do that.
Certainly you've run into this before no?
This was a deliberate crippling of a piece of software. And yes, it's partially my fault because I don't follow the mailing list, but really, should I have to? They sent out a message a few months ago saying that support for 0.94 was going to end, but then this week they officially forced 0.94 off the air by sending out an update that they knew would make it stop working. Somehow they got their URL into the error message, too.
This is very irresponsible. Millions of seats of email are protected by ClamAV. Depending on the configuration of each site, those seats either became unprotected or stopped receiving email.
partially my fault because I don't follow the mailing list, but really,
should I have to? They sent out a message a few months ago saying that
No, you shouldn't have to even have paid attention to the support-going-away email either.
But consider other instances.
w3c.org (I think that's the url) is the domain listed in a lot of DTD listings. They're there for reference, they're not supposed to be programmatically used, but apparently a lot of software was resolving the address and reading the file, such that the w3c ended up paying a lot of money in bandwidth they didn't intend to (that'll teach them to use a URL to denote a file version, assholes) so what they did was fix their webserver to start returning http 503 when systems asked for these files and one day lots of software all over the world started breaking. Yay.
People who ran the software who's fault it was not, they just bought a broken package.
There's another example I had, but I can't remember at themoment, but that's just the way it is people just do whatever they want, and you have to deal.
Actually I guess the best example is facebook. THey're so stoned on their success that they have no concept that they should have some respect for their FREE DEVELOPER base. They break their API all the time and they could care less how many programs they break, becuase they're popular, and it's not their problem.
I expect apple to do the same thing. I suppose in one sense they already do. The hell you have to go through to put up an app is abuse never before seen in the software world (well, outside AT&T I guess)
They All Suck.
Lovely log message from dovecot:
"Time just moved backwards by 8 seconds. This might cause a lot of problems, so I'll just kill myself now."
This is very irresponsible. Millions of seats of email are protected
by ClamAV. Depending on the configuration of each site, those seats
either became unprotected or stopped receiving email.
Umm, developers of antivirus software don't generally support old engine versions indefinitely. If you want to guard against the latest threats... you have to update.
I recently got rid of my 2nd to last machine and I think I mentioned this I now have nowhere to backup my one remaining machine to.
so I got a 64g usb stick, and it finally arrived yesterday.
So I was playing with it. First I thought I'd try my rsync trick.
Well, the stick was formatted fat32, so all the permission information went away.
so I put a ext3 filesystem on it and linux started complaining that there was no journaling information and wouldn't mount it.
Okay, ext2, it did that, and then I tried to rsync to it, and I got lots of IO errors.
I don't know if this is bad memory or the driver doesn't work or what, but it reliably messed up files a lot of the time.
So I ran badblocks and it said there were no problems (but that was a readonly test) I haven't tried a write/read test yet.
So... before I go too much farther is there a know issue with using USB sticks with ext2? I looked around and it seems like common practice.
It's quite possible I got a shitty stick, or maybe a stick of shit but I dunno.
Are there usb stick verify utilities?
You should not use a journaling file system on a stick. Excessive writes will burn up the stick in short time, Linux does one heck of a lot of writes. Ubuntu has an option to install to a USB stick...check what non-journaling file system that uses.