Advanced .NET remoting

Advanced .NET Remoting

Volumn , Issue , 2005, Pages 1-579

  Rammer, Ingo ^a   Szpuszta, Mario ^b  

^a Thinktecture ^*  (Germany)

^b Developer and Platform Group of Microsoft Austria   (Austria)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892102919     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-1-4302-0011-6     Document Type: Book

References (10)

1. For more information about threat modeling, take a look at Michael Howard and David LeBlanc's Writing Secure Code, Second Edition (Microsoft Press, 2002)
2. or Frank Swiderski and Window Snyder's Threat Modeling (Microsoft Press, 2004).
3. Going into details of code access security would definitely require a book on its own. One of the best references for code access security I know is the book. NET Framework Security by Brian A. LaMacchia et al. (Addison-Wesley, 2002). For now, it is enough to know that code access security enables you to give permissions to code based on evidence like author, digital signature of the code, assembly origin, assembly name, or assembly version.
4. Hint: you can get free certificates for development purposes from VeriSign (http://www.verisign.com).
5. You can also download and install the IIS resource kit from http://www.microsoft.com/downloads, which includes a tool called selfssl.exe that can be used for creating a SSL certificate as well as enabling SSL on IIS with just one step. SelfSSL is intended for installing SSL on development and/or test machines.
6. Genuine Channels is an independently developed product. The author has no relationship with this company. You can reach them at http://www. genuinechannels.com.
7. If you are interested in more details, I'd recommend having a look at the book Pro. NET 1.1 Network Programming, Second Edition by Christian Nagel et al. (Apress, 2004).
8. Free from http://www.pocketsoap.com.
9. You can get this tcpTrace tool at http://www.pocketsoap.com.
10. The following was inspired by a blog post by my friend Richard Blewett at http://staff.develop.com/richardb/weblog.