I had this problem 8 years ago, but with ASP as we called it then
The problem is that the ASP code runs on a remote server, whereas your smartcard reader is a local piece of hardware
How I got round it was a small client application that regularly polled the smartcard reader for a card insert/removal. If a card was inserted, then it called a web-service to alert the server, which created a unique key based on the card and some random number. It then asked the user to enter a PIN, which was related to the card id and random number.
This meant that it required the particular card and an unreapeatable number. I pretty sure I used SSL to encrypt the web-service message, which of course is the most vulnerable part of the system
that's how I did it. The SCM tech support guys are really helpful and speak excellent English, it may be worth giving them a shout
The ApplicationPoolIdentity
is assigned membership of the Users
group as well as the IIS_IUSRS
group. On first glance this may look somewhat worrying, however the Users
group has somewhat limited NTFS rights.
For example, if you try and create a folder in the C:\Windows
folder then you'll find that you can't. The ApplicationPoolIdentity
still needs to be able to read files from the windows system folders (otherwise how else would the worker process be able to dynamically load essential DLL's).
With regard to your observations about being able to write to your c:\dump
folder. If you take a look at the permissions in the Advanced Security Settings, you'll see the following:
See that Special permission being inherited from c:\
:
That's the reason your site's ApplicationPoolIdentity
can read and write to that folder. That right is being inherited from the c:\
drive.
In a shared environment where you possibly have several hundred sites, each with their own application pool and Application Pool Identity, you would store the site folders in a folder or volume that has had the Users
group removed and the permissions set such that only Administrators and the SYSTEM account have access (with inheritance).
You would then individually assign the requisite permissions each IIS AppPool\[name]
requires on it's site root folder.
You should also ensure that any folders you create where you store potentially sensitive files or data have the Users
group removed. You should also make sure that any applications that you install don't store sensitive data in their c:\program files\[app name]
folders and that they use the user profile folders instead.
So yes, on first glance it looks like the ApplicationPoolIdentity
has more rights than it should, but it actually has no more rights than it's group membership dictates.
An ApplicationPoolIdentity
's group membership can be examined using the SysInternals Process Explorer tool. Find the worker process that is running with the Application Pool Identity you're interested in (you will have to add the User Name
column to the list of columns to display:
For example, I have a pool here named 900300
which has an Application Pool Identity of IIS APPPOOL\900300
. Right clicking on properties for the process and selecting the Security tab we see:
As we can see IIS APPPOOL\900300
is a member of the Users
group.
Best Answer
Use
windbg
from the Windows SDK debug tools. The function you are looking for isInTSRedirectModeWithContext
.Also this might help: http://lifayk.blogspot.ro/2012/07/windows-smart-card-subsystem-and-remote.html