2.2.2 - one opened bug as of right now
-
It's almost here!
-
actually that one can probably be closed as it appears some commits were made a while ago and atleast one person confirmed it to be working.
-
Looks like it has been closed, 100%!
-
When I saw this thread, I thought "what one is left" as I'd finished pre-release testing and was about to bump to -RELEASE. I'd verified that a few days ago and had forgotten to mark it resolved.
Release building now, after which final release testing starts, which is generally a couple day process.
The most recent 2.2.2 snapshot @ snapshots.pfsense.org should be more or less identical to release (only version # changed probably), for those who can help test.
-
@cmb:
When I saw this thread, I thought "what one is left" as I'd finished pre-release testing and was about to bump to -RELEASE. I'd verified that a few days ago and had forgotten to mark it resolved.
Release building now, after which final release testing starts, which is generally a couple day process.
The most recent 2.2.2 snapshot @ snapshots.pfsense.org should be more or less identical to release (only version # changed probably), for those who can help test.
Is PPTP removed?
-
nope its still there …. they'll remove it in 2.3.x
-
nope its still there …. they'll remove it in 2.3.x
Actually this one interest me.. why?
I'm well aware of the security issues with PPTP (not a new issue, have been discussed in the security community for decades) but this may or may not be a real problem in a specific installation, there can be technical reasons for someone running a PPTP interface internally somewhere where the problems PPTP vs security is not an issue.
There are lots of systems in businesses that may be totally isolated network segments that may have old "insecure" designs internally and old protocols in use. Whether or not that's an issue depends on lots of factors including financially. If you have a bunch of PCs set up to monitor machines somewhere and they are not networked further then network base threats don't apply the same as to other PCs etc.
I suppose that this is a way of hindering the average sysadmin making the mistake of using PPTP where it would expose the communication to real risks and there's also a risk of someone simply being lazy and deploying it since it's so easy.
Still… it perhaps should be available behind a few red angry pop-ups asking the admin if he knows what he's doing.
-
because ESF wishes to spend their time more useful on other things that are more relevant (in their eyes) at this point in time. That's why they'll remove it from pfSense-base and leave it up to the community.
anyone could potentially create a 'pptp server' addon package for pfSense after 2.3.x, that could be installed by webgui. so it'll all depend if someone wishes to spend the time and effort to keep supporting pptp