|
|
sending info through port 80, using a domain name, isight flashes?
lostInSpace commented on using another protocol. One thing I thought of, is that if the person is using from a port restricted wifi connection (like a lot of coffee shops, airports, etc) it may not work to ssh or ftp the image file or ip address back to the server. I think a thread to lostInSpace's comment noted using curl instead. Either way I think this is a great hint and really an excellent way to monitor this activity. With an obscure name to the daemon, it would nearly be impossible for even a fairly advanced mac user to know what is going on before its too late. They would have to systematically look in the activity monitor utility and find any daemons non-standard to the os install. I don't know if I could do it.
sending info through port 80, using a domain name, isight flashes?
This will work with IPs or a DNS name. In my environment and for at home, I use an IP so thats why it's based around that. A normal web address will work fine too though, just make sure it fits in the script. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.07 seconds |
|