Re: Passwordless accounts vi ports!

Olivier, I've checked my 10.3Stable systems and they all have '*' as their password, which is consistent with /usr/ports/Mk/UIDs. You might like to check the age of the latter. Regards, Dewayne. PS Both ports and src were built from updated src and ports from 2016-08-09

Re: Passwordless accounts vi ports!

Hi! > I just checked the security scanning outputs of FreeBSD and found this > surprising result: > > [...] > Checking for passwordless accounts: > polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin > pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin >

Re: Passwordless accounts vi ports!

> On Aug 10, 2016, at 22:05, O. Hartmann wrote: > > I just checked the security scanning outputs of FreeBSD and found this > surprising result: > > [...] > Checking for passwordless accounts: > polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin >

Passwordless accounts vi ports!

I just checked the security scanning outputs of FreeBSD and found this surprising result: [...] Checking for passwordless accounts: polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin

Re: freebsd-update and portsnap users still at risk of compromise

On 11/08/2016 1:11 AM, Mail Lists via freebsd-security wrote: sorry but this is blabla and does not come even near to answering the real problem: It appears that freebsd and the US-government is more connected that some of us might like: Not publishing security issues concerning update

Re: [HEADSUP] extracting LoadModule out of httpd.conf

Mathieu Arnold wrote on 08/10/2016 17:42: Hi, It is coming. https://reviews.freebsd.org/D7460 constructive comments welcome. I don't think I will do that for Apache 2.2 because it expires at the end of the year. I agree that there are problems with LoadModule lines in httpd.conf. Because

PO#: 001238

- This mail is in HTML. Some elements may be ommited in plain text. - Hello, You have received PO#: 001238 from POSH COMPANY LLC, that were uploaded to you through the WeTransfer. use the link below to download the Purchase Order on Adobe Pdf. CLICK HERE WeTransfer Plus!

Re: Mosh regression between 10.x and 11-stable

On 8/10/16 4:18 AM, Peter Jeremy wrote: > I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 > r303811 and mosh to that host from my Linux laptop stopped working. All > I get on the laptop is: > $ mosh remotehost > Connection to remotehost closed. > /usr/bin/mosh: Did not

Re: Outdated port of antimicro

Hi! > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211712 Committed, thanks very much! -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-ports@freebsd.org mailing list

Re: Mosh regression between 10.x and 11-stable

On 8/10/16 4:18 AM, Peter Jeremy wrote: > I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 > r303811 and mosh to that host from my Linux laptop stopped working. All > I get on the laptop is: > $ mosh remotehost > Connection to remotehost closed. > /usr/bin/mosh: Did not

Re: [HEADSUP] extracting LoadModule out of httpd.conf

https://reviews.freebsd.org/D7460 constructive comments welcome. Would be nice if dialog were able to disable/enable modules after choosing them for installation. An installed but disabled module would still, in this design, write a file to modules.d but the LoadModule line would be commented.

Re[2]: freebsd-update and portsnap users still at risk of compromise

sorry but this is bullshit and does not come even near to answering the real problem: It appears that freebsd and the US-government is more connected that some of us might like: Not publishing security issues concerning update mechanisms - we all can think WHY freebsd is not eager on this

Re[2]: freebsd-update and portsnap users still at risk of compromise

sorry but this is blabla and does not come even near to answering the real problem: It appears that freebsd and the US-government is more connected that some of us might like: Not publishing security issues concerning update mechanisms - we all can think WHY freebsd is not eager on this

[HEADSUP] extracting LoadModule out of httpd.conf

Hi, It is coming. https://reviews.freebsd.org/D7460 constructive comments welcome. I don't think I will do that for Apache 2.2 because it expires at the end of the year. -- Mathieu Arnold pgpz9ojhzgQlv.pgp Description: PGP signature

Re: freebsd-update and portsnap users still at risk of compromise

On Wed, Aug 10, 2016 at 09:50:37AM +0100, Big Lebowski wrote: > On Tue, Aug 9, 2016 at 9:21 PM, Matthew Donovan > wrote: > > > You mean operating system as distribution is a Linux term. There's not much > > different between HARDENEDBSD and FreeBSD besides that HardenedBSD

Re: freebsd-update and portsnap users still at risk of compromise

> On 10 Aug 2016, at 10:50 AM, Big Lebowski wrote: > > With all due respect :) Not really. Feel free to try again. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To

Re: freebsd-update and portsnap users still at risk of compromise

On Tue, Aug 9, 2016 at 9:21 PM, Matthew Donovan wrote: > You mean operating system as distribution is a Linux term. There's not much > different between HARDENEDBSD and FreeBSD besides that HardenedBSD fixes > vulnerabilities and has a an excellent ASLR system compared to

Mosh regression between 10.x and 11-stable

I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 r303811 and mosh to that host from my Linux laptop stopped working. All I get on the laptop is: $ mosh remotehost Connection to remotehost closed. /usr/bin/mosh: Did not find mosh server startup message. I've tried

Re: Clamd core dumps

10.08.16 15:47, Kubilay Kocak пишет: > Change should also be MFH'd if the quarterly version is affected > Done by r419990, r419991 > On 10 Aug 2016, at 12:26 PM, Renato Botelho > wrote: > >> Thanks! Please go ahead and commit it. >> >> >> Em