best software firewall?

This does not result into the above URL.

Yours, VB.

This paper seems not to be about .NET security, but about an extra sandbox implementation, which is not part of .NET. From it:

| Our sandbox is implemented as two security layers, one on top of the | Windows API and one in the kernel.

Yours, VB.

It also talks about using .NET Remoting as a proxy between managed and unmanaged code to enforce security between them.

Duane :)

This is not the topic.

Yours, VB.

Yes, it is the topic. *NET is not secure* is the topic. The contents of the topic cannot be what you want it to be. As a matter of fact, even I have learned something from that article if I have to write secure .NET appications that deal with managed and unmanaged code in a solution.

Duane :)

We're talking about wether .NET is secure, not how to secure it in spite of being insecure.

I'm very interested in finding answers to my questions, though. Do you have some?

Yours, VB.

The bottom line is .NET is secure when it comes to running programs that are under the control of .NET, managed code. .NET has no control of unmanaged code. However, .NET has some control of unmanaged code when it comes to initiating/running unmanaged code in a .NET solution. And one can protect .NET objects by using a proxy.

You're not going to find anything else about it. If we as Human Beings were perfect, then every thing we do I would expect to be perfect. We are not perfect.

It is what it is, and I for one, I am not going to be too concerned about the security of .NET.

Duane :)

Is this true? Duane, I think, you cannot or don't want to help me. What's with other people here?

Of course.

Yours, VB.

It's not that I don't want to help you. I have taken you as far as I can take you. You'll have to cross the rest of the road yourself.

I suggest you find a .NET NG, as I don't think anyone here is really going to know the ins and outs of .NET.

Of course this is true.

I wish you the best of luck on this endeavor.

Duane :)

OK. Thanx alot! ;-)

Hm... I'll consider that.

Yours, VB.