BeginAuthenticateAsClient 在新的 AppDomain 中不起作用

发布于 2024-12-29 12:39:51 字数 1867 浏览 2 评论 0原文

我正在尝试在新的 AppDomain 中创建一个 SslStream 对象。但是，在流上运行 BeginAuthenticateAsClient 方法会导致抛出异常。

internal class SslWrapper : MarshalByRefObject
{
    public void CreateStream(Stream innerStream)
    {
        var ioStream = new SslStream(innerStream, 
                                     false,
                                     ValidateRemoteCertificate,
                                     SelectLocalCertificate);

        ioStream.BeginAuthenticateAsClient("Target",
                                           GetCertificates(),
                                           SslProtocols.Tls,
                                           false,
                                           new AsyncCallback(CallbackMethod), 
                                           null);
    }

    private void CallbackMethod(IAsyncResult result)
    {
        // TODO: handle callback...
    }
}

例外情况指出：

Assembly System 中的类型 System.Net.AsyncProtocolRequest、Version=2.0.0.0、Culture=neutral、PublicKeyToken=b77a5c561934e089 未标记为可序列化。

编辑：调用BeginAuthenticateAsClient()后抛出异常。调用了 SelectLocalCertificate() 回调方法，但未调用 ValidateRemoteCertificate()。

新的 AppDomain 和 SslWrapper 创建如下：

_appDomain = AppDomain.CreateDomain(name, null, new AppDomainSetup { PrivateBinPath = pathToDll });
_wrapper = (SslWrapper)_appDomain.CreateInstanceFromAndUnwrap(pathToDll, typeof(SslWrapper).FullName);
_wrapper.CreateStream(innerStream);

使用同步 AuthenticateAsClient() 可以成功工作，就像在默认情况下运行异步代码一样应用程序域。

我假设该异常与 AsyncCallback 方法有关。但是，此方法不应跨越 AppDomain 边界，那么为什么我会收到异常？更重要的是，有可能避免吗？

我使用的是.NET 2，WinXP 64位。

编辑：这也是 .NET 4 中的问题。

原文

I am trying to create an SslStream object in a new AppDomain. However, running the BeginAuthenticateAsClient method on the stream causes an Exception to be thrown.

internal class SslWrapper : MarshalByRefObject
{
    public void CreateStream(Stream innerStream)
    {
        var ioStream = new SslStream(innerStream, 
                                     false,
                                     ValidateRemoteCertificate,
                                     SelectLocalCertificate);

        ioStream.BeginAuthenticateAsClient("Target",
                                           GetCertificates(),
                                           SslProtocols.Tls,
                                           false,
                                           new AsyncCallback(CallbackMethod), 
                                           null);
    }

    private void CallbackMethod(IAsyncResult result)
    {
        // TODO: handle callback...
    }
}

The exception states:

The type System.Net.AsyncProtocolRequest in Assembly System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 is not marked as serializable.

Edit: The exception is thrown after calling BeginAuthenticateAsClient(). The SelectLocalCertificate() callback method is called, but ValidateRemoteCertificate() is not.

The new AppDomain and SslWrapper are created as follows:

_appDomain = AppDomain.CreateDomain(name, null, new AppDomainSetup { PrivateBinPath = pathToDll });
_wrapper = (SslWrapper)_appDomain.CreateInstanceFromAndUnwrap(pathToDll, typeof(SslWrapper).FullName);
_wrapper.CreateStream(innerStream);

Using the synchronous AuthenticateAsClient() instead works successfully, as does running the asynchronous code in the default AppDomain.

I assume the exception is related to the AsyncCallback method.
However, this method should not be crossing the AppDomain boundary, so why might I be getting the exception? More importantly, is it possible to avoid it?

I am using .NET 2, WinXP 64bit.

Edit: This is also a problem in .NET 4.

分享到QQ

分享到微博