He gave you an option to subscribe to the list.
Do what I’m going to do: Subscribe.
On Apr 10, 2014, at 5:52 PM, Volker Kuhlmann wrote:
> On Fri 11 Apr 2014 09:27:07 NZST +1200, Jim Thompson wrote:
>
>> It was posted on announce@, but it seems that I’m moderated there. This
>> is why my 2.1.
On Fri 11 Apr 2014 12:11:06 NZST +1200, Jeremy Porter wrote:
> The security@ email list is brand new. Its so we can announce
> issues like Heartbleed. People can filter on it etc.
> Any security issues we become aware of will be announce here, as
> security advisories.
Perhaps it would be usefu
It's much appreciated, thanks guys. Well done! :)
On 04/11/2014 09:18 AM Mehma Sarja wrote:
Thanks go out to Chris, Jim and the whole pfSense team for what must be
back breaking work coming on the heels of the 2.1.1 release! This kind of
commitment speaks volumes for the quality of products comi
+1
--
Ryan Coleman
ryanjc...@me.com
m. 651.373.5015
o. 612.568.2749
> On Apr 10, 2014, at 20:18, Mehma Sarja wrote:
>
> Thanks go out to Chris, Jim and the whole pfSense team for what must be back
> breaking work coming on the heels of the 2.1.1 release! This kind of
> commitment speaks volum
Thanks go out to Chris, Jim and the whole pfSense team for what must be
back breaking work coming on the heels of the 2.1.1 release! This kind of
commitment speaks volumes for the quality of products coming out of
Netgate.
Yudhvir
___
List mailing list
L
On 4/10/2014 5:52 PM, Volker Kuhlmann wrote:
On Fri 11 Apr 2014 09:27:07 NZST +1200, Jim Thompson wrote:
It was posted on announce@, but it seems that I’m moderated there. This
is why my 2.1.1 release announcement was also held. I’ve pushed the message
through.
Setup glitches. Thanks!
se
On Fri 11 Apr 2014 09:27:07 NZST +1200, Jim Thompson wrote:
> It was posted on announce@, but it seems that I’m moderated there. This
> is why my 2.1.1 release announcement was also held. I’ve pushed the message
> through.
Setup glitches. Thanks!
> security@ is for posting SAs
Uhhmm, IMHO I
On Apr 10, 2014, at 4:25 PM, Dimitri Rodis
wrote:
> Can we also get information as to which versions of pfSense are affected
> aside from 2.1.1? Or is 2.1.1 the only affected version?
https://pfsense.org/security/advisories/pfSense-SA-14_04.openssl.asc
___
On Apr 10, 2014, at 4:10 PM, Volker Kuhlmann wrote:
> On Fri 11 Apr 2014 07:23:52 NZST +1200, Jim Thompson wrote:
>
>> pfSense release 2.1.2 is now available.
>
> Thank you for all the quick work!
>
> May I ask though why this isn't simultaneously posted on
> pfsense-announce and pfsense-secu
Can we also get information as to which versions of pfSense are affected aside
from 2.1.1? Or is 2.1.1 the only affected version?
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
On Fri 11 Apr 2014 07:23:52 NZST +1200, Jim Thompson wrote:
> pfSense release 2.1.2 is now available.
Thank you for all the quick work!
May I ask though why this isn't simultaneously posted on
pfsense-announce and pfsense-security-announce? In particular, if the
security-announce list was to be
On 10/04/2014 21:13, kol wrote:
> How do you revoke a CA certifate?
Export the CRL from whatever you use to manage your CA (I use TinyCA,
I've no experience of using pfSense, this whole thing might well be even
easier if you use pfSense).
In pfSense:
System -> Cert Manager -> Certificate Revoca
How do you revoke a CA certifate?
-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Jim Thompson
Sent: Thursday, April 10, 2014 3:24 PM
To: pfSense Support and Discussion Mailing List
Subject: [pfSense] pfSense 2.1.2 is released
https://blog.pfsense.org/
Excellent work!!
-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Jim Thompson
Sent: Thursday, April 10, 2014 3:24 PM
To: pfSense Support and Discussion Mailing List
Subject: [pfSense] pfSense 2.1.2 is released
https://blog.pfsense.org/?p=1253
pfSense r
https://blog.pfsense.org/?p=1253
pfSense release 2.1.2 is now available. pfSense release 2.1.2 follows less
than a week after pfSense release 2.1.1, and is primarily a security release.
The Heartbleed OpenSSL bug and another OpenSSL bug which enables a side-channel
attack are both covered by
just the right time for me :)
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
Am 10.04.2014 02:12, schrieb Jan:
> Chris,
>
> any idea on the schedule?
>
> Cheers
>
> On 04/09/2014 05:03 PM Chris Buechler wrote:
>> Scratch that - that just missed a commit for another security fix,
>> it's rebuilding now.
>>
>> On Wed, Apr 9, 2014 at 3:48 AM, Chris Buechler wrote:
>>> Normall
The final testing (testing updates against the real update servers, which can’t
be effectively simulated) is happening now.
jim
On Apr 10, 2014, at 12:50 PM, k_o_l wrote:
> Any update to when the fix will be released?!
>
> -Original Message-
> From: List [mailto:list-boun...@lists
Any update to when the fix will be released?!
-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Chris
Buechler
Sent: Wednesday, April 09, 2014 5:04 AM
To: pfSense support and discussion
Subject: Re: [pfSense] 2.1.2-RELEASE up for testing
Scratch that - tha
Just a shot in the wild.
Did you have state killing disabled in the setup?
Otherwise more information is needed on this.
Normally apinger should be way better on 2.1 that it was on 2.0 because a
lot of work went into that.
On Thu, Apr 10, 2014 at 6:27 PM, Raimund Sacherer wrote:
>
> - "Ra
- "Raimund Sacherer" wrote:
>
> Hello,
>
> I installed on the weekend our new firewall system. It consists of two Dell
> R210 with intel (igb) 2-port interface cards.
>
> The old system was 2.0-RELEASE.
>
> We have 11 Gateways configured, it's a mix of WAN's and LAN-Type
> interconn
21 matches
Mail list logo
