In the abysmal depths where the mind pines ;For the delight of knowledge without which it dies.The unreachable truth, unhindered, incessantly shinesAmidst the plethora of impeccable lies.

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>

Nothing specific as such but i was just curious on something that happened recently while downloading a huge file from a site. Here goes …

Basically, i was downloading a video file of size 80MB when my system had something about 100MB left in the hard disk. I felt it was fair enough to store the file for now, view the video and then delete it to reclaim the disk space. 

But here comes the catch. When i finished downloading the huge file, the system had actually downloaded it to a temporary internet directory and then tried to copy it to the destination directory which was specified. Now why would it want to do that ??

Doing something like that would require 2 times the size of the file downloaded to be present in the hard disk. Why impart such a constraint ??? All it needs to do is to download it directly onto the destination directory. Or what could have been done is to download the file to the temporary directory and then move it, not copy to the destination directory. We know that copying a file takes much longer a time when compared to moving a file, if the destination is in the same disk. So why copy ?? But the actual implementation does neither ! Why so ?

Are there any specific security or any other implications for doing the implementation the way it has been done now ?? Any ideas ?

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>

Ok. Sorry about the recent lack of posts but will write about that in detail later … For now, enjoy these links on security.

Probably most of it here is well known already but i just wanted to consolidate all the links i found out recently about security while reading on the topic ! This one is a security special 🙂

• Improving Web Application Security: Threats and Countermeasures – This download contains guidelines for architecting, designing, building, reviewing, and configuring secure to build hack resilient ASP.NET Web applications across the application tiers, technology, and servers.
• Building Secure ASP .NET Applications – A guide which focuses on the key elements of authentication, authorization, and secure communication within and across the tiers of distributed .NET Web applications.
• Saying Goodbye to an Old Friend – by Michael Howard where he talks about the work going on to make the C runtime libraries more robust in the face of malicious data. A very nice read 🙂
• Michael Howard also points out to another eBook which talks about Secure Programming for Linux and Unix HOWTO by David A. Wheeler. And he’s got a blog too … Subscribed. Have a look at all his articles here. Not everything is applicable to Linux only. Have a look.
• Defend Your Code with Top Ten Security Tips Every Developer Must Know – by Michael Howard again !
• Threat modeling – A nice review on thread modeling tools by Jon Udell with some good links too.
• Security Policy Best Practices from GotDotNet. Read more basics at “About .NET Security”.
• A site dedicated to providing security related links to SysAdmins and Hackers. Read on …
• FoundStone, Inc has a superb site with lots of resources on securing data from many of the common threats. They also have a rich Resources section where there are several webcasts and whitepapers too …

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>

<div style="clear:both; padding-bottom: 0.25em;">
</div>

<p>
</p>