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.=0A= Anyone have ideas on this?=0A= =0A= Thanks, rick=0A= =0A= ________________________________________=0A= From: Peter Eriksson <pen@lysator.liu.se>=0A= Sent: Thursday, February 4, 2021 6:56 AM=0A= To: Rick Macklem=0A= Subject: Have you seen this bug?=0A= =0A= CAUTION: This email originated from outside of the University of Guelph. Do= not click links or open attachments unless you recognize the sender and kn= ow the content is safe. If in doubt, forward suspicious emails to IThelp@uo= guelph.ca=0A= =0A= =0A= https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251462=0A= =0A= This sounds like a bug in the in-kernel crypto stuff and not NFS/krb5i per = se, but still.. Currently we=92re not afflicted by it since our FreeBSD ser= vers don=92t have the SHA acceleration support - but we=92re starting to di= scuss what servers to get for our next generation and then it might become = a problem=85=0A= =0A= - Peter=0A= =0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968E799558BD6368D29D8D9DDB39>