• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

OpenSSL hardware crypto engine functionality is not available

Scheduled Pinned Locked Moved OpenVPN
4 Posts 2 Posters 2.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    bchan
    last edited by bchan Dec 2, 2023, 4:29 AM Dec 2, 2023, 4:01 AM

    I just upgraded to CE 2.7.1. When I looked at the log of OpenVPN I found the captioned message.
    In the System/Advanced/Misc setting, I have "Cryptographic Hardware" set to "AES-NI CPU based acceleration". This worked perfectly in the past.
    I am using these ciphers:
    AES-128-GCM
    AES-128-CBC

    Am I missing something in the setting in CE 2.71?
    How can I turn on hardware acceleration again?

    Thanks in advance for any advice and insights.

    T 1 Reply Last reply Dec 2, 2023, 4:22 PM Reply Quote 0
    • T
      tinfoilmatt @bchan
      last edited by Dec 2, 2023, 4:22 PM

      @bchan reboot.

      B 1 Reply Last reply Dec 4, 2023, 7:39 AM Reply Quote 0
      • B
        bchan @tinfoilmatt
        last edited by bchan Dec 4, 2023, 7:39 AM Dec 4, 2023, 7:39 AM

        @cyberconsultants The upgrade already triggered a reboot and I have not changed any setting. Why another reboot will solve the problem?

        On the other hand, I read somewhere that CPU AES-NI is considered "kernal" now in openssl. Perhaps that is the reason why it is not longer needed in OPENVPN configuration.
        I have measured both the upload and download speed and noticed no degradation even with the warning message.

        T 1 Reply Last reply Dec 4, 2023, 4:28 PM Reply Quote 0
        • T
          tinfoilmatt @bchan
          last edited by Dec 4, 2023, 4:28 PM

          @bchan you could review kernel initialization by running...

          sysctl -a
          

          ...if you want to review what might not have 'come up' properly. a subsequent reboot could then affirm or disaffirm any findings.

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received