Method and device for transmitting an electronic message

• US 20040236953A1
• Filed: 06/24/2004
• Published: 11/25/2004
• Est. Priority Date: 05/15/2001
• Status: Abandoned Application

• Current Assignee: Veridis
• Original Assignee: Veridis
• Inventors: Merenne, Olivier, Lemmens, Sebastien
• Application Number:
  US10/477,991
• Publication Number:
  US 20040236953A1
• Time in Patent Office: Days
• US Class Current: 713/182
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32

Abstract

A method for transmitting an electronic message from a sender node to at least one receiver node,—forming an electronic message at said sender node;—adding an attribute to said electronic message;—sending said electronic message from said sender node to a first server;—processing said electronic message in order to form a processed electronic message;—transmitting said processed electronic message to said receiver node(s);—said processing comprises a processing by said first server which has a master-slave configuration and comprises a set of slave servers, each slave server being provided for processing a predetermined attribute to said electronic message, and wherein adding said attribute comprises a selection of at least one attribute identifier among series of attribute identifiers, each attribute identifier of said series being associated with one of said slave servers, and wherein said processing comprises: (i) an identifying step comprising; identifying among said set of slave servers, by said master server and based on said attribute identifier, this or those slave server(s) to which said electronic message will be sent in order to be processed; and (ii) a handling step comprising: (ii-1) transmitting said electronic message from said master server to said identified slave server(s); (ii-2) processing said electronic message by each of said identified slave servers in order to incorporate said attribute into said electronic message; (ii-3) transmitting said processed electronic message from the slave server to the master server.

Claims

1. A method for transmitting an electronic message from a sender node to at least one receiver node, said method comprising:

forming an electronic message at said sender node;

adding an attribute to said electronic message;

sending said electronic message from said sender node to a first server;

processing said electronic message in order to form a processed electronic message;

transmitting said processed electronic message to said receiver node (s);

characterized in that said processing comprises a processing by said first server which has a master-slave configuration and comprises a set of slave servers, each slave server being provided for processing a predetermined attribute to said electronic message, and wherein adding said attribute comprises a selection of at least one attribute identifier among a series of attribute identifiers, each attribute identifier of said series being associated with one of said slave servers, and wherein said processing comprises;

(i) an identifying step comprising;

identifying among said set of slave servers, by said master server and based on said attribute identifier, this or those slave server (s) to which said electronic message will be sent in order to be processed; and

(ii) a handling step comprising;

(ii-1) transmitting said electronic message from said master server to said identified slave server (s);

(ii-2) processing said electronic message by each of said identified slave servers in order to incorporate said attribute into said electronic message;

(ii-3) transmitting said processed electronic message from the slave server to the master server.

2. A method as claimed in claim 1 characterized in that said sender and receiver node are operating within a network comprising at least one further node to which a further server, having a master-slave configuration, is connected, and wherein said identifying step comprises:

verifying for each selected attribute identifier, by said first master server whether there is among the slave server (s) associated with the first server, a slave server able to incorporate said added attribute into said electronic message,

if said first server establishes that it lacks an associated slave server able to incorporate said added attribute into said electronic message, searching among said further server (s), if one of them has at least one slave server (s) able to incorporate said added attribute into said electronic message; and

upon finding among said further server (s), a dedicated further server able to incorporate said added attribute into said electronic message;

transmitting, by said first server to said dedicated further server;

processing said electronic message by a slave server of said further server in order to incorporate said attribute into said electronic message; and

if upon said searching, said first server doesn'"'"'t find among said further server (s), any further server able to incorporate said attribute into said electronic message, generating a first error message, by said first server.

3. A method as claimed in claim 1, characterized in that after transmitting said electronic message to said receiver node, said electronic message is received and handled further by said receiver node having a receiver server with a master-slave configuration.

4. A method as claimed in claim 1, characterized in that said method further comprises, upon receipt of said electronic message by said first server:

forming, by said first master server, a label having a data structure comprising a set of fields, each field having each time a predetermined length, said set of fields comprising an identifier field;

selecting said identifier field within said label

integrating, by said first master server, said selected attribute identifier within said identifier field;

linking said label to said electronic message.

5. A method as claimed in claim 4, characterized in that said method further comprises the generation of a first digital signature on the basis of a content of said identifier field and the integration of said first digital signature into said identifier field.

6. A method as claimed in claim 4, characterized in that said set of fields also comprises a hash field and wherein said method further comprises:

forming, before transmitting said electronic message to said identified slave server, a first hash computed on the basis of said electronic message

selecting said hash field within said label and integrating said first hash in said selected hash field; and

before said handling step;

generating a second hash based on said electronic message received by said identified slave server and comparing said first and second hash;

