On Tue, Mar 26, 2019 at 08:07:48PM +0100, Bradley T. Hughes wrote:
>
>
> On 2019-03-26 19:07, Jonathan Chen wrote:
> > On Wed, 27 Mar 2019 at 00:24, Bradley T. Hughes wrote:
> >> On 2019-03-26 03:14, bob prohaska wrote:
> >>> On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote:
>
On 2019-03-26 19:07, Jonathan Chen wrote:
On Wed, 27 Mar 2019 at 00:24, Bradley T. Hughes wrote:
On 2019-03-26 03:14, bob prohaska wrote:
On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote:
Looks like you need to upgrade www/libnghttp2 as well. :)
Thanks for reading, I'd
On 2019-03-26 16:29, bob prohaska wrote:
On Tue, Mar 26, 2019 at 12:22:08PM +0100, Bradley T. Hughes wrote:
On 2019-03-26 03:14, bob prohaska wrote:
On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote:
[snip]
Looks like you need to upgrade www/libnghttp2 as well. :)
On Wed, 27 Mar 2019 at 00:24, Bradley T. Hughes wrote:
> On 2019-03-26 03:14, bob prohaska wrote:
> > On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote:
^~~~
> [snip]
>
> Looks like you need to upgrade www/libnghttp2 as well. :)
>
> > Thanks for reading,
Just came across that about 4 mos ago. :) Seemed like the next generation of
tighter security for pfSense.
So, HardenedBSD is fork of FreeBSD that is pushing in more defense
(passive/active) into all the FreeBSD derivatives? Very cool. Nicer to have
something that only has 20 or so CVEs
I'm not really a compliance guru, so I can't say whether HardenedBSD
comes closer to . I have looked into
Common Criteria/NIAP briefly for US Federal Government deployments in
certain high-security enclaves. HardenedBSD does come closer with
CC/NIAP, though there are still gaps to fill.
Have you
Sorry for the top-post.
Shawn,
It seems that NIST, FIPS 140-2, and things along those lines are quickly
becoming a complete reality for all people dealing with the US Gov't no matter
what the size company.
So, encryption modules must be FIPs approved for compliance and NIST 800-171 is
the
On Tue, Mar 26, 2019 at 05:02:48PM +, Paul Pathiakis via freebsd-ports
wrote:
> https://www.open-scap.org/
>
> Hi all,
>
> It's the US NIST scanner for operating system compliance.
>
> I'd like to use FreeBSD and FreeNAS in various places but it has to pass
> compliance.
I just asked my
https://www.open-scap.org/
Hi all,
It's the US NIST scanner for operating system compliance.
I'd like to use FreeBSD and FreeNAS in various places but it has to pass
compliance.
Thank you
___
freebsd-ports@freebsd.org mailing list
On Tue, Mar 26, 2019 at 12:22:08PM +0100, Bradley T. Hughes wrote:
>
>
> On 2019-03-26 03:14, bob prohaska wrote:
> > On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote:
> [snip]
>
> Looks like you need to upgrade www/libnghttp2 as well. :)
>
> > Thanks for reading, I'd be
> On Mar 23, 2019, at 4:07 PM, Dmitri Goutnik wrote:
>
>> On 19-03-23 15:38:14, Lucas Nali de Magalhães wrote:
>>
>> lang/go14 doesn't build in FreeBSD 12 without COMPAT11 in the kernel because
>> of the inode 64bit extension was added in the kernel. lang/go needs go14 to
>> compile and will
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236801
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 3/26/19 7:14 AM, Walter Schwarzenfeld wrote:
> rust misses libgit2.so.0.27.8 needs version bump after update of libgit2
> to 0.28.1.
Also kf5-ktexteditor; 'pkg check -d' is usually good at finding these,
imb
___
freebsd-ports@freebsd.org
On 2019-03-26 03:14, bob prohaska wrote:
On Mon, Mar 25, 2019 at 10:23:26PM +0100, Bradley T. Hughes wrote:
Hi Bob!
On 2019-03-23 22:39, bob prohaska wrote:
Recent attempts to compile www/node using 11-Stable on an rpi2
fail with
../src/node_file.cc:2023:15: error: use of undeclared
rust misses libgit2.so.0.27.8 needs version bump after update of libgit2
to 0.28.1.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
Hi,
I'm working on separating net/tigervnc into -server and -client.
If you're a user of TigerVNC, I'd appreciate if you test/review my changes.
Also Java version of vncviewer will be added later.
https://reviews.freebsd.org/D19709
I'd like to commit this before next quarterly branch is
17 matches
Mail list logo