I can't speak for them now since, as I said, I'm no longer there; but that was certainly the case when I was there. There was just too much risk of abuse to generally allow outbound connections of any sort. It's a pretty unique environment, from a security perspective. You have to consider the external network to be more trustworthy than the internal.
As the former sysadmin of the Test Drive Program, I can say pretty definitively that Test Drive has been around for years - since before Compaq bought Digital, I believe. It's nice to see it mentioned, since I know the folks in MRO work pretty hard to keep it going. My admittedly biased feeling on the subject is that Test Drive is a pretty good place where anyone can go to try out operating systems and software on HP hardware to which they might not otherwise have access. They also make sure there are compilers on each system, so you can try our own code on other platforms as well. You can also check out the definitive list of current systems in the program.
They're also blocking email from residential cable modem users who have their own MTAs. As near as I can tell, they started doing this around March 31. At least, that's when the first message bounced back to me with the following message:
550-The IP address you are using to connect to AOL is an IP address owned
550-by ATTBI/Comcast and is either open to the free relaying of e-mail,
550-is serving as an open proxy, or is a dynamic (residential) IP address.
550-AOL cannot accept further e-mail transactions from your server until
550-either your server is closed to free relaying/proxy, or your provider
550-removes your IP address from their list of dynamic IP addresses. For
550-additional information, please visit http://postmaster.info.aol.com
550-or contact your network support organization at
550-security_ldc@cable.comcast.com.
550 Goodbye
Why did you choose to look at the TCP/IP code over any other particular subsystem? Do you have plans to review any other portions of the code? For instance, I think it would be very interesting to see a similar comparison which examined the code for file systems or virtual memory. Have you reported the bugs you found back to the authors of the code?
Slashdot Mirror
I can't speak for them now since, as I said, I'm no longer there; but that was certainly the case when I was there. There was just too much risk of abuse to generally allow outbound connections of any sort. It's a pretty unique environment, from a security perspective. You have to consider the external network to be more trustworthy than the internal.
As the former sysadmin of the Test Drive Program, I can say pretty definitively that Test Drive has been around for years - since before Compaq bought Digital, I believe. It's nice to see it mentioned, since I know the folks in MRO work pretty hard to keep it going. My admittedly biased feeling on the subject is that Test Drive is a pretty good place where anyone can go to try out operating systems and software on HP hardware to which they might not otherwise have access. They also make sure there are compilers on each system, so you can try our own code on other platforms as well. You can also check out the definitive list of current systems in the program.
They're also blocking email from residential cable modem users who have their own MTAs. As near as I can tell, they started doing this around March 31. At least, that's when the first message bounced back to me with the following message:
550-The IP address you are using to connect to AOL is an IP address owned
550-by ATTBI/Comcast and is either open to the free relaying of e-mail,
550-is serving as an open proxy, or is a dynamic (residential) IP address.
550-AOL cannot accept further e-mail transactions from your server until
550-either your server is closed to free relaying/proxy, or your provider
550-removes your IP address from their list of dynamic IP addresses. For
550-additional information, please visit http://postmaster.info.aol.com
550-or contact your network support organization at
550-security_ldc@cable.comcast.com.
550 Goodbye
And that, my liege, is how we know the Earth to be banana shaped.
;-)
Someone had to say it.
Why did you choose to look at the TCP/IP code over any other particular subsystem? Do you have plans to review any other portions of the code? For instance, I think it would be very interesting to see a similar comparison which examined the code for file systems or virtual memory. Have you reported the bugs you found back to the authors of the code?