Welcome to the MacNN Forums.

msuper69 · 04:28 PM

Why is Safari giving me this warning when I open the MacNN homepage (www.macnn.com) ?

Clicking on the link from within that warning brings up this:

This just started happening in the last hour or so. Very strange.

Laminar · Mar 13, 2009, 04:25 PM

You need to find a better picture host - I'm being asked for a name and password to access iDisk when I load this page.

msuper69 · Mar 13, 2009, 04:30 PM

Originally Posted by Laminar

You need to find a better picture host - I'm being asked for a name and password to access iDisk when I load this page.

I've moved the images to a different location that should be accessible by anybody.

Thanks!

seanc · Mar 13, 2009, 04:51 PM

Looks like something's interfering with your DNS & trying to take you elsewhere.

Manually change your DNS servers to OpenDNS: 208.67.222.222, 208.67.220.220 - let us know the outcome.

besson3c · Mar 13, 2009, 04:54 PM

That warning is not for macnn.com. Unless the MacNN web server was compromised and redirecting people to a different domain, I would check on your local computer. What do you get when you go a:

hosts macnn.com
ping macnn.com

in your terminal?

turtle777 · Mar 13, 2009, 06:28 PM

Sounds like it could be that OS X trojan that changes DNS settings...

-t

Laminar · Mar 15, 2009, 01:42 AM

Hm....installed any jpgs lately?

turtle777 · Mar 15, 2009, 02:33 AM

LULZ.

-t

Camali · Mar 15, 2009, 10:57 AM

I got the same thing the yesterday, I kind of thought it was an ad causing this to pop up. It happened twice, only after like 4 seconds on the main MACNN screen. Hasn't happened to today though.

msuper69 · Mar 15, 2009, 11:11 AM

Originally Posted by besson3c

That warning is not for macnn.com. Unless the MacNN web server was compromised and redirecting people to a different domain, I would check on your local computer. What do you get when you go a:

hosts macnn.com
ping macnn.com

in your terminal?

Mikes-MBA:~ Michael$ host macnn.com
macnn.com has address 207.58.150.187
macnn.com mail is handled by 20 car.macnn.com.
macnn.com mail is handled by 20 dum.macnn.com.
macnn.com mail is handled by 10 postoffice.macnn.com.
macnn.com mail is handled by 20 bb.macnn.com.
macnn.com mail is handled by 20 sm.macnn.com.
macnn.com mail is handled by 20 ben.macnn.com.
Mikes-MBA:~ Michael$ ping macnn.com
PING macnn.com (207.58.150.187): 56 data bytes
64 bytes from 207.58.150.187: icmp_seq=0 ttl=54 time=56.674 ms
64 bytes from 207.58.150.187: icmp_seq=1 ttl=54 time=55.978 ms
64 bytes from 207.58.150.187: icmp_seq=2 ttl=54 time=54.963 ms
64 bytes from 207.58.150.187: icmp_seq=3 ttl=54 time=54.157 ms
64 bytes from 207.58.150.187: icmp_seq=4 ttl=54 time=55.289 ms
^C
--- macnn.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 54.157/55.412/56.674/0.861 ms

msuper69 · Mar 15, 2009, 11:32 AM

The original problem seems to have cleared up.

Now I'm getting constant beach balls no matter what action I take. Just typing a single letter causes a busy wait cursor.

I might open a new thread in Applications as this now has nothing to do with macnn but rather any web site. And I just started using the Safari 4 beta.

turtle777 · Mar 15, 2009, 12:06 PM

Might be incompatible plugins screwing up Safari 4.

-t

mr_zone · Mar 15, 2009, 09:12 PM

Got the same message yesterday when clicking on a macnn story link. Quit Safari, then tried Firefox, which downloaded a suspect pdf with that "wqoiwe..." filename. I get Finder crashes every 60 sec. or so now despite running NAV, ClamAV, and MacScan. OS X 10.4.11, Safari 3.2.1., on a PPC G4. Very annoying. No DNS changes.

besson3c · Mar 15, 2009, 10:03 PM

mr_zone: what do you get when you do a:

cat /etc/resolv.conf

in your terminal?

mr_zone · Mar 16, 2009, 07:33 AM

Here is the result of cat /etc/resolv.conf:

cat /etc/resolv.conf
domain hsd1.ct.comcast.net.
nameserver 68.87.71.226
nameserver 68.87.73.242
nameserver 68.87.64.146

reader50 · Mar 16, 2009, 11:50 PM

I had a PDF download (in Firefox) from a different site around the same time. Apparently prompted by an ad on that site.

My PDF contained a script, but since I don't let PDFs display in browser, and don't let my system auto-execute "safe" downloaded files, it didn't affect me at all.

Suggestion: in Safari prefs, turn off inline display of PDFs, and turn off "open safe files" after downloading. It may not be a big issue yet, but it's a security gap that will eventually be exploited.

As to the runaway processes, open a pair of Terminal windows. In the first one, type:

top -uds 5

This will give 5-second snapshots of all processes, sorted by CPU percentage. Look for suspicious stuff near the top of the list. If you see something weird hogging CPU, then note it's PID number in left-most column. Go to the other Terminal window and type:

kill 123

Where '123' would be the actual PID number of the suspect process. If it doesn't want to die, reissue the command as a non-ignorable kill order:

kill -9 123

Don't try to kill the kernel process (PID=0). If you kill something essential, you'll have to reboot. More detailed diagnostic advice should be sought in the OS X forum, or Apps if you narrow the problem down to just one app, like Safari.

turtle777 · Mar 17, 2009, 12:46 PM

Well, reader is right on how to kill the process, but you'd also need to make sure the process won't restart after you reboot.

-t

mr_zone · Mar 17, 2009, 06:43 PM

My Finder crash issue was fixed by simply going into System Prefs and turning off Stuffit Archive Via Rename (AVR). This was suggested by an older thread about OS X 10.4 on a Mac repair site. Odd that Console reported Finder crashes, odder still that the payload of a presumed rogue pdf would switch on AVR, or that AVR provoked crashing. I tried watching PIDs for awhile as suggested, but no sign of anything illicit. Thank you all for your help.

Chuckit · Mar 17, 2009, 06:55 PM

Archive Via Rename probably invades the Finder to do its thing.

turtle777 · Mar 17, 2009, 11:50 PM

Screw Stuffit.

-t