OT: File Server at home
Guest
Posts: n/a
Re: OT: File Server at home
HomeBrewer proclaimed:
>>Run a secure ftp server on Linux or FreeBSD. Do not run the built in FTP
>>server (IIS) in Windows. If you don't know how to set up sftp, find a
>>buddy to do it for you. Also, a public server should be on a dedicated
>>demiliterized computer.
>
>
> Tried linux, can't go back there - never heard of freebsd - I'll google it.
> I gues by demiliterized you mean nothing of importance on it?
FreeBSD was pretty popular about 10 years ago among small to medium
sized ISP's.
>>Run a secure ftp server on Linux or FreeBSD. Do not run the built in FTP
>>server (IIS) in Windows. If you don't know how to set up sftp, find a
>>buddy to do it for you. Also, a public server should be on a dedicated
>>demiliterized computer.
>
>
> Tried linux, can't go back there - never heard of freebsd - I'll google it.
> I gues by demiliterized you mean nothing of importance on it?
FreeBSD was pretty popular about 10 years ago among small to medium
sized ISP's.
Guest
Posts: n/a
Re: OT: File Server at home
HomeBrewer proclaimed:
>>Run a secure ftp server on Linux or FreeBSD. Do not run the built in FTP
>>server (IIS) in Windows. If you don't know how to set up sftp, find a
>>buddy to do it for you. Also, a public server should be on a dedicated
>>demiliterized computer.
>
>
> Tried linux, can't go back there - never heard of freebsd - I'll google it.
> I gues by demiliterized you mean nothing of importance on it?
FreeBSD was pretty popular about 10 years ago among small to medium
sized ISP's.
>>Run a secure ftp server on Linux or FreeBSD. Do not run the built in FTP
>>server (IIS) in Windows. If you don't know how to set up sftp, find a
>>buddy to do it for you. Also, a public server should be on a dedicated
>>demiliterized computer.
>
>
> Tried linux, can't go back there - never heard of freebsd - I'll google it.
> I gues by demiliterized you mean nothing of importance on it?
FreeBSD was pretty popular about 10 years ago among small to medium
sized ISP's.
Guest
Posts: n/a
Re: OT: File Server at home
HomeBrewer proclaimed:
>>Run a secure ftp server on Linux or FreeBSD. Do not run the built in FTP
>>server (IIS) in Windows. If you don't know how to set up sftp, find a
>>buddy to do it for you. Also, a public server should be on a dedicated
>>demiliterized computer.
>
>
> Tried linux, can't go back there - never heard of freebsd - I'll google it.
> I gues by demiliterized you mean nothing of importance on it?
FreeBSD was pretty popular about 10 years ago among small to medium
sized ISP's.
>>Run a secure ftp server on Linux or FreeBSD. Do not run the built in FTP
>>server (IIS) in Windows. If you don't know how to set up sftp, find a
>>buddy to do it for you. Also, a public server should be on a dedicated
>>demiliterized computer.
>
>
> Tried linux, can't go back there - never heard of freebsd - I'll google it.
> I gues by demiliterized you mean nothing of importance on it?
FreeBSD was pretty popular about 10 years ago among small to medium
sized ISP's.
Guest
Posts: n/a
Re: OT: File Server at home
FreeBSD is "linux" based on the Berkley kernel; Redhat is based on the
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
Guest
Posts: n/a
Re: OT: File Server at home
FreeBSD is "linux" based on the Berkley kernel; Redhat is based on the
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
Guest
Posts: n/a
Re: OT: File Server at home
FreeBSD is "linux" based on the Berkley kernel; Redhat is based on the
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
Guest
Posts: n/a
Re: OT: File Server at home
FreeBSD is "linux" based on the Berkley kernel; Redhat is based on the
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
System V kernel.
Lon wrote:
> HomeBrewer proclaimed:
>
>>> Run a secure ftp server on Linux or FreeBSD. Do not run the built in
>>> FTP
>>> server (IIS) in Windows. If you don't know how to set up sftp, find a
>>> buddy to do it for you. Also, a public server should be on a dedicated
>>> demiliterized computer.
>>
>>
>>
>> Tried linux, can't go back there - never heard of freebsd - I'll
>> google it.
>> I gues by demiliterized you mean nothing of importance on it?
>
>
> FreeBSD was pretty popular about 10 years ago among small to medium
> sized ISP's.
>
>
Guest
Posts: n/a
Re: File Server at home
HomeBrewer proclaimed:
>>Most ISPs frown on running servers and several actually block port 80
>
> HTTP.
>
>>So I'd say FTP would be the better option. That and at least on *** they
>
> allow
>
>>FTP providing it's not set up for anonymous access.
>>
>>XP pro comes with a basic FTP service. Read up on any vulerabilites and
>
> make
>
>>sure that box is secure because as soon as you put it up joe-hacker is
>
> going
>
>>to try connecting.
>>
>>Linky > http://www.sofotex.com/download/FTP_Software/
>
>
>
> I know how to use FTP programs to get files and look at other servers, but I
> tried to set one up as a host and I could never connect to it ( I think the
> software was FTPserver or something like that). I think it was because it
> was behind my router. I also tried to load linux on my old machine - but
> linux proved to be too much of a learning curve. I don't need a server that
> bad.
>
> Basically I would just like to have the computer sitting there hosting files
> for me. I think I have to mess with my router settings and have it do some
> of the work. Or maybe I can't even have a ftp server behind a router, I
> don't know.
>
Rather than use FTP or worse, NetBIOS, you might want to use secure
socket layer with secure shell and secure copy. That way you could
set a key [for each partner] in each machine and allow only those
systems where the key has been set to connect.
Most FTP's are too easy to crack.
>>Most ISPs frown on running servers and several actually block port 80
>
> HTTP.
>
>>So I'd say FTP would be the better option. That and at least on *** they
>
> allow
>
>>FTP providing it's not set up for anonymous access.
>>
>>XP pro comes with a basic FTP service. Read up on any vulerabilites and
>
> make
>
>>sure that box is secure because as soon as you put it up joe-hacker is
>
> going
>
>>to try connecting.
>>
>>Linky > http://www.sofotex.com/download/FTP_Software/
>
>
>
> I know how to use FTP programs to get files and look at other servers, but I
> tried to set one up as a host and I could never connect to it ( I think the
> software was FTPserver or something like that). I think it was because it
> was behind my router. I also tried to load linux on my old machine - but
> linux proved to be too much of a learning curve. I don't need a server that
> bad.
>
> Basically I would just like to have the computer sitting there hosting files
> for me. I think I have to mess with my router settings and have it do some
> of the work. Or maybe I can't even have a ftp server behind a router, I
> don't know.
>
Rather than use FTP or worse, NetBIOS, you might want to use secure
socket layer with secure shell and secure copy. That way you could
set a key [for each partner] in each machine and allow only those
systems where the key has been set to connect.
Most FTP's are too easy to crack.
Guest
Posts: n/a
Re: File Server at home
HomeBrewer proclaimed:
>>Most ISPs frown on running servers and several actually block port 80
>
> HTTP.
>
>>So I'd say FTP would be the better option. That and at least on *** they
>
> allow
>
>>FTP providing it's not set up for anonymous access.
>>
>>XP pro comes with a basic FTP service. Read up on any vulerabilites and
>
> make
>
>>sure that box is secure because as soon as you put it up joe-hacker is
>
> going
>
>>to try connecting.
>>
>>Linky > http://www.sofotex.com/download/FTP_Software/
>
>
>
> I know how to use FTP programs to get files and look at other servers, but I
> tried to set one up as a host and I could never connect to it ( I think the
> software was FTPserver or something like that). I think it was because it
> was behind my router. I also tried to load linux on my old machine - but
> linux proved to be too much of a learning curve. I don't need a server that
> bad.
>
> Basically I would just like to have the computer sitting there hosting files
> for me. I think I have to mess with my router settings and have it do some
> of the work. Or maybe I can't even have a ftp server behind a router, I
> don't know.
>
Rather than use FTP or worse, NetBIOS, you might want to use secure
socket layer with secure shell and secure copy. That way you could
set a key [for each partner] in each machine and allow only those
systems where the key has been set to connect.
Most FTP's are too easy to crack.
>>Most ISPs frown on running servers and several actually block port 80
>
> HTTP.
>
>>So I'd say FTP would be the better option. That and at least on *** they
>
> allow
>
>>FTP providing it's not set up for anonymous access.
>>
>>XP pro comes with a basic FTP service. Read up on any vulerabilites and
>
> make
>
>>sure that box is secure because as soon as you put it up joe-hacker is
>
> going
>
>>to try connecting.
>>
>>Linky > http://www.sofotex.com/download/FTP_Software/
>
>
>
> I know how to use FTP programs to get files and look at other servers, but I
> tried to set one up as a host and I could never connect to it ( I think the
> software was FTPserver or something like that). I think it was because it
> was behind my router. I also tried to load linux on my old machine - but
> linux proved to be too much of a learning curve. I don't need a server that
> bad.
>
> Basically I would just like to have the computer sitting there hosting files
> for me. I think I have to mess with my router settings and have it do some
> of the work. Or maybe I can't even have a ftp server behind a router, I
> don't know.
>
Rather than use FTP or worse, NetBIOS, you might want to use secure
socket layer with secure shell and secure copy. That way you could
set a key [for each partner] in each machine and allow only those
systems where the key has been set to connect.
Most FTP's are too easy to crack.
Guest
Posts: n/a
Re: File Server at home
HomeBrewer proclaimed:
>>Most ISPs frown on running servers and several actually block port 80
>
> HTTP.
>
>>So I'd say FTP would be the better option. That and at least on *** they
>
> allow
>
>>FTP providing it's not set up for anonymous access.
>>
>>XP pro comes with a basic FTP service. Read up on any vulerabilites and
>
> make
>
>>sure that box is secure because as soon as you put it up joe-hacker is
>
> going
>
>>to try connecting.
>>
>>Linky > http://www.sofotex.com/download/FTP_Software/
>
>
>
> I know how to use FTP programs to get files and look at other servers, but I
> tried to set one up as a host and I could never connect to it ( I think the
> software was FTPserver or something like that). I think it was because it
> was behind my router. I also tried to load linux on my old machine - but
> linux proved to be too much of a learning curve. I don't need a server that
> bad.
>
> Basically I would just like to have the computer sitting there hosting files
> for me. I think I have to mess with my router settings and have it do some
> of the work. Or maybe I can't even have a ftp server behind a router, I
> don't know.
>
Rather than use FTP or worse, NetBIOS, you might want to use secure
socket layer with secure shell and secure copy. That way you could
set a key [for each partner] in each machine and allow only those
systems where the key has been set to connect.
Most FTP's are too easy to crack.
>>Most ISPs frown on running servers and several actually block port 80
>
> HTTP.
>
>>So I'd say FTP would be the better option. That and at least on *** they
>
> allow
>
>>FTP providing it's not set up for anonymous access.
>>
>>XP pro comes with a basic FTP service. Read up on any vulerabilites and
>
> make
>
>>sure that box is secure because as soon as you put it up joe-hacker is
>
> going
>
>>to try connecting.
>>
>>Linky > http://www.sofotex.com/download/FTP_Software/
>
>
>
> I know how to use FTP programs to get files and look at other servers, but I
> tried to set one up as a host and I could never connect to it ( I think the
> software was FTPserver or something like that). I think it was because it
> was behind my router. I also tried to load linux on my old machine - but
> linux proved to be too much of a learning curve. I don't need a server that
> bad.
>
> Basically I would just like to have the computer sitting there hosting files
> for me. I think I have to mess with my router settings and have it do some
> of the work. Or maybe I can't even have a ftp server behind a router, I
> don't know.
>
Rather than use FTP or worse, NetBIOS, you might want to use secure
socket layer with secure shell and secure copy. That way you could
set a key [for each partner] in each machine and allow only those
systems where the key has been set to connect.
Most FTP's are too easy to crack.
