Well: https://www.netgate.com/blog/pfsense-2-5-and-aes-ni.html so we are talking about 2.5 not 3.x ?
"While we’re not revealing the extent of our plans, we do want to give early notice that, in order to support the increased cryptographic loads that we see as part of pfSense verison 2.5, pfSense Community Edition version 2.5 will include a requirement that the CPU supports AES-NI. On ARM-based systems, the additional load from AES operations will be offloaded to on-die cryptographic accelerators, such as the one found on our SG-1000 <https://www.netgate.com/products/sg-1000.html>. ARM v8 CPUs include instructions like AES-NI <https://www.arm.com/files/downloads/ARMv8_Architecture.pdf> that can be used to increase performance of the AES algorithm on these platforms." Eero On Thu, Feb 15, 2018 at 7:18 PM, Edwin Pers <[email protected]> wrote: > I believe I read somewhere that the new version that requires aes-ni will > be 3.x, and they plan to continue the 2.x line alongside it, as 3.x will be > a major rewrite > > > -Ed > > -----Original Message----- > From: List [mailto:[email protected]] On Behalf Of Eero > Volotinen > Sent: Thursday, February 15, 2018 12:14 PM > To: Kyle Marek <[email protected]> > Cc: pfSense Support and Discussion Mailing List <[email protected]> > Subject: Re: [pfSense] Configs or hardware? > > Well. Next version of pfsense (2.5) will not install into hardware that > does not support AES-NI, so buying such hardware is not wise ? > > Eero > > > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
