On Feb 7, 2011, at 18:31 , Mike Meyer wrote:
Since the worry is usually about the main repo, how about an
enhancement that disallows pushing/pulling changes that aren't signed
with an approved key?
I was also thinking about it, but there is one major problem. What with
properly signed
On Mon, Feb 7, 2011 at 11:51 AM, Richard Hipp d...@sqlite.org wrote:
Since commits (and everything else really) happens on the client, you cannot
really enforce things. The client has complete control over their copy of
the repository.
Auto-shun improperly signed commits?
But:
On Tue, Feb
Hey,
Two questions regarding signing.
1) Can you enforce the signing of commits on the server's side?
2) Can a list of accepted keys be used? I wanna make sure the developers are
using the correct key when signing.
--
Justin Mazzi
___
fossil-users
On Mon, Feb 7, 2011 at 11:45 AM, Justin Mazzi jma...@gmail.com wrote:
Hey,
Two questions regarding signing.
1) Can you enforce the signing of commits on the server's side?
2) Can a list of accepted keys be used? I wanna make sure the developers
are using the correct key when signing.
4 matches
Mail list logo
