GoFuckYourself.com - Adult Webmaster Forum - View Single Post - Anyone Rent an Office With Shared Internet?

raymor · 05-09-2011, 10:37 AM

There's not much difference, really, except maybe for incoming connections, if they use
private IPs. If you pay the ISP directly for a connection in your office, they still bring the
connections together in a wiring closet somewhere. If you have a your own free standing
building, you are in fact sharing a connection with the other people on your street. Whether
the lines connect in the basement or at the end of the street doesn't much matter.

There are two ways that it can be set up. You can get a regular IP, if the ISP provides a pool
of IPs to the building, or you could get a private network IP, where the whole building has just
one public IP. If you get a public IP (an IP from the ISP), for all intents and purposes it's the
same thing as if you paid the ISP directly. If it's a private IP such as 196.168.x.x or 10.0.x.x,
you may have difficulty connection from your home to your office, and because with regular
FTP the server actually connects back to the client, you may need to use passive FTP.

Either way, assuming you have multiple computers which share data you'll probably want
to use your own router, in order to create your own private network within the building or
ISP network. When connecting outside of your own network and working with sensitive
data, you'll use encryption such as SSL, SSH, ftps, GPG, etc. That's the same as what
you're used to, where neighbors can often snoop on your unsecured traffic.

We'd suggest a two layered approach. It's probably a good idea to set your mail client
to use SSL/TLS for POP3, but also identify the sensitive data and encrypt it. For example,
we use GPG when sending credit card information through email, even though our email
connection uses SSL. That way the sensitive data has two levels of protection - the
standard encryption applied to all POP3 traffic, plus the GPG that's used for sensitive emails.

05-09-2011, 10:37 AM
raymor Confirmed User Join Date: Oct 2002 Posts: 3,745	There's not much difference, really, except maybe for incoming connections, if they use private IPs. If you pay the ISP directly for a connection in your office, they still bring the connections together in a wiring closet somewhere. If you have a your own free standing building, you are in fact sharing a connection with the other people on your street. Whether the lines connect in the basement or at the end of the street doesn't much matter. There are two ways that it can be set up. You can get a regular IP, if the ISP provides a pool of IPs to the building, or you could get a private network IP, where the whole building has just one public IP. If you get a public IP (an IP from the ISP), for all intents and purposes it's the same thing as if you paid the ISP directly. If it's a private IP such as 196.168.x.x or 10.0.x.x, you may have difficulty connection from your home to your office, and because with regular FTP the server actually connects back to the client, you may need to use passive FTP. Either way, assuming you have multiple computers which share data you'll probably want to use your own router, in order to create your own private network within the building or ISP network. When connecting outside of your own network and working with sensitive data, you'll use encryption such as SSL, SSH, ftps, GPG, etc. That's the same as what you're used to, where neighbors can often snoop on your unsecured traffic. We'd suggest a two layered approach. It's probably a good idea to set your mail client to use SSL/TLS for POP3, but also identify the sensitive data and encrypt it. For example, we use GPG when sending credit card information through email, even though our email connection uses SSL. That way the sensitive data has two levels of protection - the standard encryption applied to all POP3 traffic, plus the GPG that's used for sensitive emails. __________________ For historical display only. This information is not current: support@bettercgi.com ICQ 7208627 Strongbox - The next generation in site security Throttlebox - The next generation in bandwidth control Clonebox - Backup and disaster recovery on steroids