As interesting as this thread has been (not!), let me remind everybody
that the cheapest, easiest and most efficient and profitable way
for a Nation State Actor to trojan the FreeBSD code-base, is to
assign an employee to a deniable job, and have them become a FreeBSD
committer.
No amount of crypt
On Sat, 2 Jan 2021 08:40:55 +0300
Rozhuk Ivan wrote:
> On Sat, 2 Jan 2021 06:33:55 +0100
> "Hartmann, O." wrote:
>
> > Colour settings seem to be broken since a couple of months. Out of
> > the blue, coloured kernel messages vanished - this problem is on 12
> > as well as CURRENT (we're running
On Sat, 2 Jan 2021 06:33:55 +0100
"Hartmann, O." wrote:
> Colour settings seem to be broken since a couple of months. Out of
> the blue, coloured kernel messages vanished - this problem is on 12
> as well as CURRENT (we're running 12.2-RELENG, 12-STABLE and CURRENT).
>
I do no see problem on st
On Sat, 2 Jan 2021 08:25:49 +0300
Rozhuk Ivan wrote:
> Hi!
>
> I am tring current and found that kernel options:
> options TERMINAL_NORM_ATTR = (FG_GREEN|BG_BLACK) # def to
> SC_NORM_ATTR / 2 | 0x00 options TERMINAL_KERN_ATTR =
> (FG_YELLOW|BG_BLACK) # def t
Hi!
I am tring current and found that kernel options:
options TERMINAL_NORM_ATTR = (FG_GREEN|BG_BLACK) # def to
SC_NORM_ATTR / 2 | 0x00
options TERMINAL_KERN_ATTR = (FG_YELLOW|BG_BLACK) # def to
SC_KERNEL_CONS_ATTR / 14 / 0x00
does not work anymore.
Fast greping source
On Sat, Jan 02, 2021 at 08:37:14AM +0800, Li-Wen Hsu wrote:
> On Sat, Jan 2, 2021 at 4:25 AM Christian Weisgerber
> wrote:
> >
> > On 2021-01-01, Shawn Webb wrote:
> >
> > > This is why I asked FreeBSD to provide anonymous read-only ssh://
> > > support for git. I'm very grateful they support it
On 01/01/2021 22:06, Herbert J. Skuhra wrote:
On Fri, 01 Jan 2021 21:29:45 +0100, Graham Perrin wrote:
On 01/01/2021 19:24, Herbert J. Skuhra wrote:
On Fri, 01 Jan 2021 20:01:16 +0100, Graham Perrin wrote:
…
I did try `mergemaster -p` and somehow (!) ended up with an empty
`/etc/group` fil
On Sat, Jan 2, 2021 at 4:25 AM Christian Weisgerber wrote:
>
> On 2021-01-01, Shawn Webb wrote:
>
> > This is why I asked FreeBSD to provide anonymous read-only ssh://
> > support for git. I'm very grateful they support it.
> >
> > One thing that I need to do with the HardenedBSD infrastructure i
It worked thank youFilippo
On Friday, January 1, 2021, 5:25:10 PM GMT+1, Milan Obuch
wrote:
On Fri, 1 Jan 2021 16:11:52 + (UTC), Filippo Moretti
wrote:
>
> I run again portmaster and I have the same error as previously
> reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GM
On 2021-01-01 11:01, Graham Perrin wrote:
At what should have been the end of my first upgrade since the transition to
git:
cd /usr/src/freebsd-current && make installworld && etcupdate
𠄴– concluded with a successful installworld, then a few lines about scanning
and
skipping certificates, th
The patches that I believe fix this are now committed to head.
Have a good 2021, rick
From: owner-freebsd-curr...@freebsd.org on
behalf of Rick Macklem
Sent: Thursday, December 31, 2020 5:56 PM
To: Konstantin Belousov
Cc: freebsd-current@freebsd.org; Al
On Fri, Jan 1, 2021, 1:40 PM Mina Galić wrote:
> On Thursday, December 31st, 2020 at 20:51, Allan Jude <
> allanj...@freebsd.org> wrote:
>
> > We've had the AESNI module for quite a few years now, and it has not
> caused any problems.
> >
> > I am wondering if there are any objections to includin
On Fri, 01 Jan 2021 21:29:45 +0100, Graham Perrin wrote:
>
> On 01/01/2021 19:24, Herbert J. Skuhra wrote:
>
> > On Fri, 01 Jan 2021 20:01:16 +0100, Graham Perrin wrote:
> >
> >> …
> >>
> >> I did try `mergemaster -p` and somehow (!) ended up with an empty
> >> `/etc/group` file. Dug myself out
On Thu, 31 Dec 2020 21:25:08 -0500
grarpamp wrote:
> > Is there any reason to think [bittorrent] insecure?
>
> Cost under $50k of compute to break sha-1,
AFAIK you cannot break SHA-1 in the sense of creating data that
matches a specific hash. What you can do is create a collision between
two
On Thursday, December 31st, 2020 at 20:51, Allan Jude
wrote:
> We've had the AESNI module for quite a few years now, and it has not caused
> any problems.
>
> I am wondering if there are any objections to including it in GENERIC, so
> that users get the benefit without having to have the "trib
On 01/01/2021 19:24, Herbert J. Skuhra wrote:
On Fri, 01 Jan 2021 20:01:16 +0100, Graham Perrin wrote:
…
I did try `mergemaster -p` and somehow (!) ended up with an empty
`/etc/group` file. Dug myself out of that hole, I'll prefer to
continue using etcupdate.
-m /path/to/sources
On 2021-01-01, Shawn Webb wrote:
> This is why I asked FreeBSD to provide anonymous read-only ssh://
> support for git. I'm very grateful they support it.
>
> One thing that I need to do with the HardenedBSD infrastructure is
> publish on our site the ssh pubkeys of the server (both RSA and
> ed2
I run again portmaster and I have the same error as previously reportedFilippo
On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo Moretti
wrote:
Ufs
It exits with a different error:
===> Installing contributed scripts
/bin/mkdir -p
/usr/ports/devel/git/work-default/stage/usr/loca
On Fri, 01 Jan 2021 20:01:16 +0100, Graham Perrin wrote:
>
> At what should have been the end of my first upgrade since the
> transition to git:
>
> cd /usr/src/freebsd-current && make installworld && etcupdate
>
> 𠄴– concluded with a successful installworld, then a few lines about
> scanning an
At what should have been the end of my first upgrade since the
transition to git:
cd /usr/src/freebsd-current && make installworld && etcupdate
𠄴– concluded with a successful installworld, then a few lines about
scanning and skipping certificates, then:
> Failed to build new tree.
I see the
On Fri, 1 Jan 2021 16:11:52 + (UTC), Filippo Moretti
wrote:
>
> I run again portmaster and I have the same error as previously
> reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo
> Moretti wrote:
> Ufs
> It exits with a different error:
> ===> Installing contributed
I could not update git from 2.29 in my system
[root@STING /usr/ports/devel/git]# uname -a
FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #14 main-c255423-gee938b20335:
Wed Dec 30 10:41:00 CET 2020
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64
This is the error which can be dup
What filesystem is this?
Does it work if you sysctl vfs.cache_fast_lookup=0 ?
On 1/1/21, Filippo Moretti wrote:
> I could not update git from 2.29 in my system
> [root@STING /usr/ports/devel/git]# uname -a
> FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #14
> main-c255423-gee938b20335: Wed Dec
On Thu, Dec 31, 2020 at 09:25:08PM -0500, grarpamp wrote:
> > There is already HTTPS to protect the "authenticity" of the magnet
> > link.
>
> No. FreeBSD fails to publish signed fingerprints of their TLS pubkeys,
> therefore users can't pin them down, therefore any MITM can bypass
> CA game and M
24 matches
Mail list logo
