Re: **Secure** Ftp server
From: Leythos (void_at_nowhere.com)
Date: 07/28/04
- Next message: ys: "What Windows process initiate connection to other Port 139?"
- Previous message: phn_at_icke-reklam.ipsec.nu: "Re: **Secure** Ftp server"
- In reply to: phn_at_icke-reklam.ipsec.nu: "Re: **Secure** Ftp server"
- Next in thread: Hairy One Kenobi: "Re: **Secure** Ftp server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 27 Jul 2004 22:02:45 GMT
In article <ce6hct$2v1b$1@nyheter.ipsec.se>, phn@icke-reklam.ipsec.nu
says...
> Leythos <void@nowhere.com> wrote:
> > In article <ce5iu3$2khc$1@nyheter.ipsec.se>, phn@icke-reklam.ipsec.nu
> > says...
> >> Mike <honey@michaelmoyse.co.uk> wrote:
> >> > phn@icke-reklam.ipsec.nu wrote:
> >>
> >> >> Leythos <void@nowhere.com> wrote:
> >> >>
> >> % stuff removed to focus on one question %%
> >>
> >> >> True. But i Can read, cert is one place to read about windows broken
> >> >> security, securityfocus another.
> >>
> >> > http://www.openbsd.org/security.html Is fun to read as well. Lets face
> >> > it, all operating systems have vulnerabilities and the biggest one is
> >> > the guy on the keyboard and his knowledge of security and the O/S he is
> >> > using. Then we are back on the TCO argument again.
> >>
> >> The refenrence to openbsd is interesting. There has not (to my knowledge)
> >> been a single break-in in an openbsd running default installation.
> >>
> >> There has been applications ( which you have to start first) that had
> >> holes, there has been a number of problems with local stuff ( where
> >> one must create a running process first in order to exploit).
> >>
> >> The application we are discussing, a simple ftp server would
> >> not be part of any of these problems. In fact one could use
> >> a 2.2 release ( 8 years old) and still be safe.
> >>
> >> Compare that to the track record of MS. Then compare the price
> >> difference, easiness of install and amount of work needed to
> >> keep the machine running.
>
> > Compare all of the above to a novice installing BSD and FTP and
> > configuring it on a new platform when he already has the MS licenses and
> > infrastructure - there is a cost, and it's significant. It would be more
> > secure and cheaper to just setup a open-source FTP product on a system
> > he already has, already has secured, and already understands.
>
> > Linux and it's variants is only one path, and it's not free by any
> > means, let alone for an installed Windows base. If you actually start
> > tracking the cost of a Linux server installation/maintenance to that of
> > a Windows 2000 server installation, doing the exact same things, they
> > are equal in time/effort and most big shops don't get the free version,
> > they get one that includes support agreements from one of the bigger nix
> > vendors, so cost is about the same.
>
> You should try it and answer from experience and not by quoting
> MS sales litterature. That's MS task, your ought to be to evaluate
> all possible ways of fulfilling a task.
I do answer for experience, 20+ years of it, as the for the licensing,
well, if you can't get a straight answer from MS then who can you get
one from :) I've managed everything from 370's, IBM AIX servers, and 4
bit processor based systems to the current bread of Windows and some
Linux based systems.
-- -- spamfree999@rrohio.com (Remove 999 to reply to me)
- Next message: ys: "What Windows process initiate connection to other Port 139?"
- Previous message: phn_at_icke-reklam.ipsec.nu: "Re: **Secure** Ftp server"
- In reply to: phn_at_icke-reklam.ipsec.nu: "Re: **Secure** Ftp server"
- Next in thread: Hairy One Kenobi: "Re: **Secure** Ftp server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]