our goose is cooked

[NeoGen]

Free-DC might be out doing us by 3 to 1 like rrcrain said, but we ain't letting go of our spot that easy! If they really want it they'll have to bleed for it! :twisted:

Keep pushing what you can gang! :D

[Majestic-12]

It warms my heart to see such an ethusiasm guys, but don't kill yourself over it - crawl only as much as you can, every little hepls and its the cause that matters rather than single individual performance - some people just have ridiculous amounts of resources, don't allow this to upset you or anything

[rrcrain]

I am having a serious issue with the client on both of my machines. On eht AMD 64 running XP. it is causing a BSOD and an automatic reboot. On the 2000 server, it's even goofier. It appears the client started broadcasting rather than sending addressed packets flooding my router (switch actually) in the process.

[carlos]

Majestic-12,

I have an Antivirus called NOD32 and it blocked one of the url's, saying it had a virus!!!! Do you want to comment?
Another question is how to join a team? I can't login using this page:

http://majestic12.kicks-ass.org/login.jhh

Regards,

Carlos

[NeoGen]

Norton Internet Security also raises several alarms sometimes when Majestic-12 is working on certain sites. I'm very convinced that Norton really blocks MJ12 from connecting to those sites, even tough I gave MJ12 full permission, thus probably contributing to the timed out stats.
I think there is no danger involved in MJ12 going through those sites, as the html code is scanned through like if it was a text file, no scripts are executed or anything, and it doesn't leave traces on the hard drive after packing in the bucket and returning.


And I tried the login site and it worked for me. I think I also had problems with it in the beggining, but don't remember how I solved it. I think my problem was with norton, I had to shut down the firewall to be able to access that site.

[Evil-Dragon]

Let me explain about how MJ12 deals with any malicious code, in case you are worried.

Sometimes viruses are embedded in web pages or in plain text. Because the viruses are read in plain text through MJ12 it will raise alarms with virus detectors because it will match signatures patterns.

Let me reassure you though, MJ12 NEVER executes any code... javascript, viruses, spyware, malware, etc... it saves all to plain text or discards it with Conan in place nowadays anyway.

There is nothing to worry about.

[carlos]

NeoGen,

The machine is at university behind a powerfull firewall. I can't login even turning off the Win XP firewall.

Evil-Dragon,

I'm not worried. Thanks.


Now I need to know if it is possible to manually join a team. Can the Majestic 12 administrator do that for me?

Carlos

[rrcrain]

Virus scan today revealed that the Majestic 12 client had become infected with the VBS.soraci.B virus.

This is the first virus to get onto my machine in over 2 years.

[NeoGen]

I made a quick search on that virus, found this:
http://www3.ca.com/securityadvisor/v....aspx?id=43004

Since it only affects HTML files it must be one of those virus that can come embedded with the html pages that MJ12 crawls, but we know that no code is executed, so it can't harm you.
And you get rid of it as soon as you upload the barrel back to HQ. Or even earlier maybe, as the content analyzing process should strip out the useful text from all the rest of the garbage and HTML that compose the page.

[Majestic-12]

Here is relevant FAQ entry: My anti-virus detected a virus in crawled data!

In a nutshell its possible that some webpages contain virus - some anti-viruses intercept those while they are crawled and say there is a virus - indeed there is but since its NEVER executed in any way _ANYWHERE_ - neither on your computer nor on my servers during indexing, there is no threat whatsoever.

The real issue with those virus alarms is that some anti-viruses choose to delete whole barrel with other pages - luckily this seems to happen so rarely that in a grand scheme of things its not very significant.

Now talking about BSOD that running node gives you - this is highly likely that something is wrong hardware wise on your PC - node can stress computer resources (especially when archiving) and if you have faulty hardware then it won't like it.

carlos: if you can't login please post in our forums in Bugs - I am currently tracking few similar issues and more voices only help assign higher priority.