Re: VS2005 website deployment problems with EFS



I am not reallly too worried about moving projects outside of my documents. I do this all the time. In fact, my normal location for projects is c:\projects (or d:\projects when I have a second drive). It is just another backup location for me. And, since I have projects in source control, it is not an issue. If help desk thinks this will help, I am all for it.

As for deploying sites, can you publish to a local directory? If so, you can then xcopy the bits out to the server. I prefer this method over publishing directly, esp. to production, as it gives me a chance to test the published site prior to going live.

We use PointSec. It is not WIndows EFS, but it does encrypt. I state this, as I have had no problems with encryption, but I am not using the exact type you are.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

Blog:
http://feeds.feedburner.com/GregoryBeamer

*********************************************
| Think outside the box |
*********************************************
"JeffDotNet" <JeffDotNet@xxxxxxxxxxxxxxxxx> wrote in message news:647ABE3C-5AE4-43B4-8C31-75623265970C@xxxxxxxxxxxxxxxx
Recently we were required to install EFS on our machines.

Ever since the installation of EFS I have been unable to successfully us the
publish website or copy website deployment methods without manually
decrypting the files first.

Dev laptop: Win XP SP2 (Machine I am deploying website from)
Visual Studio 2005 SP1
Dev Server: win2003 (Destination of the website)

“Publish website”
Publish website will exit with Publish Succeeded but will not publish any
files that have been encrypted by EFS. (This leaves me little more than a
set of empty directories)

“Copy Website”
Using Visual studio “copy website” takes forever and in the end fails and
the log reports it was unable to encrypt files.

If I manually decrypt the files before using “Copy Website” visual studio is
able to properly send the files to the server. However this manual
decryption causes the source file timestamps to be modified and this is very
undesirable.

Manual Copy (Without “Copy Website”)

If I manually copy the files to my development server it takes an extremely
long time. (between 15-45minutes for a small intranet application) I assume
this is due to the decryption being done just prior to moving the files.

If I manual decrypt the files then the manual copy the files it is quick as
ever.


The helpdesk has recommended moving my projects outside of my documents to
avoid the EFS encryption. Is there a way to configure VS2005 to work around
EFS? I would really prefer not to move my VS projects outside of my
documents.


.



Relevant Pages

  • RE: Laptop Security - Microsoft EFS
    ... With EFS the keyare unique to the drive. ... EFS to encrypt system files. ... cleartext during a mount attack, but the easiest way for an attacker to gain ... who can also decrypt the respective persons info. ...
    (Security-Basics)
  • VS2005 website deployment problems with EFS
    ... Recently we were required to install EFS on our machines. ... publish website or copy website deployment methods without manually ... If I manual decrypt the files then the manual copy the files it is quick as ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Info regd Hard Disk Encryption required.
    ... Another similar solution is to run a virtual machine and encrypt its entire ... EFS can handle that. ... > An alternative to EFS is the older PGP Disc. ... >> decrypt it while the system is booting. ...
    (microsoft.public.win2000.security)
  • Re: EFS and Biometrics? Other options?
    ... There is no password involved in EFS. ... specified recovery agent and available keys. ... To decrypt the file, the machine must be able to access either the user's ... the private key that corresponds to the public key that was used to encrypt ...
    (Focus-Microsoft)
  • Re: efs and "encryption" overall... help?
    ... To be absolutely sure that an attacker can not access EFS encrypted files ... stronger encryption to encrypt EFS files, not that it would be easy to crack ... Pro that more then one user may be able to decrypt the file if the original ... > first encryption a certificate is created that is used to decrypt those ...
    (microsoft.public.windows.server.networking)