Monthly Archives: June 2004

continuing my “Security in Whidbey” collection, there’s a new article on MSDN describing the new security features in ASP.NET 2.0. Another one (from our favourite security geek :) can be found here.

this morning i had some free time (and also was fed up with WMI, with which i was experimenting the last days) – so i opened my ever growing outlook task list and one entry catched my attention “check out LogParser!”. cool – … Continue reading →

UPDATE : new version available windows includes a handy little tool called ‘netsh’. you can use this to completely configure your networking environment from the command line. and when i say ‘completely’ i mean ‘completely’. you can configure every aspect of … Continue reading →

a very detailed documentation of the changes in XPSP2 http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2chngs.mspx

an interesting list of ports used by various microsoft servers & services http://www.microsoft.com/smallbusiness/gtm/securityguidance/articles/ref_net_ports_ms_prod.mspx

keith brown has an online version of his new book ‘A .NET Developers Guide to Windows Security’. I can only highly recommend reading this! it rocks!!! or as bruce schneier once said on ‘hacking exposed’: ‘informational gold!’

Those you know me know that i alway favoured XML Spy for all X-related editing.Finally there is a free home edition! it include a lot of the regular product features. unfortunately the WSDL designer and SOAP debugger stay in the … Continue reading →

In Whidbey there will be a SslStream class Enables Apps to communicate over an SSL authenticated/enrypted stream Supports client and server side of SSL connection Also applies to remoting tcp/binary cool!

In Whidbey the ProcessStartInfo class has three new properties Domain Username Password This will allow to start processes under another user account whithout having to use impersonation. via shawnfa

In Whidbey you can’t disable Code Access Security by using the caspol utility…. I think this is a step in the right direction….:) …but you will still be able to change this behaviour by using a registry key SecurityManager.SecurityEnabled read more…1…2