On Mon, Mar 5, 2012 at 7:50 PM, Leo Razoumov wrote:
> On Mon, Mar 5, 2012 at 18:49, Richard Hipp wrote:
> > On Mon, Mar 5, 2012 at 6:34 PM, Leo Razoumov
> wrote:
> >>
> >> What happens if an attacker can shun artifacts, rebuild database, edit
> >> commit messages, events, tickets, etc?
> >> Fos
On Mon, Mar 5, 2012 at 18:49, Richard Hipp wrote:
> On Mon, Mar 5, 2012 at 6:34 PM, Leo Razoumov wrote:
>>
>> What happens if an attacker can shun artifacts, rebuild database, edit
>> commit messages, events, tickets, etc?
>> Fossil sync might happily pull compromised items into a local repo.
>>
On Mon, Mar 5, 2012 at 6:34 PM, Leo Razoumov wrote:
> On Mon, Mar 5, 2012 at 18:25, Richard Hipp wrote:
> > On Mon, Mar 5, 2012 at 6:14 PM, Leo Razoumov
> wrote:
> >>
> >> In light of a recent Github compromise
> https://lwn.net/Articles/485162/
> >> I am curious of how one can detect and repai
On Mon, Mar 5, 2012 at 18:25, Richard Hipp wrote:
> On Mon, Mar 5, 2012 at 6:14 PM, Leo Razoumov wrote:
>>
>> In light of a recent Github compromise https://lwn.net/Articles/485162/
>> I am curious of how one can detect and repair a compromised fossil site??
>
> The code that is already checked
On Mon, Mar 5, 2012 at 6:14 PM, Leo Razoumov wrote:
> In light of a recent Github compromise https://lwn.net/Articles/485162/
> I am curious of how one can detect and repair a compromised fossil site??
>
The code that is already checked in is cryptographically secure. Changing
the code is as d
In light of a recent Github compromise https://lwn.net/Articles/485162/
I am curious of how one can detect and repair a compromised fossil site??
--Leo--
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cg
6 matches
Mail list logo