Proceedings of the 17th ACM International Conference on Supporting Group Work 2012
DOI: 10.1145/2389176.2389197
|View full text |Cite
|
Sign up to set email alerts
|

Authenticating operation-based history in collaborative systems

Abstract: Within last years multi-synchronous collaborative editing systems became widely used. Multi-synchronous collaboration maintains multiple, simultaneous streams of activity which continually diverge and synchronized. These streams of activity are represented by means of logs of operations, i.e. user modifications. A malicious user might tamper his log of operations. At the moment of synchronization with other streams, the tampered log might generate wrong results. In this paper, we propose a solution relying on … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 41 publications
0
4
0
Order By: Relevance
“…A solution based on authenticators for detecting log tampering can be adopted, log tampering being detected at time of synchronization before the log is accepted by receivers [32].…”
Section: Trust Assessment In Contract-based Multi-synchronous Collabo...mentioning
confidence: 99%
“…A solution based on authenticators for detecting log tampering can be adopted, log tampering being detected at time of synchronization before the log is accepted by receivers [32].…”
Section: Trust Assessment In Contract-based Multi-synchronous Collabo...mentioning
confidence: 99%
“…Authenticated logs [19,20] make misbehaviors evident. An authenticated log contains all participants' contributions along with their dependencies.…”
Section: Vfjc Log As Threat Mitigationmentioning
confidence: 99%
“…We have proposed using authenticators for detecting log tampering. 50 Log tampering is detected at time of synchronization before the log is accepted by receivers. (3) How to use log auditing result and treat data resulted from misused actions?…”
Section: Auditing Principlesmentioning
confidence: 99%
“…Our solution about the construction and verification of authenticators to secure log are presented in our previous work. 50 Authenticators prevent re-ordering of log events and therefore causality is preserved. If log was tampered, receiving site might discard it and the trust level of the site that misbehaved would be decremented.…”
Section: Correctness Of C-ppc Modelmentioning
confidence: 99%