Personally I just think we should say to hell with this and make an standard chap protocol so that no matter what service you use you can chat with anybody anytime. I mean give me a break its just chatting who really cares that much anyway.
Just to let you know Slackware has a great version of linux that runs on sparc flawlessly for me so far. I'm a huge slackware buff so you know but still I would highly recommend it.
Re:Security for Mac Users
on
Cracking OSX
·
· Score: 1
I agree but I also thing that Apple was aiming alot into the UNIX crowd for this one. I mean as a UNIX users for years on end and a mac user I'm loving it. I mean how long does it take to make a great GUI for UNIX well apple did it. Anyways OS X is pretty secure out of box. It doesn't have much of anything open (port wise). Maybe we should start up our own OS X security training course hehe. Thanks for the great post.
IN a very rare case would this cause a problem with an ISP that was using these blocks also. Reason being if an ISP is using these types of address' inside for lets say maybe a webserver it would be hitting a firewall hopefully a cisco which would route to the destination of which the correct interface it is connected. If you had NAT setup at your business and or a firewall the ip that people and or routers would see would be the router you were either assinged statically from your ISP or from the dial-up pool that radius assinged you. The only thing the local address would have to do with anything would be routing locally. Hence the 10.x.x.x block that you are coming from should never affect the 10.x.x.x block that the isp is using. If this were the case breaking into the ISP's network would be an ease if they didn't have 10.x.x.x from 0.0.0.0 block out.
I would think though by putting this hosts on a DMZ it would still allow access to the inside network and hence you are back to where you started. If I were to do this I would more than likely just setup vpn and use that instead.
Slashdot Mirror
Personally I just think we should say to hell with this and make an standard chap protocol so that no matter what service you use you can chat with anybody anytime. I mean give me a break its just chatting who really cares that much anyway.
LOL now that was funny. Good one man.
Just to let you know Slackware has a great version of linux that runs on sparc flawlessly for me so far. I'm a huge slackware buff so you know but still I would highly recommend it.
I agree but I also thing that Apple was aiming alot into the UNIX crowd for this one. I mean as a UNIX users for years on end and a mac user I'm loving it. I mean how long does it take to make a great GUI for UNIX well apple did it. Anyways OS X is pretty secure out of box. It doesn't have much of anything open (port wise). Maybe we should start up our own OS X security training course hehe. Thanks for the great post.
IN a very rare case would this cause a problem with an ISP that was using these blocks also. Reason being if an ISP is using these types of address' inside for lets say maybe a webserver it would be hitting a firewall hopefully a cisco which would route to the destination of which the correct interface it is connected. If you had NAT setup at your business and or a firewall the ip that people and or routers would see would be the router you were either assinged statically from your ISP or from the dial-up pool that radius assinged you. The only thing the local address would have to do with anything would be routing locally. Hence the 10.x.x.x block that you are coming from should never affect the 10.x.x.x block that the isp is using. If this were the case breaking into the ISP's network would be an ease if they didn't have 10.x.x.x from 0.0.0.0 block out.
I would think though by putting this hosts on a DMZ it would still allow access to the inside network and hence you are back to where you started. If I were to do this I would more than likely just setup vpn and use that instead.