Typo:
On Mon, Jan 4, 2021 at 5:25 PM Conrad Meyer wrote:
> SHA1 has always, by design, been vulnerable to a 2^80 resource attack :-).
2^160 for a specific hash. 2^80 if you're just trying to find any collision.
___
freebsd-current@freebsd.org mailing
On Mon, Jan 4, 2021 at 1:44 PM Ryan Stone wrote:
> FWIW, a coworker of mine had a little hobby of introducing commits
> into our internal repro that had hashes that all started with
> deadc0de. As I understand it, it was able to do this by adding an
> bogus attribute with the right value to the c
On Mon, Jan 4, 2021 at 3:44 PM Poul-Henning Kamp wrote:
> Shattered is less impressive when you take into account that you
> can stuff as much much garbage into a PDF file as you need, without
> affecting the files normal function.
>
> Compact data formats, formats which leave no wiggle-room and d
John-Mark Gurney writes:
> SHAttered[1] (2017) created two valid PDF documents which had the same
> SHA-1 hash. The issue was that they were able to choose the entire
> document.
Shattered is less impressive when you take into account that you
can stuff as much much garbage into a PDF f
RW wrote this message on Fri, Jan 01, 2021 at 16:56 +:
> 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
>> Though it can help attribute that to a source,
Meaning to source 'account', vs say weak old CVSROOT
that any could text edit on 200 account box, claim bitrot, etc.
Whether inspiration came from the pet dog's bug report
is moot, more secure systems narrow into accounts that
would then be examine
grarpamp writes:
> > No amount of cryptography can or will protect against that.
>
> Though it can help attribute that to a source,
No.
You would end up with the committer saying "it came in as a bug-report,
I looked at it, and it looked sensible so I committed it."
Unless you are goin
Folks, please change the Subject: line here. This has now become a
thread of only tangiental interest to a typical FreeBSD developer
(in this case, typified by me :-) )
mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/l
> No amount of cryptography can or will protect against that.
Though it can help attribute that to a source,
else ignore rainbow books and go back to telnet,
root password 'root', CVS, no backups, logs, etc.
> As interesting as this thread has been (not!)
Contrare.
Equally as interesting as thre
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, 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 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
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 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
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
> 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 MITM attack users at will, feed them bogus infohash,
isos, git repo tof
On Thu, 31 Dec 2020 11:39:08 -0800
John-Mark Gurney wrote:
> grarpamp wrote this message on Wed, Dec 30, 2020 at 00:55 -0500:
> > > signatures of the magnet links
> >
> > Signing torrent.asc, with stronger or even same hash as BT
> > protocol, still serve purpose of authenticate torrent file ba
grarpamp wrote this message on Wed, Dec 30, 2020 at 00:55 -0500:
> > signatures of the magnet links
>
> Signing torrent.asc, with stronger or even same hash as BT
> protocol, still serve purpose of authenticate torrent file back
> to a signer to the degree therein, caveat their platform security,
>> SHA-256 arrives, if you look at the git history.
> git's SHA-256 [...] requiring a super new git version to even test it out.
It's "in" current release 2.30.0 and before, duly caveated as experimental
and not fully featured yet...
git-init(1)
--object-format=
Specify the giv
On 2020-12-29 20:59, Chris wrote:
On 2020-12-29 16:46, John-Mark Gurney wrote:
Steffen Nurpmeso wrote this message on Tue, Dec 29, 2020 at 22:04 +0100:
|SolarWinds supply chain attack, being able to smuggle a modified file
|into a git repo, say an OS's build server, such that the tools don't
On 2020-12-29 16:46, John-Mark Gurney wrote:
Steffen Nurpmeso wrote this message on Tue, Dec 29, 2020 at 22:04 +0100:
|SolarWinds supply chain attack, being able to smuggle a modified file
|into a git repo, say an OS's build server, such that the tools don't
|know the tree is modified is a re
Steffen Nurpmeso wrote this message on Tue, Dec 29, 2020 at 22:04 +0100:
> |SolarWinds supply chain attack, being able to smuggle a modified file
> |into a git repo, say an OS's build server, such that the tools don't
> |know the tree is modified is a real problem...
>
> SHA-256 arrives, if you
John-Mark Gurney wrote in
<20201229011939.gu31...@funkthat.com>:
|Steffen Nurpmeso wrote this message on Wed, Dec 23, 2020 at 17:24 +0100:
|>|Then there's also the point that the repo is (looks like it) using
|>|SHA-1 hashes, which are effectively broken, so depending upon them
|>|to validate
On Mon, Dec 28, 2020, 6:19 PM John-Mark Gurney wrote:
> Steffen Nurpmeso wrote this message on Wed, Dec 23, 2020 at 17:24 +0100:
> > |Then there's also the point that the repo is (looks like it) using
> > |SHA-1 hashes, which are effectively broken, so depending upon them
> > |to validate the
Steffen Nurpmeso wrote this message on Wed, Dec 23, 2020 at 17:24 +0100:
> |Then there's also the point that the repo is (looks like it) using
> |SHA-1 hashes, which are effectively broken, so depending upon them
> |to validate the tree is questionable anyways.
>
> git uses the hardened SHA-1 f
Kurt Jaeger wrote this message on Wed, Dec 23, 2020 at 13:15 +0100:
> Hi!
>
> > It's also hard to collect ALL the keys of the devs at any point in
> > time to decide if that key is authorized to sign a commit in the
> > repo...
>
> We do have most of the keys in docs/share/pgpkeys/ plus history.
> We do have most of the keys in docs/share/pgpkeys/ plus history.
https://git.kernel.org/pub/scm/docs/kernel/ksmap
https://git.kernel.org/pub/scm/docs/kernel/pgpkeys
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
Am 23.12.20 um 21:55 schrieb Ulrich Spörlein:
> On Wed, 2020-12-23 at 12:19:47 -0800, John Kennedy wrote:
>> On Mon, Dec 21, 2020 at 12:47:38PM -0800, John Kennedy wrote:
>>> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>>> > The FreeBSD project will be moving it's source repo from
On Wed, 2020-12-23 at 12:19:47 -0800, John Kennedy wrote:
On Mon, Dec 21, 2020 at 12:47:38PM -0800, John Kennedy wrote:
On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> The FreeBSD project will be moving it's source repo from subversion to git
> starting this this weekend. The docs
On Mon, Dec 21, 2020 at 12:47:38PM -0800, John Kennedy wrote:
> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> > The FreeBSD project will be moving it's source repo from subversion to git
> > starting this this weekend. The docs repo was moved 2 weeks ago. The ports
> > repo will mo
On 23/12/20 15:20, Michael Grimm wrote:
Renato Botelho wrote:
If you want to switch to a different already existing branch, as svn switch
does, you should look at git-checkout.
It can be a bit expensive due to the size of src repository so if you do work
on multiple branches too often you c
Renato Botelho wrote:
> If you want to switch to a different already existing branch, as svn switch
> does, you should look at git-checkout.
>
> It can be a bit expensive due to the size of src repository so if you do work
> on multiple branches too often you can improve it using git-worktree.
Warner Losh wrote:
> On Wed, Dec 23, 2020 at 7:32 AM Michael Grimm wrote:
>> With svn I used:
>>svn switch svn://svn.freebsd.org/base/stable/NEW /usr/src
>>
>> For git I found:
>>git branch -m stable/OLD stable/NEW
>>or
>>git branch -M stable/OLD stable/NEW
>
>
On Wed, Dec 23, 2020 at 7:32 AM Michael Grimm wrote:
> Hi,
>
> Warner Losh wrote:
>
> > The FreeBSD project will be moving it's source repo from subversion to
> git
> > starting this this weekend.
>
> First of all I'd like to thank all those involved in this for their
> efforts.
>
> Following
>
On Tue, Dec 22, 2020 at 06:32:43PM -0800, John-Mark Gurney wrote:
> Steffen Nurpmeso wrote this message on Fri, Dec 18, 2020 at 19:28 +0100:
> > Brooks Davis wrote in
> > <20201218175241.ga72...@spindle.one-eyed-alien.net>:
> > |On Thu, Dec 17, 2020 at 05:53:20PM -0800, Thomas Mueller wrote:
> >
On Wed, Dec 23, 2020 at 3:35 AM Marek Zarychta <
zarych...@plan-b.pwste.edu.pl> wrote:
> W dniu 17.12.2020 o 01:46, Warner Losh pisze:
> > Greetings,
> >
> > The FreeBSD project will be moving it's source repo from subversion to
> git
> > starting this this weekend. The docs repo was moved 2 weeks
John-Mark Gurney wrote in
<20201223023242.gg31...@funkthat.com>:
|Steffen Nurpmeso wrote this message on Fri, Dec 18, 2020 at 19:28 +0100:
|> Brooks Davis wrote in
|> <20201218175241.ga72...@spindle.one-eyed-alien.net>:
|>|On Thu, Dec 17, 2020 at 05:53:20PM -0800, Thomas Mueller wrote:
...
On 23.12.2020 18:04, Lev Serebryakov wrote:
On 23.12.2020 17:32, Michael Grimm wrote:
git-branch(1):
With a -m or -M option, will be renamed to .
If
==
had a corresponding reflog, it is renamed to match
On 23.12.2020 17:32, Michael Grimm wrote:
git-branch(1):
With a -m or -M option, will be renamed to . If
==
had a corresponding reflog, it is renamed to match
, and a reflog entry is created to remembe
On 23/12/20 11:32, Michael Grimm wrote:
Hi,
Warner Losh wrote:
The FreeBSD project will be moving it's source repo from subversion to git
starting this this weekend.
First of all I'd like to thank all those involved in this for their efforts.
Following https://github.com/bsdimp/freebsd-git
Hi,
Warner Losh wrote:
> The FreeBSD project will be moving it's source repo from subversion to git
> starting this this weekend.
First of all I'd like to thank all those involved in this for their efforts.
Following https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md
form yo
Hi!
> It's also hard to collect ALL the keys of the devs at any point in
> time to decide if that key is authorized to sign a commit in the
> repo...
We do have most of the keys in docs/share/pgpkeys/ plus history.
> Like if a dev starts in 2021, any commits made by that
> dev prior to 2021 shou
W dniu 17.12.2020 o 01:46, Warner Losh pisze:
> Greetings,
>
> The FreeBSD project will be moving it's source repo from subversion to git
> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
> repo will move at the end of March, 2021 due to timing issues.
>
> The short ver
Steffen Nurpmeso wrote this message on Fri, Dec 18, 2020 at 19:28 +0100:
> Brooks Davis wrote in
> <20201218175241.ga72...@spindle.one-eyed-alien.net>:
> |On Thu, Dec 17, 2020 at 05:53:20PM -0800, Thomas Mueller wrote:
> |>>> I hope we don't have to start signing all commits. saltstack/salt has
On 2020-Dec-22, at 13:31, Mark Millard wrote:
> On 2020-Dec-22, at 13:06, bob prohaska wrote:
>
>> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>>
>>> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
>>> Prevents about 1000 dependencies.
>>>
>>
On 2020-Dec-22, at 13:06, bob prohaska wrote:
> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>
>> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
>> Prevents about 1000 dependencies.
>>
>
> That seems to have worked. It reported something about pac
On 2020-Dec-22, at 10:39, bob prohaska wrote:
> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>>
>> The FreeBSD project will be moving it's source repo from subversion to git
>> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
>> repo will move at the
On Dec 22, 2020, at 1:39 PM, bob prohaska wrote:
> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>>
>> The FreeBSD project will be moving it's source repo from subversion to git
>> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
>> repo will move at the
Attributions are really confusing at this point...
On 2020-Dec-22, at 13:06, bob prohaska wrote:
> bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src
On 2020-Dec-22, at 13:31, Mark Millard wrote:
> I cloned FreeBSD's src.git via:
> git clone -o freebsd --config
> remote.freebsd
On 22 Dec 2020, at 22:50, Mark Millard wrote:
On 2020-Dec-22, at 13:31, Mark Millard wrote:
Clone
https://git.FreeBSD.org/src.git
anon...@git.freebsd.org:src.git
g...@gitrepo.freebsd.org:src.git
Hmm. It turns out that the last 2 are links on that page and the
links expand out to:
https://cg
On Tue, Dec 22, 2020 at 12:19:03PM -0800, Mark Millard wrote:
>
> git in base would have licensing issues.
>
I gather you're referring to GPLv2. A sticky wicket.
The trouble with ports is the tree is getting awfully big.
The host in question has a 32 GB disk and is over half full
with just a bas
On 22 Dec 2020, at 22:06, bob prohaska wrote:
> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>
>> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
>> Prevents about 1000 dependencies.
>>
>
> That seems to have worked. It reported something about package man
On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>
> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
> Prevents about 1000 dependencies.
>
That seems to have worked. It reported something about package management
not being installed, but after a prompt insta
Van: bob prohaska
Datum: 22 december 2020 19:38
Aan: freebsd-...@freebsd.org
CC: FreeBSD Current
Onderwerp: Re: HEADS UP: FreeBSD src repo transitioning to git this weekend
On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>
> The FreeBSD project will be moving it's
On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>
> The FreeBSD project will be moving it's source repo from subversion to git
> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
> repo will move at the end of March, 2021 due to timing issues.
>
Is there som
On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> The FreeBSD project will be moving it's source repo from subversion to git
> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
> repo will move at the end of March, 2021 due to timing issues. ...
I filed Bug
Brooks Davis wrote in
<20201218175241.ga72...@spindle.one-eyed-alien.net>:
|On Thu, Dec 17, 2020 at 05:53:20PM -0800, Thomas Mueller wrote:
|>>> I hope we don't have to start signing all commits. saltstack/salt has
|>>> that policy, and it's extremely annoying.
|>
|>> Have to? Not currently
On Thu, Dec 17, 2020 at 05:53:20PM -0800, Thomas Mueller wrote:
> > > I hope we don't have to start signing all commits. saltstack/salt has
> > > that policy, and it's extremely annoying.
>
> > Have to? Not currently. As with all process changes, there will be
> > community discussion around the
On 2020-12-17 21:53, Thomas Mueller wrote:
> I hope we don't have to start signing all commits. saltstack/salt has
> that policy, and it's extremely annoying.
Have to? Not currently. As with all process changes, there will be
community discussion around the different points.
Warner
I hop
> > I hope we don't have to start signing all commits. saltstack/salt has
> > that policy, and it's extremely annoying.
> Have to? Not currently. As with all process changes, there will be
> community discussion around the different points.
> Warner
I hope not!
Signatures, at least in email me
I tried cloning with the following result:
[root@STING /home/filippo]# git clone -o freebsd -b main
https://git.freebsd.org/src.git /usr/src
Cloning into '/usr/src'...
fatal: repository 'https://git.freebsd.org/src.git/' not found
Should I wait past the weekend to clone?Filippo
On Thursday,
On Thu, 2020-12-17 at 13:39:09 -0700, Warner Losh wrote:
On Thu, Dec 17, 2020 at 12:53 PM Alan Somers wrote:
On Thu, Dec 17, 2020 at 12:06 PM Warner Losh wrote:
On Thu, Dec 17, 2020 at 12:01 PM Nathan Whitehorn One question I didn't see in the (excellent!) docs is whether we should
> be PGP-
On Thu, Dec 17, 2020 at 12:53 PM Alan Somers wrote:
> On Thu, Dec 17, 2020 at 12:06 PM Warner Losh wrote:
>
>> On Thu, Dec 17, 2020 at 12:01 PM Nathan Whitehorn > >
>> wrote:
>>
>> >
>> >
>> > On 12/16/20 7:46 PM, Warner Losh wrote:
>> > > Greetings,
>> > >
>> > > The FreeBSD project will be mov
On Thu, Dec 17, 2020 at 12:06 PM Warner Losh wrote:
> On Thu, Dec 17, 2020 at 12:01 PM Nathan Whitehorn
> wrote:
>
> >
> >
> > On 12/16/20 7:46 PM, Warner Losh wrote:
> > > Greetings,
> > >
> > > The FreeBSD project will be moving it's source repo from subversion to
> > git
> > > starting this t
On Thu, Dec 17, 2020 at 12:01 PM Nathan Whitehorn
wrote:
>
>
> On 12/16/20 7:46 PM, Warner Losh wrote:
> > Greetings,
> >
> > The FreeBSD project will be moving it's source repo from subversion to
> git
> > starting this this weekend. The docs repo was moved 2 weeks ago. The
> ports
> > repo will
On 12/16/20 7:46 PM, Warner Losh wrote:
Greetings,
The FreeBSD project will be moving it's source repo from subversion to git
starting this this weekend. The docs repo was moved 2 weeks ago. The ports
repo will move at the end of March, 2021 due to timing issues.
The short version is that we
On Thu, Dec 17, 2020 at 11:33 AM Andreas Ott wrote:
> Hi,
>
> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> > This switch will preserve much of the current FreeBSD development
> workflow.
> > After the switch, the subversion repo will become almost read-only.
>
> Will there be an
Hi,
On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> This switch will preserve much of the current FreeBSD development workflow.
> After the switch, the subversion repo will become almost read-only.
Will there be an update to the build from source instructions in
https://www.freebsd
Greetings,
The FreeBSD project will be moving it's source repo from subversion to git
starting this this weekend. The docs repo was moved 2 weeks ago. The ports
repo will move at the end of March, 2021 due to timing issues.
The short version is that we're switching the version control we're using
69 matches
Mail list logo
