Sorry if this is off topic. Ignore this if you wish.
The big topic on the news and on the internet recently has been the screening that goes on at airports. It makes me wonder why there are no systems that use facial recognition to pull up information on each and every passenger going onto a flight.
Faces could be scanned during ticketing and check in and info provided at the ticket desk (ie. name, ID, etc.) could be included to look up each and every passenger that will be travelling. By the time they get to the security checkpoint, passenger profiles could be available to screeners. Anyone not found in the system, would be filtered through a "higher" level of screening. Those that are in the "system" would be directed to the "standard" level of screening.
I'm wondering why this kind of system does not exist today.
References:
http://eyetrackingupdate.com/2010/01/14/accurate-biometric-needed-for-screening-airport-security/
http://www.securitymanagement.com/news/british-airport-tests-facial-recognition-security-gates-005635
http://www.militaryaerospace.com/index/display/article-display/162111/articles/military-aerospace-electronics/volume-13/issue-11/electro-optics-supplement/news/facial-recognition-takes-off-in-airport-security.html
Thursday, November 18, 2010
Tuesday, November 16, 2010
Huge Framework.log file?
This seems to occur for SQL 2005 running on Windows 2003 server. Adding DELETE permission to the Network service account fixed it.
To set the permissions on the %systemroot%\system32\ wbem\logs folder, follow these steps:
To set the permissions on the %systemroot%\system32\ wbem\logs folder, follow these steps:
- Locate the %systemroot%\system32\wbem\logs folder, right-click on the folder, and then select Properties.
- On the Security tab, click the Advanced button.
- Select the NETWORK SERVICE account from the Permission entries list, and then click Edit.
- Locate the Delete permission, and then click to select the Allow checkbox.
- Click OK three times.
Reference: http://support.microsoft.com/kb/836605
Monday, November 15, 2010
CrashOnAuditFail regkey
If you have this regkey set to "1", beware of your disk space running out for any reason. If the drive that houses the Windows event logs gets full and the security log is unable to write entries, this regkey gets set to "2" and only local Administrators will be allowed to connect to and from the server.
To restore functionality, you will need to clear up disk space where the event logs are being stored and then reset the regkey to "1" and reboot the server.
Windows NT provides the "Crash On Audit Fail" flag in the Registry key located in SYSTEM\CurrentControlSet\Control\Lsa\CrashOnAuditFail.
Reference: http://technet.microsoft.com/en-us/library/cc963220.aspx
To restore functionality, you will need to clear up disk space where the event logs are being stored and then reset the regkey to "1" and reboot the server.
Windows NT provides the "Crash On Audit Fail" flag in the Registry key located in SYSTEM\CurrentControlSet\Control\Lsa\CrashOnAuditFail.
Reference: http://technet.microsoft.com/en-us/library/cc963220.aspx
Labels:
CrashOnAuditFail,
Registry,
Windows 2000,
Windows 2003
Subscribe to:
Comments (Atom)