On Apr 16, 2014, at 4:34 PM, Brian Candler wrote:
> On 15/04/2014 20:12, Jim Thompson wrote:
>> We dropped the price, too.
>>
>> -- Jim
> Which price are you referring to?
On the EC2 instance(s).
> I see that a support subscription is now $200 for 2 hours plus $200 per extra
> hour.
$400 fo
On 15/04/2014 20:12, Jim Thompson wrote:
We dropped the price, too.
-- Jim
Which price are you referring to?
I see that a support subscription is now $200 for 2 hours plus $200 per
extra hour.
The one my client purchased a couple of months ago was $600 for 5 hours
and (I think) $100 per ex
On Tue, Apr 15, 2014 at 1:41 AM, Chris Buechler wrote:
> On Sun, Apr 13, 2014 at 7:33 AM, Doug Lytle wrote:
> > Jim Thompson wrote:
> >> 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.
>
There will be a blog post. I may update announce@, but my thinking on security@
is that it is for notices.
We dropped the price, too.
-- Jim
> On Apr 13, 2014, at 22:21, linbloke wrote:
>
>
> Thanks Jim. There's still no sign of them in the AWS AMI public images
> library. Can you post th
>> Perhaps the bigger question here is "why isn't the OP using v6?" :-)
My ISP doesn't support it and I have no need for it at this time, it being a
home network.
Doug
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listi
On 14/4/14 5:11 pm, cbr wrote:
I don't believe you can completely disable IPv6 via webUI of pfSense
Perhaps the bigger question here is "why isn't the OP using v6?" :-)
Kind regards,
Chris
--
This email is made from 100% recycled electrons
___
List
Chris Buechler wrote:
> The "now I notice" being the key part there. Nothing related to that's
> changed. If you don't check "Allow IPv6" under System>Advanced, you
> have a block all rule on IPv6 with logging. Things on your LAN will
> have link local addresses and spew multicast stuff. Probably w
Seth Mos wrote:
> Also, if you've been using the 2.1 snapshots in 2012 and 2013 the config
> will had that setting enabled, which corresponds with your firewall
> logs. Maybe you have a upgraded config.
Thanks for the response,
I've only been using pfSense since last November. I'll review my
se
On 15-4-2014 7:41, Chris Buechler wrote:
> On Sun, Apr 13, 2014 at 7:33 AM, Doug Lytle wrote:
>> Jim Thompson wrote:
>>> 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.
>>
>> Okay,
>
On Sun, Apr 13, 2014 at 7:33 AM, Doug Lytle wrote:
> Jim Thompson wrote:
>> 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.
>
> Okay,
>
> I've just upgraded from 2.1.1 to 2.1.2, now I noti
Hey Jim,
The addresses in your message are all link-local IPv6 addresses -
http://en.wikipedia.org/wiki/Link-local_address#IPv6
Any interface with IPv6 enabled stack on any device on the network will have a
link-local address (does not need to have a routable address assigned!)
Check the interfa
Thanks Jim. There's still no sign of them in the AWS AMI public images
library. Can you post the AMI IDs here or to the security announce list
when they're available please?
Kind regards,
lb
On 12/04/2014 4:19 pm, Jim Thompson wrote:
They're built; we're waiting on Amazon.
-- Jim
On Apr
Jim Thompson wrote:
> 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.
Okay,
I've just upgraded from 2.1.1 to 2.1.2, now I notice that my firewall
logs are being spammed with IPV6 ICMP noti
> On Apr 12, 2014, at 18:55, Volker Kuhlmann wrote:
>
>> On Fri 11 Apr 2014 18:43:18 NZST +1200, Ryan Coleman wrote:
>>
>> He gave you an option to subscribe to the list.
>
> You seem to have missed the point I was making: critical security fixes
> (the 2.1.2 release in this case, unless I am
On Fri 11 Apr 2014 18:43:18 NZST +1200, Ryan Coleman wrote:
> He gave you an option to subscribe to the list.
You seem to have missed the point I was making: critical security fixes
(the 2.1.2 release in this case, unless I am misunderstanding) were not
posted to security-announce@.
The posting
They're built; we're waiting on Amazon.
-- Jim
> On Apr 11, 2014, at 22:41, linbloke wrote:
>
>
>> On 11/04/2014 5:23 am, Jim Thompson wrote:
>> 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
On 11/04/2014 5:23 am, Jim Thompson wrote:
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.
Thanks for the new release. Any sign of updated AWS AMIs?
Reg
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
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
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
29 matches
Mail list logo
