|
| 1 | +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 2 | +<HTML> |
| 3 | + <HEAD> |
| 4 | + <TITLE> [squid-users] Hardware acceleration quest |
| 5 | + </TITLE> |
| 6 | + <LINK REL="Index" HREF="index.html" > |
| 7 | + <LINK REL="made" HREF="mailto:squid-users%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-users%5D%20Hardware%20acceleration%20quest&In-Reply-To=%3Cdd1a3c4c-389a-419a-a5a8-5dd95f3464de%40treenet.co.nz%3E"> |
| 8 | + <META NAME="robots" CONTENT="index,nofollow"> |
| 9 | + <style type="text/css"> |
| 10 | + pre { |
| 11 | + white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */ |
| 12 | + } |
| 13 | + </style> |
| 14 | + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> |
| 15 | + <LINK REL="Previous" HREF="027763.html"> |
| 16 | + |
| 17 | + </HEAD> |
| 18 | + <BODY BGCOLOR="#ffffff"> |
| 19 | + <H1>[squid-users] Hardware acceleration quest</H1> |
| 20 | + <B>Amos Jeffries</B> |
| 21 | + <A HREF="mailto:squid-users%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-users%5D%20Hardware%20acceleration%20quest&In-Reply-To=%3Cdd1a3c4c-389a-419a-a5a8-5dd95f3464de%40treenet.co.nz%3E" |
| 22 | + TITLE="[squid-users] Hardware acceleration quest">squid3 at treenet.co.nz |
| 23 | + </A><BR> |
| 24 | + <I>Fri Jan 16 07:09:25 UTC 2026</I> |
| 25 | + <P><UL> |
| 26 | + <LI>Previous message (by thread): <A HREF="027763.html">[squid-users] Hardware acceleration quest |
| 27 | +</A></li> |
| 28 | + |
| 29 | + <LI> <B>Messages sorted by:</B> |
| 30 | + <a href="date.html#27765">[ date ]</a> |
| 31 | + <a href="thread.html#27765">[ thread ]</a> |
| 32 | + <a href="subject.html#27765">[ subject ]</a> |
| 33 | + <a href="author.html#27765">[ author ]</a> |
| 34 | + </LI> |
| 35 | + </UL> |
| 36 | + <HR> |
| 37 | +<!--beginarticle--> |
| 38 | +<PRE>On 16/01/2026 05:38, Jonathan Lee wrote: |
| 39 | +><i> We use to be able to use ssl engine and set it to something like devcrypto, is there anyway to utilize any hardware acceleration with new squid versions to access something like a SafeXcel or other newer crypto chips ? |
| 40 | +</I> |
| 41 | +The change in engine support is due to OpenSSLv3 changes. So current |
| 42 | +Squid build against older OpenSSLv1.x operate the same as before. |
| 43 | + |
| 44 | +OpenSSL v3 uses "providers" instead of "engines". For now you can use |
| 45 | +openssl.conf to load any you can find with hardware acceleration. |
| 46 | + <<A HREF="https://docs.openssl.org/master/man5/config/#provider-configuration">https://docs.openssl.org/master/man5/config/#provider-configuration</A>> |
| 47 | + |
| 48 | + |
| 49 | +Cheers |
| 50 | +Amos |
| 51 | + |
| 52 | +</PRE> |
| 53 | + |
| 54 | +<!--endarticle--> |
| 55 | + <HR> |
| 56 | + <P><UL> |
| 57 | + <!--threads--> |
| 58 | + <LI>Previous message (by thread): <A HREF="027763.html">[squid-users] Hardware acceleration quest |
| 59 | +</A></li> |
| 60 | + |
| 61 | + <LI> <B>Messages sorted by:</B> |
| 62 | + <a href="date.html#27765">[ date ]</a> |
| 63 | + <a href="thread.html#27765">[ thread ]</a> |
| 64 | + <a href="subject.html#27765">[ subject ]</a> |
| 65 | + <a href="author.html#27765">[ author ]</a> |
| 66 | + </LI> |
| 67 | + </UL> |
| 68 | + |
| 69 | +<hr> |
| 70 | +<a href="https://lists.squid-cache.org/listinfo/squid-users">More information about the squid-users |
| 71 | +mailing list</a><br> |
| 72 | +</body></html> |
0 commit comments