matching said first and second hash by said master server,

generating a second error message by said master server if said comparison results is a non-matching of said first and second hash.

7. A method as claimed in claim 4, characterized in that said set of fields also comprises a log field and wherein said method further comprises, before transmitting said processed electronic message from said first master server to said identified slave server:

selecting, by said master server, said log field within said label;

generating a report comprising an identification information indicating said identified slave server which produced said report;

generating a second digital signature based a private key of said identified slave server;

integrating in said log field, said report and said second digital signature by said identified slave server.

8. A method as claimed in claim 7, characterized in that said set of fields further comprises a key keyring field provided for storing a set of public keys in such a manner that each server is able to verify said second digital signature generated on the basis of said private key of said identified slave server (s), and wherein said method further comprises, before said handling:

selecting said key keyring field within said label;

integrating a public key of said identified slave server (s), in said key keyring field;

verifying, by a least one slave server, said second digital signature which is previously generated by slave server, and generating a third error message if said at least one of slave server is not able to verify said second digital signature.

9. A method as claimed in claim 7, characterized in that said set of field also comprises a third signature field and wherein said method further comprises:

generating, by each server which modifies said electronic message, a third digital signature, based on the content of the third signature field.

10. A method as claimed in claim 4, characterized in that said set of fields also comprises a serial number field and wherein said method further comprises, before forming said label by said first server:

forming, by said first server, an envelop having a serial number;

introducing said electronic message into said envelop;

linking said label to said envelop;

integrating, by said first server and in said serial number field of said label, a copy of said serial number;

extracting, by said identified slave server and before incorporating said attribute, said electronic message from said envelop;

introducing by said identified slave server said electronic message into said envelop, after said identified slave server has incorporated said attribute.

11. A method as claimed in claim 1, characterized in that said sender and receiver node belong to a network comprising a network address generator, said method further comprises:

generating a network address by said network address generator;

assigning said electronic message to said network address;

sending by said network address generator, said network address to said receiver node; and

pointing by said receiver node said network address so that said receiver node has access to said electronic message.

12. A method as claimed in claim 11, characterized in that said assigned network address comprises a data block verified by said first server in order to access to said electronic message.

13. A method as claimed in claim 12, characterized in that said data block is encrypted and/or signed by a authenticated server.

14. A method as claimed in claim 4, characterized in that said set of fields also comprises a session key field, and wherein a predetermined server, belonging to a network, is an access control slave server having a public-private key pair, and wherein said method further comprises:

before transmitting said processed electronic message to said receiver node(s);

selecting by said access control slave server a public key of said first user having a first private-public key;

generating by said access control slave server a session key and encrypting said electronic message with said session key;

encrypting said session key with said first public key of said first user;

encrypting said encrypted session key with said access control slave server'"'"'s public key in order to obtain a twice-encrypted session key;

placing said twice-encrypted session key in a session field of said label

sending said electronic message to said first user node;

sending, by said first user node, to said access control slave server said twice-encrypted session key;

decrypting by said access control slave server said twice-encrypted session key with said access control slave server'"'"'s private key;

sending, by said access control slave server, to said first user said encrypted session key;

decrypting by said first user with said first user'"'"'s private key said encrypted session key;

decrypting said electronic message with said decrypted session key.

15. A method as claimed in claim 14, characterized in that said method further comprises,

generating by a second user a second private-public key pair comprising a second public and second private key as well as a second reference corresponding to said second public and second private key

sending, by said second user to a certifying server, a first message comprising said second public key with said second reference and a reference to a predetermined contact point;

receiving by said certifying server said first message;

generating by said certifying server on basis of said second public key a certified second public key comprising a digital signature of said certifying server and a secret code;

assigning said second reference to said certified second public key;

encrypting by said certifying server, based on said second public key or said certified second public key said secret code and said second certified public key;

sending to said contact point a second message comprising said encrypted secret code and said encrypted certified second public key;

accessing said contact point by said second user and decrypting with his second private key said encrypted secret code and said encrypted certified second public key;

sending by said second user to said certifying server said secret code signed with said second private key and said second reference;

decrypting said secret code by said certifying server with said certified second public key;

comparing said decrypted secret code and said generated secret code and if both matches associating by said certifying server said certifying public key to said contact point

sending by said server to said second user a fourth error message in case of non-matching.

16. A method as claimed in claim 15, characterized in that said method further comprises:

before receiving said message by said certifying server

supplying a certified digital data block furnished by a predetermined party identified by said first server and adding said certified digital data block to said message;

after said message has been received by said certifying server

authenticating by said certifying server said certified digital datablock;

