On 25 Jul, Network Operations wrote:
> AcK!
>
> If "cheaper" is what they're lookin for why not freeBSD/SSH ??
>
> Now of course if they want a more secure solution I'd go with freeBSD/SSH instead..
>
> cheers..
>
> Marc..
>
I'd have to possibly disagree with you on both points.
In order to implement a BSD/SSH solution, they need someone on board who
understands BSD. Otherwise, it's contracted out, and thus becomes more
expensive.
As for a more secure solution... OpenBSD is generally seen as more
secure. Granted, once hardened, there's few differences between them,
but with all the security reviewing done by the OpenBSD team, that's
the public perception. And you don't need to use SSH. You can use the
integrated IPSec client (can't remember its name right now) to create
an IPSec VPN, thus providing the ability for it to integrate with other
compatible (i.e. FreeS/WAN and possibly PGP) IPSec clients.
--
Faith goes out through the window when beauty comes in at the door.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
