[libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing

[libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing

[bugzilla-daemon]

https://bugs.libre-soc.org/show_bug.cgi?id=266

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Allow read-only git clone   |deploy git commit-signing
                   |over https                  |and tag-signing

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
changing the topic of this bugreport.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing

[Jacob Lifshay]

On Mon, May 18, 2020, 13:43 <bugzilla-daemon@libre-soc.org> wrote:

> https://bugs.libre-soc.org/show_bug.cgi?id=266
>
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Summary|Allow read-only git clone   |deploy git commit-signing
>                    |over https                  |and tag-signing
>
> --- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> changing the topic of this bugreport.


We really shouldn't just repurpose bug reports when the goal of the
original bug report is accomplished, since it makes it quite confusing to
people who weren't paying attention the whole time or are looking through
past bug reports. Additionally, nearly all the comments are on a totally
different topic than what the title was changed to.

Luke, please change the title back, close this bug, and create a new one.

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] [Bug 266] deploy git commit-signing and tag-signing

[Luke Kenneth Casson Leighton]

On Monday, May 18, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Mon, May 18, 2020, 13:43 <bugzilla-daemon@libre-soc.org> wrote:
>
> > https://bugs.libre-soc.org/show_bug.cgi?id=266
> >
> > Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
> >
> >            What    |Removed                     |Added
> >
> > ------------------------------------------------------------
> ----------------
> >             Summary|Allow read-only git clone   |deploy git
> commit-signing
> >                    |over https                  |and tag-signing
> >
> > --- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> > changing the topic of this bugreport.
>
>
> We really shouldn't just repurpose bug reports when the goal of the
> original bug report is accomplished, since it makes it quite confusing to
> people who weren't paying attention the whole time or are looking through
> past bug reports. Additionally, nearly all the comments are on a totally
> different topic than what the title was changed to.
>
> Luke, please change the title back, close this bug, and create a new one.


awww okaaay :)  can't i be totally lazy just once?

(thx for calling this one jacob)



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

[libre-riscv-dev] [Bug 266] Allow read-only git clone over https

[bugzilla-daemon]

https://bugs.libre-soc.org/show_bug.cgi?id=266

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|deploy git commit-signing   |Allow read-only git clone
                   |and tag-signing             |over https
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

[libre-riscv-dev] [Bug 266] Allow read-only git clone over https

[bugzilla-daemon]

https://bugs.libre-soc.org/show_bug.cgi?id=266

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=322

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

[libre-riscv-dev] [Bug 266] Allow read-only git clone over https

[bugzilla-daemon]

https://bugs.libre-soc.org/show_bug.cgi?id=266

--- Comment #5 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> changing the topic of this bugreport.

Luke changed back to avoid confusion. Sincere thanks for taking the extra time!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

[libre-riscv-dev] [Bug 266] Allow read-only git clone over https

[bugzilla-daemon]

http://bugs.libre-riscv.org/show_bug.cgi?id=266

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hmm really we should be doing git tag signing and/or git commit sign-off,
with gpg keys.  relying on HTTPS in particular for security just paints
a bullseye on the server.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

[libre-riscv-dev] [Bug 266] Allow read-only git clone over https

[bugzilla-daemon]

http://bugs.libre-riscv.org/show_bug.cgi?id=266

vklr@vkten.in <vklr@vkten.in> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vklr@vkten.in

--- Comment #2 from vklr@vkten.in <vklr@vkten.in> ---
Yes. git protocol is insecure over untrusted network as documented in official
git-scm.org site itself.

Please use new protocol for http/https protocol and not the old dumb protocol.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

[libre-riscv-dev] [Bug 266] Allow read-only git clone over https

[bugzilla-daemon]

http://bugs.libre-riscv.org/show_bug.cgi?id=266

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
A potentially useful reference (not known to be correct):
http://swarm.cs.pub.ro/~razvan/blog/http-repository-sharing-asides-gitweb/

Showing the URL required for cloning is a good accessibility improvement.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev