Ordinary Mind

http://www.nirsoft.net/utils/blue_screen_view.html

Seems to be nice but BSOD is rare this day.

It’s a bit odd that Visual Studio doesn’t even come with basic automatic build/version number increment. The community tasks,

http://msbuildtasks.tigris.org/

seems to be powerful but there is basically no documentation. You’ve to dive into the source code to know how use it. The best doc I can find are this and this.

I was working on a script that required cookie authentication. The script failed to set cookie in IE8 with domain specified. It works if domain is not set nor runs on Firefox. After hours of search, I finally got the answer from Eric’s Internet Explorer Cookie Internals (FAQ) - IE would only save cookie to level 3 or higher domain, e.g .level3.xx.yy but not xx.yy nor yy. What a shame!

PSTools is an indispensable set of tools to any Windows admin. But you could get caught if you are not careful.

To improve security, I usually run schedule job with a specific account that granted with least required privileges. This is a good practice but this should be done before performing final test!

I had once setup a schedule job running psexec and later found that the job never completed. It’s found that the process hung at the EULA dialog because I’ve never run psexec with that particular account on the system. So, test your setup no matter how trivial the change you have done. BTW, for this particular case, there is an undocumented option /accepteula which helps to skip the EULA dialog.

To get rid of those boring 404 favicon.ico not found error in the web server error log,  I spared a few minutes this afternoon to draw my first favicon using favicon.cc .  Though I’m not good at graphics, it’s not that difficult at all.

Have explored PKI for a long time. Now both OpenCA and Microsoft CA support OCSP,

• OpenCA OCSP Daemon
• Online Responder Installation, Configuration, and Troubleshooting Guide

and RSA moved the OCSP responder to a separate product since Keon 6.6.

When develop with subversion or other source control tool, I think performing svn update on the production web site is better than export the source on to the server. However, such practice could be a security risk if you don’t protect the meta data directories, e.g. .svn for Subversion.

For Apache web server, you may protect CVS/SVN/GIT meta data  dir by adding the following lines to the server/site config file,

# protect src meta data
<IfModule mod_rewrite.c>
RewriteEngine on

# Protect directories used by CVS, Subversion and Git - see also above.
ReWriteRule “(^|/)(CVS|\.svn|\.git)/” - [F]
</IfModule>

Be sure to have mod_rewrite enabled or the above lines have no effect.

Using the Directory or DirectoryMatch directives like this,

# forbidden access to svn dir
<Directory ~ “.*/\.svn/”>
Order allow,deny
Deny from all
</Directory>

may achieve similar result but meta data in cgi directory could get executed, e.g.

http://your_server/cgi-bin/.svn/README.txt

http://www.apachetutor.org/admin/reverseproxies

Apple launches HTTP Live Streaming standard in iPhone 3.0

Apple looks to improve visual quality of streaming video