comparing by said certifying server said decrypted secret code and said generated secret code, and

assigning by said certifying server said certifying public key and said contact point to said certified digital identity if both are matching and upon non-matching, sending a fifth error message to said third user.

17. A method as claimed in claim 15, characterized in that said method further comprises,

generating by a third user a third public-private key pair comprising a third public and third private key as well as a third reference corresponding to said third public and private key pair;

sending by said third user to a certifying server a first message comprising said third public key with his third reference and a third reference to a predetermined contact point;

receiving by said certifying server said message;

generating on basis of said third public key a certified third public key comprising a digital signature of said certifying server and a network address

linking said third reference with said certified third public key;

encrypting by a slave server based on said third public key or said certified third public key said network address and said certifying third public key;

sending to said contact point a second message comprising said encrypted network address and said encrypted certified third public key;

accessing by said third user with his third private key said contact point and decrypting said encrypted network address and said encrypted certified third public key;

pointing by said third user said network address in order to request to certifying server to assign said certified third public key to said contact point, if said network address is not pointed by said third user after a period of time, a slave server sends to said third user a first fourth message.

18. A method as claimed in claim 17, characterized in that said method further comprises:

sending by a user who wishes to revoke his public key a revocation message to said certifying server;

receiving by said certifying server, said revocation message;

generating by said certifying server a revocation network address comprising data requesting said certifying server to revoke said public key;

sending by said certifying server to said contact point said revocation network address;

requesting by said user said network address so as to order said certifying server to revoke said public key;

revoking by said certifying server said public key.

19. A method as claimed in claim 18, characterized in that said method further comprises,

upon revoking by said certifying server said public key:

sending said revoked public key to said user;

if said user returns to certifying server said revoked public key then said certifying server publishes said revoked public key.

20. A method as claimed in claim 18, characterized in that said method further comprises, during said generation of a revocation network address by said certifying server, an addition by said certifying server into said network address of data indicating that said public key has been revoked.

21. A method as claimed in claim 17, characterized in that a predetermined server belonging to a network is assigned as an private key storage slave server, and wherein said method further comprises:

generating by a fourth user a fourth private-public key pair;

generating by said fourth user a passphrase, a random salt and a random puzzle with arbitrary puzzle size;

generating by said fourth user a secure hash, based on said passphrase, said random salt and said random puzzle;

encrypting said fourth private key by using said secure hash;

storing said encrypted fourth private key on said private key storage slave server together with said random salt and said puzzle size;

if-the fourth user desires to take back his encrypted private key from said private key storage slave server, then said method comprises;

requesting by said fourth user to said private key storage slave server said encrypted private key, said random salt, and said predetermined puzzle size;

sending by said private key storage slave server to said fourth user said private key, said random salt, and said puzzle size;

iterating for every possible choice of a puzzle, having said puzzle size, and generating for each iteration a hash, based on said passphrase, said random salt and said choosed puzzle, for each generated hash trying to decrypt said private key until the correct puzzle has been found.

22. A device for transmitting an electronic message from a sender node to at least one receiver node, said device comprising a sender node to which is assigned a first server carrying at least one sequence of instructions for transmitting said electronic message, said first server being able to add based on an attribute identifier, an attribute to said electronic message characterized in that said first server has a masterslave configuration comprising a set of slave servers, each slave server being provided for processing a predetermined attribute to said electronic message, each attribute corresponding each time to an attribute identifier pre-selected among a series of attribute identifiers, each attribute identifier of said series being associated with one of said slave servers, said master being provided for identifying based on said selected attribute identifier (s) among said set of slave servers to which said electronic message will be sent in order to be processed and for transmitting to this or those identified slave server (s) said electronic message, each of said identified slave servers being provided for processing said electronic message in order to incorporate said attribute into said electronic message and for transmitting said processed electronic message to said master server.

23. A device as claimed in claim 22, characterized in that said sender and receiver node are connected to a network comprising at least one further node to which a further server, having a master-slave configuration, is assigned and that said first master server is provided for verifying for each attribute identifier whether there is among his associated slave server (s), a slave server able to incorporate said attribute into said electronic message, and provided for searching, if said first server establishes that it lacks an associated slave server able to incorporate said attribute into said electronic message, among said further server (s), if one of them has at least one slave server (s) able to incorporate said attribute into said electronic message;

said first master server being provided for transmitting said electronic message to a dedicated further server able to incorporate said attribute into said electronic message, and provided for generating a first error message if said first server doesn'"'"'t find among said further server (s), any further server able to incorporate said attribute into said electronic message.

24. A device as claimed in claim 22, characterized in that said receiver node has a receiver server with a master-slave configuration provided for receiving and handling said electronic message.