-
|
Assuming I have a well-configured OpenSSL Engine in my Linux Ubuntu 20.04.5 system - And this is my So, considering the engine is working, if I implement a HTTPS proxy server using Yarp, may I assume the .net/OpenSSL stack would automatically offload crypto requests to the OpenSSL Engine? If not, how can I configure Yarp to do that? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
|
cc: @wfurt |
Beta Was this translation helpful? Give feedback.
-
|
There is no setting for engines or other HW in .NET. And we certainly don't have any test coverage. dotnet/runtime#37383 is still open but it may work if the initialization is done by openssl itself. My suggestion would be to create simple app with |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply and comments @wfurt I'll give that a try and see what I get. For some reason, with the above
|
Beta Was this translation helpful? Give feedback.
-
|
cc: @bartonjs in case he has some more insight. Getting hands on some HW is on my TODO list. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I did these tests and notice some issues with dotnet. First, I ran this command:
and looked for Then I get this simple program and ran it: using System.Diagnostics;
using System.Net.Security;
using System.Net.Sockets;
namespace TLSTest
{
public static class Program
{
public static async Task Main(string[] args)
{
if(args.Length == 0)
{
Console.WriteLine("Use: TLSTTest host_name");
return;
}
Stopwatch stopwatch = Stopwatch.StartNew();
var targetHost = args[0];
Console.WriteLine($"Testing {targetHost}");
using TcpClient tcpClient = new TcpClient();
await tcpClient.ConnectAsync(targetHost, 443);
using SslStream sslStream = new SslStream(tcpClient.GetStream());
try
{
await sslStream.AuthenticateAsClientAsync(targetHost);
await Console.Out.WriteLineAsync($"Connected to {targetHost} with {sslStream.SslProtocol}");
await Console.Out.WriteLineAsync($"Elapsed time = {stopwatch.ElapsedMilliseconds}");
}
catch(Exception Ex)
{
Console.WriteLine($"Exception = {Ex.Message}\n\nHResult = {Ex.HResult}\n\nInner Exception = {Ex.InnerException}");
}
}
}
}Output Looked again for both These tests were run with no OpenSSL Engine configured; and since dotnet is producing these errors when trying to load OpenSSL, that might be the root cause for the engine to fail loading when configured. Any ideas? OpenSSL |
Beta Was this translation helpful? Give feedback.
-
|
That is not necessarily problem as the |
Beta Was this translation helpful? Give feedback.
-
|
Hi @wfurt That makes sense. In either case, I repeated all the above tests, this time enabling the engine. Again, After googling similar loading issues, I found a simple solution: Using Thanks for taking the time for answering my questions and comments. Cheers. |
Beta Was this translation helpful? Give feedback.
-
|
The interesting question is if you see differences in loading and using the engine. |
Beta Was this translation helpful? Give feedback.
-
|
Will answer that as soon as I get some data and after tuning BIOS and engine settings for best performance :) |
Beta Was this translation helpful? Give feedback.
There is no setting for engines or other HW in .NET. And we certainly don't have any test coverage. dotnet/runtime#37383 is still open but it may work if the initialization is done by openssl itself.
I'm planning to take closer look at dotnet/runtime#66224 and perhaps engines as well for 8.0
My suggestion would be to create simple app with
SslStreamand give it try. When you look at the operations withstraceit should be clear. You can also create self-contained app (to limit noise) and doLD_DEBUG=libs maApp. That would show you what libraries are loaded and you can check if the engine is there.You can also run https://github.com/dotnet/performance and see if there is difference. I wou…