# US 2019/0377889 A1 · Verifiable version control on authenticated and/or encrypted electronic documents

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0377889 A1
- Document ID: US20190377889A1
- Status: Published application
- Kind: A1
- Application number: 16/484,876
- Filed: 2018-02-01
- Published: 2019-12-12
- Earliest claimed: 2017-02-10
- Inventors: Michael Mertens; Michael Raumann
- Web page: https://patentgrep.com/patent/US20190377889A1

## CPC

- G06F 21/60: Protecting data
- G06F 21/6209: {to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself}
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/085: {Secret sharing or secret splitting, e.g. threshold schemes}
- H04L 63/123: {received data contents, e.g. message integrity}
- G06F 2221/2107: File encryption
- H04L 63/045: {wherein the sending and receiving network entities apply hybrid encryption, i.e. combination of symmetric and asymmetric encryption (cryptographic mechanisms or cryptographic arrangements using a plurality of keys or algorithms H04L9/14)}
- H04L 63/104: {Grouping of entities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present invention concerns a method for encrypting files performed by a client computer, the method comprising encrypting at least a part of the content of a file into a change-set data structure using a secret key shared among a plurality of users, and signing the change-set data structure using a private signing key of a user of the client computer. The invention also concerns a method for decrypting files performed by a client computer, the method comprising receiving a change-set data structure, verifying a digital signature of the change-set data structure using a public verification key of a user who created the change-set, and decrypting an encrypted data portion of the change-set data structure to obtain the file using a secret key shared among a plurality of users.

## Claims

### Claim 1

A method for encrypting files performed by a client computer, the method comprising:
encrypting at least a part of content of a file into a change-set data structure using a secret key shared among a plurality of users; and
signing the change-set data structure using a private signing key of a user of the client computer;
wherein the change-set data structure comprises a hash taken over a signature digest of a last significant change, wherein a significant change comprises: a change-set that adds a new file, a change-set that removes a file, a group change that adds a new member, and/or a group change that removes a member.

### Claim 2

A method for decrypting files performed by a client computer, the method comprising:
receiving a change-set data structure;
verifying a digital signature of the change-set data structure using a public verification key of a user who created the change-set;
wherein the change-set data structure comprises a hash taken over a signature digest of a last significant change, wherein a significant change comprises: a change-set that adds a new file, a change-set that removes a file, a group change that adds a new member, and/or a group change that removes a member; and wherein the method further comprises:
verifying whether a hash taken over a signature digest of a previous significant change matches said hash in the change-set data structure; and
decrypting an encrypted data portion of the change-set data structure to obtain the file using a secret key shared among a plurality of users.

### Claim 3 (depends on 2)

The method of claim 2, wherein the change-set data structure further comprises one or more of:
a document identifier;
an initialization vector usable for encrypting and decrypting the file;
message authentication data;
a hash of the encrypted at least the part of the content of the file and/or a hash over a previous version of the file;
an encrypted name of the file; and/or
a sequence number.

### Claim 4 (depends on 1)

The method of claim 1, further comprising the step of providing a key structure comprising a first key-pair and a second key-pair,
the first key-pair comprising a private signing key and a public verification key,
the second key-pair comprising a public encryption key and a private decryption key,
wherein the first and second key-pairs comprise asymmetric key-pairs.

### Claim 5 (depends on 4)

The method of claim 4, wherein the key structure is usable for encrypting the shared secret key, wherein the shared secret key comprises a symmetric key.

### Claim 6 (depends on 4)

The method of claim 4, wherein the public verification key of the first key-pair digitally signs the second key-pair, wherein the first key-pair uniquely identifies a user.

### Claim 7 (depends on 2)

The method of claim 2, wherein the encrypted data portion of the change-set data structure represents only a part of the content of the file which has been changed as compared to a previous version of the file.

### Claim 8 (depends on 4)

The method of claim 4, further comprising the step of providing a group change data structure comprising one or more of:
a group identifier;
one or more references to a public key of a user to be added to and/or removed from a group corresponding to the group change data structure;
a key fingerprint for each reference;
a digital signature;
a sequence number;
one or more secret keys usable for encrypting and decrypting files, wherein the one or more secret keys are encrypted by the encryption key of the second key-pair; and/or
one or more access permissions for users.

### Claim 9 (depends on 1)

The method of claim 1, further comprising the step of providing a history data structure, wherein the history data structure comprises a sequence of history segments, each history segment comprising a sequence of group change data structures and/or change-set data structures;
wherein the group change data structure reflects a change of a user group, and the change-set data structure reflects a change of a file.

### Claim 10 (depends on 9)

The method of claim 9, wherein each history segment further comprises a history audit data structure, the history audit data structure comprising a last structure in the sequence, the history audit data structure comprising:
a first hash identifying a previous history segment;
a second hash over all the structures in the history segment; and/or
a digital signature over the first and second hash.

### Claim 11 (depends on 10)

The method of claim 10, wherein the second hash is ordered:
firstly, by key hashes of the structures;
secondly, by a type of the structures, wherein group change data structures have a highest priority, change-set data structures that add or remove a file have a second highest priority, and change-set data structures that modify a file have a third highest priority; and/or
thirdly, by a hash taken over a signature digest of the structure.

### Claim 12 (depends on 9)

The method of claim 9, comprising the step of starting a new history segment after a predefined time span.

### Claim 13

A computer program comprising instructions for implementing a method comprising:
encrypting at least a part of content of a file into a change-set data structure using a secret key shared among a plurality of users; and
signing the change-set data structure using a private signing key of a user of a client computer;
wherein the change-set data structure comprises a hash taken over a signature digest of a last significant change, wherein a significant change comprises: a change-set that adds a new file, a change-set that removes a file, a group change that adds a new member, and/or a group change that removes a member.

### Claim 14 (depends on 1)

A client computer configured for performing a method as defined in claim 1.

### Claim 15 (depends on 14)

A system comprising a plurality of client computers according to claim 14.

### Claim 16 (depends on 1)

The method of claim 1, wherein a blockchain is used to store the change-set data structure.

### Claim 17 (depends on 1)

The method of claim 1, wherein the change-set data structure further comprises one or more of:
a document identifier;
an initialization vector usable for encrypting and decrypting the file;
message authentication data;
a hash of the encrypted at least the part of the content of the file and/or a hash over a previous version of the file;
an encrypted name of the file; and/or
a sequence number.

### Claim 18 (depends on 2)

The method of claim 2, further comprising the step of receiving a history data structure, wherein the history data structure comprises a sequence of history segments, each history segment comprising a sequence of group change data structures and/or change-set data structures;
wherein the group change data structure reflects a change of a user group, and the change-set data structure reflects a change of a file.

### Claim 19 (depends on 2)

The method of claim 2, further comprising the step of receiving a key structure comprising a first key-pair and a second key-pair,
the first key-pair comprising a private signing key and a public verification key,
the second key-pair comprising a public encryption key and a private decryption key,
wherein the first and second key-pairs comprise asymmetric key-pairs.

### Claim 20 (depends on 2)

The method of claim 2, wherein a blockchain is used to store the change-set data structure.
