If you were to read the original post you'd see that this IS a Client/Customer
situation and thus it is most likely being "contracted out" and should_not be more
expensive. Especially since they are considering a Microsoft VPN product (which also
requires someone "onboard" to install/configure).
And since you're having a hard time with SSH, then use BSD/IPSec
Botton line is to use a secure, Free (other than service Obviously) solution, rather
than an expensive, flawed, proprietary solution.
Hope this clears things up for you..
cheers..
>>> [EMAIL PROTECTED] 07/25/00 12:19PM >>>
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.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
