News for hackers. Stuff that matters.
Re:PfSense 2.5 and AES-NI by givemefive on Monday May 01, 2017 @02:01PM (#14239878)
Sounds like a move to sell more hardware. My pfsense barely does any crypto. This will push me over to openbsd.
Re:PfSense 2.5 and AES-NI by gonzo on Monday May 01, 2017 @02:06PM (#14239908)
If this was a move to sell more hardware, why wouldn't we make the decision for 2.4 (which is imminent) rather than 2.5, which is based on FreeBSD 12, when 12.0R isn't even scheduled?
Re:PfSense 2.5 and AES-NI by givemefive on Monday May 01, 2017 @02:30PM (#14240158)
I don't know. What is your reasoning? I don't really understand why you'd want to force people to upgrade HW when they don't need to.
Re:PfSense 2.5 and AES-NI by tptacek on Monday May 01, 2017 @02:57PM (#14240409)
There is a difference between a design decision reasonable people can disagree, even forcefully, about, and a design decision that is actually a deceptive attempt to get people to buy new hardware.
Re:PfSense 2.5 and AES-NI by acdha on Monday May 01, 2017 @03:59PM (#14240945)
They spelled out the reasoning in the post:

“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”

You may disagree with that but it's intellectually dishonest to argue as if they didn't provide clear, technically defensible rationale, especially at a time when much of the industry has been moving to hardware offload.

Re:PfSense 2.5 and AES-NI by SaltySolomon on Monday May 01, 2017 @02:41PM (#14240256)
Wait, your argument is that isn't a way to sell more hardware is that you will do it later, not now?
Re:PfSense 2.5 and AES-NI by gonzo on Monday May 01, 2017 @03:30PM (#14240683)
If we only allowed people to load pfSense on hw that we sell,or have sold, you would have a point.

Since we don't even attempt same, my point stands.

Re:PfSense 2.5 and AES-NI by Gamblore on Monday May 01, 2017 @04:54PM (#14241473)
That point no makes sense as this decision cuts out a lot of the cheaper hardware people ran pfSense on previously so when they look at their options now your own lower priced stuff becomes more attractive and oh yes it has AES-NI and is fully compatible.

This really feels like a long con to get people to upgrade their hardware to a pfSense unit.

Re:PfSense 2.5 and AES-NI by dom0 on Monday May 01, 2017 @02:05PM (#14239900)
Indeed, AES-NI is very rare. Few computers if any have it.

Edit: /s ... ?!

Re:PfSense 2.5 and AES-NI by kbenson on Monday May 01, 2017 @02:22PM (#14240067)
> Edit: /s ... ?!

Why are you surprised? If you are trying to make a point that AES-NI is common, just say so. Trying to do so by saying the opposite and expecting people will pick up on the sarcasm through a pure text medium without necessarily sharing the same knowledge to know whether that statement is true or not just adds confusion to the conversation.

The point itself is useful, but the manner in which you expressed it emphasizes the delivery over the content, to the degree the content is sometimes obscured.

Re:PfSense 2.5 and AES-NI by paws on Monday May 01, 2017 @02:12PM (#14239979)
Why do you say that? According to [1], AES-NI is not that rare.

[1] https://en.wikipedia.org/wiki/AES_instruction_set

Re:PfSense 2.5 and AES-NI by throwa38282 on Monday May 01, 2017 @02:11PM (#14239968)
I might be mistaken, but I thought it was in every non pentium/celeron/atom chip after 2010 and every chip after 2015 with some extensions.

My desktop and laptop have them and they're mid-high end but not upper high end.

Re:PfSense 2.5 and AES-NI by gonzo on Monday May 01, 2017 @02:16PM (#14240007)