Hello Everyone
I am going to upgrade Openssl Package* ( 0.9.8y in to 0.9.8zd) *in pfsense
2.1 release
Step 1 I have downloaded Openssl-0.9.8zd.tar.gz
Step 2 Extract Openssl-0.9.8zd.tar.gz
Step 3 cd openssl-0.9.8zd
Step4 ./config --prefix=/usr/ (Below mention error I am getting )
*cc: not
Hello Walter,
to what project from which Jim are you refering to, do you have a link?
best
- Original Message -
From: Walter Parker walt...@gmail.com
To: pfSense Support and Discussion Mailing List list@lists.pfsense.org
Sent: Tuesday, December 16, 2014 6:49:52 PM
Subject: Re:
pfsense is not distributed with a developer environment.
On Thu, Mar 26, 2015 at 5:53 AM, amit saxena amit.linux@gmail.com
wrote:
Hello Everyone
I am going to upgrade Openssl Package* ( 0.9.8y in to 0.9.8zd) *in
pfsense 2.1 release
Step 1 I have downloaded Openssl-0.9.8zd.tar.gz
Step 2
Torrent traffic: maybe with a good L7 filter (not tried this myself).
But HTTPS proxies and SSL VPN's forget about it.
It's a game of whack-a-mole. As soon as you squash one, three more will
pop-up.
You can't block SSL. You'd need to get a real web filtering solution and
by that I mean a
On Mon, Mar 23, 2015 at 9:34 AM, Christopher CUSE cc...@ccuse.com wrote:
On 03/23/2015 03:03 PM, mayak wrote:
On 03/22/2015 12:38 AM, Bryan D. wrote:
We've had a pfSense-to-pfSense always on IPsec VPN connecting 2 offices
since 2008 (pfSense 1.2 IIRC) and it's:
- been ultra reliable (if
Hello all
it is a known issue that some pfsenses generated with the update to v2.2
new ssk keys
so sshd is not accessable / service down.
it is not possible to start the service
deleting and regenerating keys doesn't help
also updte v2.2 to 2.2.1 doenstr resolved issue
has anyone a short
