You don't mention the number of users, but the budget suggests small scale
:)
Windows 2003, SP1 and R2 provide RRAS, which will do L2TP/IPSEC, and with
WXP SP2 as your client you have 2048bit Diffie-Hellman encryption available.
Setting up RRAS to perform this task is done in less than 20 minutes and is
easy to get through a firewall inbound (IE your firewall). The problems you
have to face are:
. If you wish to use pre-shared keys (the "cheapest" way of doing it) you
will need to configure the PSK passphrase on each client individually - easy
with a small number of clients. Otherwise, you will need to invest in a
certificate authority.
. This is only suitable for access by known machines, not for internet café
type environments.
. This solution works great for the remote home user, but is less successful
for your travelling salesmen using the client's internet connection as they
generally have the relevant ports/protocols blocked.
. The locally configured PSK may not be stored in a highly secure manner on
the client machines and could possibly become known in the event a machine
configured with it is stolen. You may find yourself having to re-deploy a
new PSK.
I wrote a quick and dirty step-by-step here:
http://www.leafgrove.com/view_article.asp?id=19&cat=16&state=plus
In case one of your configured laptops is stolen and an attempt is made on
your RRAS solution, pay attention to your account locking on failed password
settings. You want permanent locks on a small number of attempts (say 5),
thus forcing administrative intervention and investigation in the event of
an account becoming locked.
Cheers
James D. Stallard
-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com] On
Behalf Of dubaisans dubai
Sent: 02 January 2007 04:17
To: focus-ms@securityfocus.com
Subject: Secure Remote access - windows 2003
I am planning to provide remote access from Internet to a windows 2003
domain
controller.User-ids, NTFS permissions are all configured.
The objective is file sharing and access.
Files will need to be copied. The machine has valid Internet IP address and
is
sitting behind a Firewall.
I would like to keep solution independent of Firewall.This will be accessed
by roaming users. I am thinking of something like 0penssh for windows or
maybe just GUI based Secure-FTP
Challenges I am facing
------------------------------------
Authentication should be strong. Something more than a password. [ No budget
for RSA securiD :-))) ]
Encryption for user-crentials/data access
Options considered
----------------------------------
I read W2K3 L2TP/IPSEC - looks complex. Terminal services - File copy is not
simple and also you require Application Mode license.
The number of remote users - less than 100
Cost effective , easy to implement and easy to manage solution sought
