Date: Thu, 4 Feb 2021 14:25:30 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Peter Eriksson <pen@lysator.liu.se>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Any ideas on this bug related to aesni + sha? Message-ID: <YQXPR0101MB0968E799558BD6368D29D8D9DDB39@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <EE31EDF6-012C-4313-8603-EF16979F8B95@lysator.liu.se> References: <EE31EDF6-012C-4313-8603-EF16979F8B95@lysator.liu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Crypto is way out of my area of expertise. Anyone have ideas on this? Thanks, rick ________________________________________ From: Peter Eriksson <pen@lysator.liu.se> Sent: Thursday, February 4, 2021 6:56 AM To: Rick Macklem Subject: Have you seen this bug? CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp@uoguelph.ca https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251462 This sounds like a bug in the in-kernel crypto stuff and not NFS/krb5i per se, but still.. Currently we’re not afflicted by it since our FreeBSD servers don’t have the SHA acceleration support - but we’re starting to discuss what servers to get for our next generation and then it might become a problem… - Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968E799558BD6368D29D8D9DDB39>