ES2329149T3 - METHOD OF ENCRYPTION AND DATA TRANSFER BETWEEN AN ISSUER AND A RECEIVER USING A NETWORK. - Google Patents

Abstract

A method of encrypting and transferring data between a sender (100) and a receiver (200) using a network, the method comprises the steps of: - A server (300) receiving from the sender (100) an identifier of the receiver; - Establish a specific transfer encryption key (310) specific for the transfer; - Encrypt the data using the specific encryption key of the transfer (309); - The server (300) that accesses the specific information of the receiver (306) according to the identifier of the receiver sent by the sender and the encryption (314), with the specific information of the receiver, said transfer specific encryption key; - Transfer the encrypted data and the specific encryption key of the encrypted transfer over the network to be received by the receiver (200); Characterized by: - the server receives from the receiver the encryption key specific to the encrypted transfer and the receiver identifier; and - the server that accesses the specific information of the receiver (306) according to the identifier of the receiver sent by the receiver to decrypt the specific encryption key of the encrypted transfer (320); and ~ - decrypt the encrypted data using the specific encryption key of the decrypted transfer (323).

Description

Encryption method and data transfer between a sender and a receiver using a network.

The present invention refers to a method of encryption and data transfer between a sender and a receiver using a network that results in the transfer of data safely.

Currently more and more information is sent sensitive in electronic format from a sender to a receiver. In such circumstances, it is more important to ensure that the information cannot be intercepted or read by people not authorized, that is, the information must be transferred securely so that only sender and receiver can access the information content.

In one case, a link can be established. secure connection between a transmitter A and a receiver B before it produce the data transfer. However, in situations where, for example, 10 individuals in an office want communicate with and transfer sensitive information between them and to 10 people from another remote office in a two way way, there is the disadvantage of having to make additional hardware adjustments and software for so many secure connection links. Also this it takes considerable time and hardware resources to maintain such links and their associated password systems. This is especially true when the people in each office are connected simultaneously through some form of Intranet or Ethernet and offices communicate over the Internet. Too it is necessary to have an encryption and decryption software in the sender and the receiver, which requires additional hardware systems and software, and associated maintenance costs specialized.

In another case, an individual issuer wants transfer differentiated data to a plurality of receivers differentiated. However, this has the same disadvantages. mentioned above. Specifically, it is necessary that the issuer establish complex security provisions to maintain secure password systems. In addition, additional systems of hardware and software must be established to store and maintain such systems.

In fact, in the era of small devices and laptops, such as PDAs, mobile phones with access to Internet and capacity for emails, which have the capacity to limited processing and memory, often not technically possible to have the ease of secure two-way connections where high levels of encryption and decryption are implied.

While digital certificates can be used to reduce the demand on technical resources to sender and receiver, imply a cost that often can not justify the receiver, although this cost is small.

An alternative is for the issuer to encrypt the information to transfer and then send the encrypted data on a net. However, once again, the recipient must have resources from hardware processing available along with the memory so that the corresponding software be able to decrypt the information encrypted In addition, in situations where the receiver device have relatively poor hardware resources, assume resources valuable to allow a secure transfer of information to It is often not possible.

The use of complex encryption techniques and decryption requires the installation of special software on the device of the transmitter and in the receiver's apparatus. This is inconvenient and, It is also expensive. What's more, the installation procedure It can be complex and time-consuming, and it can cause conflicts with other software on its corresponding device. Further, additional software may require a level of calculation capacity which is not viable in the device and can occupy a valuable space of memory; this is especially true in the case of devices laptops mentioned above.

From the aforementioned it is clear that known methods and systems for data transfer safely require considerable commissioning, just like that an important computer process and local memory resources. This is clearly not suitable for those situations in which sender and / or receiver have a device with only a quantity limited of the available technical resources mentioned previously.

There is therefore a need for a method and system to transfer information in a secure way that you can reduce the level of technical resources required by the devices of the sender and / or receiver. Also, in the case that a public / private encryption key, the sender must be sure that the public key that you think belongs to the recipient has not been replaced by a public key of an intruder.

The functions of a known method to encrypt and transfer data between a sender and a receiver using a network are defined in the previous part of the characteristics of the claim 1 and are known from US 2003/0172262 that describes a secure communication system to send data from a client device to a receiver through a server distribution insurance The client device encrypts information using a secret key and encrypts the secret key using a public key associated with the server secure distribution The encrypted information and the secret key Encrypted along with the receiver data are sent to the server secure distribution that decrypts the secret key. The server of secure distribution then encrypts the secret key deciphered with the intended recipient's public key to display a password specific safe secret of the recipient. This, along with the encrypted information is subsequently sent to the receiver.

The functions that characterize this invention are defined in the features part of the claim 1.

Preferably, the method further includes establish a communication link between the sender and the server and send said receiver identifier to the server.

In one embodiment, the method further includes establish the communication link between the sender and the server To make it a secure link.

In one case, the method also includes establishing the communication link between the sender and the subject server that The server checks the sender's password.

In another embodiment, the method further includes establish a communication link between the receiver and the server and send said receiver identifier to the server.

In one case, the method also includes establishing a communication link between the receiver and the server so that Be a secure link.

In a particular case, the method also includes establish the communication link between the receiver and the server subject to the server checking the receiver password.

Preferably, the setting of the key Specific transfer encryption takes place at the sender and the specific encryption key of the established transfer is Send to server.

Otherwise, data encryption using the transfer-specific encryption key occurs in the
transmitter.

In a specific embodiment, the sender receives the encrypted transfer-specific encryption key from the server and the sender transfers the encrypted data and the encrypted transfer-specific encryption key to the receiver over the
net.

In another embodiment, the receiver receives from the server the specific encryption key of the decrypted transfer and the decryption of the encrypted data using the specific encryption key of the transfer occurs in the
receiver.

In another embodiment, the establishment of the Specific transfer encryption key occurs in the server.

In another specific case, encrypt the data using the transfer specific encryption key you Produces on the server.

In one embodiment, the server transfers the encrypted data and the specific encryption key of the transfer encrypted to the receiver over the network.

In another embodiment, decrypt the data encrypted using the specific encryption key of the decrypted transfer occurs on the server and the server transfers the encrypted information to the receiver.

Conveniently, the method also includes:

- set an authentication code value message (MAC) for data prior to encryption;

- transfer the MAC value together with the data encryption and the encryption key specific to the transfer; Y

- set a MAC value for the data after decryption and validate against the MAC value transferred.

         \ vskip1.000000 \ baselineskip
      

In one embodiment, the key encryption of Transfer specific encryption uses one or more methods of public key encryption, a blowfish algorithm, secret code of the server.

According to another aspect of the present invention, provides a method of operating a server to encrypt and transfer data between a sender and a receiver using a network, the method It includes the following steps:

- receive an identifier from the issuer receiver;

- access the specific information of the receiver according to the receiver identifier sent by the sender and encrypt, with the specific information of the receiver, a key of specific transfer encryption that is used to encrypt data;

         \ newpage
      

characterized by

- receive the encryption key from the receiver specific transfer and receiver identifier after the encrypted data and that the encryption key specific encrypted transfer have been transferred by the network for the receiver to receive;

- access the specific information of the receiver according to the receiver identifier sent by the receiver to decrypt the specific encryption key of the transfer encrypted

         \ vskip1.000000 \ baselineskip
      

In one embodiment, the method of operating a server also includes setting on the server a password of specific encryption specific transfer to the transfer.

In another embodiment, the method of operating a server also includes receiving an encryption key from the sender specific transfer specific transfer;

and transfer the specific encryption key from the encrypted transfer to the issuer.

Preferably, the method of operating a server It also includes encrypting data on the server using the key of specific encryption of the transfer.

In another preferred embodiment, the method of operating a server also includes transferring the encrypted data and the specific encryption key of the encrypted transfer over the network for the receiver to receive.

Preferably, the method of operating a server It also includes transferring the specific encryption key of decrypted transfer to the receiver.

In another embodiment, the method of operating a server also includes decrypting the encrypted data on the server using the specific encryption key of the transfer deciphered

According to another aspect of the present invention, provides a computer medium for an encryption method and data transfer between a sender and a receiver using a network, the medium includes:

- computer code to receive from the issuer a receiver identifier and set a specific key to specific encryption of the transfer to the transfer;

- computer code to encrypt the data using the specific encryption key of the transfer;

- computer code to access the specific information of the receiver according to the identifier of the receiver sent by the sender and encrypting, with the information specific to the receiver, said encryption key specific to the transfer;

- computer code to transfer the data encryption and transfer-specific encryption key encrypted over the network for the receiver to receive;

         \ vskip1.000000 \ baselineskip
      

characterized by

- the computer code to receive from receiver the encryption key specific to the encrypted transfer and the receiver identifier and to access the information specific receiver according to the receiver identifier sent by the receiver to decrypt the specific encryption key of the encrypted transfer; Y

- computer code to decrypt the data encrypted using the specific encryption key of the decrypted transfer;

         \ vskip1.000000 \ baselineskip
      

An example of the present invention is describe in detail with reference to the attached drawings, where:

Figure 1 shows a schematic diagram of a system that operates a method of the present invention by encrypting and transferring data between a sender and a receiver using a net;

Figure 2 shows a block diagram schematic of the server operating modules used in the Figure 1;

Figure 3 is a flow chart showing the processes involved in the sender and the server for the present invention and send data from the sender to the server;

         \ newpage
      

Figure 4 is a flow chart showing the processes involved in the receiver and the server in response to an email received from the server.

With reference now to figures 1 and 2, you are show a system that operates an embodiment of a method of encryption and transfer of data between a sender and a receiver using a network With reference to the drawings, the system works to encrypt and transfer data between a sender 100 and a receiver apparatus 200.

In this example, the emitting apparatus 100 comprises a computer 101 connected to a keyboard 107 and a data source 108 and an external display device 105. The source of data can include a disk reader of some kind or a connection interface to a data library, the data source stores the data to be transferred to the receiver. The 101 computer it has a general access bus 106 that connects to a microprocessor 102, a memory 103, a display interface 104, an input device interface 109 and a web browser 110 to connect to the Internet through a connection 111.

The interface of the display 104 is connected to the external display device 105 while the interface of input device 109 is connected to keyboard 107 and the source of data 108. Memory 103 will normally store the issuer identification and issuer password although these can be entered via keyboard 107 in response to display commands on the display device 105.

In this example, the receiver apparatus 200 comprises a mobile phone that has an Internet capability to through a web browser 210 that connects to the Internet through a connection 211.

The data on how said connection is established It is already well known in the field and will not be described here. He web browser connects to a general access bus 206 that is connects to a microprocessor 202, a memory 203, an interface of display 204 and an input device interface 209. The display interface 204 connects to a device Comprehensive display 205 while device interface input 209 connects to an integral keyboard 207. Memory 203 will normally store the receiver ID and password of the receiver although these can be entered through the keyboard 207 in response to display commands on the device display 205. The apparatus 200 further includes a customer of 212 email to send and receive emails through a 213 connection to Internet.

A server 300 is also connected to Internet through a connection 302. A block diagram Detailed structure of the server is shown in Figure 2. This server structure will be explained in combination with a description of the operation of this system invention.

With reference to figures 1 and 2, before use of the current system, both sender and receiver are registered initially with server 300 and its data is stored in a server database module 306. In this embodiment, the information stored includes at least one identification and one password for each sender and receiver.

The sender wishes to transfer data to the receiver saved in data source 108. For the sender to transfer the data, the issuer has to know the identification of the receiver and server web address 300. This information it can be stored in transmitter memory 103 or it can be entered manually via keyboard 107 in response to commands in the display device 105.

As shown in Figure 2, server 300 includes a 301 web server connected to the Internet through a connection 302. The web server connects to an input bus 303 and is controlled by means of a microprocessor 304. When the emitter contact the server's web address, a link is established secure as an SSL link, whose data is well known to subject matter experts. Microprocessor 304 does not allow access from sender to current system until module 305 has completed a password check along with access to the module of the database 306. The data of said password checks They are well known in the field and therefore will not be described here.

Upon completion of the verification of the password, server 300 sends the sender a visualization of the screen. Upon completing this screen, the sender sends the server the identity of the receiver together with the data to be transferred, which obtained from data source 108. These inputs are activated by the modules towards the upper edge of the figure.

Upon receiving the identification of the receiver and the data to be sent, microprocessor 304 sends the data to a module Message Authentication Code (MAC) generator 307. How I know known in the art, said generator produces a part of code which is calculated using part or all of the data in combination  with a cryptographic compendium algorithm. In the current case, the known MD hash algorithm is used to generate an MD hash value from the data. The MD hash value is sent to a client of 312 email connected to the Internet through a 316 link so that can be ready to process in a part of an email.

The received data is compressed in a module 308 before encrypted by module 309 using a password session obtained from a module 310. As is known in the art, the session key is generated from a random number, provided by a 311 random number generator. This key session is specific for this data and its transfer, by therefore, it becomes a specific encryption key of transfer. The encrypted data is sent accordingly to a email client 312 ready to process in a part of a e-mail.

The session key of module 310 is also figure in module 313 using the public key of a technique private key / public key encryption, for example, encryption RSA, which is well known in the field. From there, the exit from module 313 it is encrypted in module 314 using a blowfish algorithm that incorporates the receiver password that obtains from database 306. This password is agreed with the identification of the receiver sent from the microprocessor on bus 315. The encrypted session key is forwarded to the client of 312 email ready to process in a part of an email.

The email client 312 processes the MD hash value, the encrypted data and the encrypted session key in a way known to create an email that is then sent to the address suitable receiver provided by the microprocessor in the bus 315 after access to database 306. One way known, the email client assigns a unique label to the mail Electronic and charge shipping. A confirmation of the sending of the email it is also sent to the sender using web server 301 or the email client 312.

The mail sent by server 300 can normally received by email client 212 of the mobile phone 200. The content of the mail is established or to alert the receiver over a data transfer using the system the present invention or will automatically activate the browser web 210 to initiate a communication link with server 300. In any case, under the control of microprocessor 202, the receiver contacts the web address of the server and a secure link how to establish an SSL link, whose data is well known for experts in the field. The microprocessor server 304 does not allow access to the current system until a module 305 has completed a password check along with access to database module 306. Details about those Password checks are well known in the art and, therefore, they will not be described in this instrument.

Only after completing a successful check of the password, the encrypted data, the encrypted session key and the MD hash value contained in the mail are sent in the secure link to server 300 through a web server 301. These are activated by the modules towards the bottom edge of the figure.

It will be obvious that if the chosen method of sending and receiving emails is via web mail then it will not be necessary the separate email client 213.

At reception, microprocessor 304 forwards the encrypted session key to a module 320 that applies an algorithm inverted blowfish in combination with the receiver password that it is obtained from database 306 on bus 315 according to the receiver identification. The output of module 320 is decrypted later in module 321 using the private key of the RSA encryption used to send data. Under these modules, the original session key of module 310 is played.

The encrypted data received that is tablets are decrypted in module 323 using the key of session deciphered before being decompressed in module 324.

As with module 307, an MD hash value is generates in module 325 from the decompressed data and decrypted and under the control of microprocessor 304, module 326 perform a comparison check to validate the newly generated MD hash value versus MD hash value received from the receiver to ensure they match.

Assuming the MD hash value is correctly validated in module 326, the decrypted data of the Module 324 are returned to the receiver over the secure link.

Figure 3 is a flow chart showing the processes involved in the sender and the server for the present invention to send data from the sender to the server.

Initially, the issuer wishes to transfer the specific data to a specific receiver, having an identity of known receiver. In step S1A, the sender comes into contact with the server in an attempt to establish a secure link to communication, for example, an SSL link.

Establishing this link implies execution to through certain connection protocols and checking password mentioned above and can take the form of a viewing a web page on a display device 105, the entry of appropriate access data on the website and others. As mentioned earlier, the establishment of said communication link and password checking are very known to those skilled in the art and will not be described in detail in this document.

The server, in response to the contact from the sender, also try in step S1B to establish the link of communication through execution through certain connection protocols and password checking mentioned previously. The server will then check in step S2B to see if a valid link has been made, that is, that all communication protocols have been met and that all Password checks have been approved. If the link does not has been set, or if the password check failed, the Server goes to step S3B of Process Error. This step can involve other attempts to establish a communication link. Assuming a valid communication link is established, the process moves to step S4B to wait for the reception of the Identity of the receiver and the data to be transferred. It can include a Timing step at this point, if required.

At the issuer a check is made on the step S2A to also see if a valid link has been made, it is say that all communication protocols have been met and that all password checks have been approved. Yes the link has not been established, or if the password check failed, the sender goes to the step of S3A process error. Said step it may involve other attempts to establish a link to communication. Assuming a communication link is established valid, the process moves to step S4A to send the identity of the receiver and the data to be transferred. A step of Timing at this point, if required.

In an example, a transfer web page of data is displayed on the display device 105 which requires the entrance of the identification of the receiver and the union of the data, for example a file located in a data source 108. The data transfer page is then sent to the server 300. It will be apparent that the data to be encrypted can be entered directly on the data transfer page.

The content of the transfer page of data is received by server 300 in step S4B after the process proceed to step S5B. In this step, the server produces a single MD hash value for the data and sends the value to the client of email 312, after which the process proceeds to step S6B.

In step S6B the data is compressed, by example by zipping. Then, in step S7B a random number from the 311 random number generator is obtained to generate a session key that is specific to this transfer of data. Thereafter, in step S8B, the data is encrypted with this session key and then the encrypted data is sent to the email client 312.

The process then moves to step S9B in where the session key is encrypted using an RSA public key. Thereafter, the process moves to step S10B to retrieve the password of the receiver after which, in step S11B, the result of step S9B is encrypted with a blowfish algorithm using the password recovered in step S10B. The key to resulting encrypted session is then forwarded to the email client 312

In the next step S12B, an email was formulated in a known way to the 312 email client in a format suitable to be transferred by HTML, for example by encryption 64 base. You can also have an HTML attachment or code Online HTML for encrypted data and encrypted session key. The email is then sent and the email is loaded in a way usual, and the confirmation sent to the issuer, after which The process ends.

It will be apparent that the email contains the value MD hash, encrypted data and encrypted session key, preferably as hidden fields. The email also includes preferably an HTML link to allow the receiver to reconnect with the server. This link is configured to Automatically send hidden fields in HTML form to server. The email header is the header of the chosen subject by the issuer, and the email is addressed to the email address of the receiver.

In step S5A the issuer receives the confirmation of sending the email and the process ends.

Figure 4 is a flow chart showing the processes involved in the receiver and the server in response to An email received from the server.

In step S101A, receiver 200 receives the server email containing, among other things, the data Encrypted, encrypted session key and MD hash value. The email It can be downloaded either using the webmail or using the email client 212 on link 213. In step S102A, the receiver opens the email and contacts the server in a attempt to establish a secure communication link, by example, an SSL link. In a manner similar to that described previously, establishing this link implies execution through of certain connection protocols and a password check similar to the one discussed above in relation to module 305 and can take the form of a visualization of the web page in the display device 105, the input of the access data suitable on the website and others. As mentioned earlier, establishing said communication link and checking of the password are well known to those skilled in the art and They will not be described in detail here.

The server, in response to the contact from the receiver, also try in step S101B to establish the link of communication running through certain connection protocols and the password check mentioned above. The server then check step S102B to see if a valid link, that is, that all communication protocols have been met and that all password checks have been approved If the link has not been established, or if the Password check failed, server goes to Error step of process S103B. This step may involve other attempts to Establish a communication link. Assuming it is set a valid communication link, the process moves to step S104B to wait for the reception of the ID receiver and other information including encrypted data, encrypted session key and value hash MD. A timing step may be included at this point, if It is required.

At the receiver a check is made on the step S103A to also see if a valid link has been made, it is say that all communication protocols have been met and that all password checks have been approved. Yes the link has not been established, or if the password check failed, the sender goes to the process error step S104A. Said step it may involve other attempts to establish a link to communication. A timing step can be included in this point, if required.

Assuming a link is established from valid communication, the process moves to step S105A to send the identity of the receiver and the other information mentioned in the previous paragraph. The latter may be in the form of HTML fields hidden in the email, which are delivered to server 300. It will be Apparently the protocol for timing and arrangements to send identities, hidden fields, passwords etc, can be varied to fit with particular situations.

The process on the server then moves to step S105B to retrieve the module receiver password 306, after which, in step S106B, the encrypted session key It is decrypted with the blowfish algorithm using the password recovered in step S105B. The process then moves at a step S107B RSA decryption where the result of step S106B is decrypt using the server's private key. This causes that the session key is produced.

From then on, the process moves to S108B, where still compressed data is decrypted using the decrypted session key produced in step S107B. After this, the process moves to step S109B to decompress the data.

In the next step, S110B, the server produces a unique MD hash value for the data from step S109B. Starting then, in step S111B, the MD hash value of step S110B is Check against the MD hash value received in step S104B. Assuming that the MD hash value is validated, the process proceeds to step S113B and now the sender's encrypted data is sent to the receiver over the secure link. Sending this data enter and the process ends. If the MD hash value cannot be validated, the process branches to process error S112B. This may involve the error access and sending an error message to the receiver to indicate that the data could be corrupted or be in a committed situation.

In step S106A the receiver receives the data from Free access and the process ends.

In the embodiment of the described invention previously, the entire encryption and decryption process is develops on server 300. Therefore, the sender and receiver do not need any special software to send or receive data safely. In particular, it is not necessary to have the software, or use the hardware memory and resources of processed to allow RSA encryption and blowfish encryption. In addition, access to passwords is maintained and the server is not You need to stay at the issuer. Also, given that encryption and decryption occur on the server, the necessary provisions for encryption and decryption, the issuer and the receiver.

However, the present invention also covers the alternative of functions within box 317 of Figure 2 provided in the issuer. That is, in this modification, the generation of a session key from a random number generator and data compression and the Encrypted data compressed with that session key will perform all within the issuer. However, a secure link to the server as before, but in this case Only the generated session key is sent to the server. After the same password check as before, the modules S313 and S314 regenerate a session key that, in this case, they are returned to the issuer. The encrypted data, the session key  encrypted and hash value are then provided to the email client transmitter (not shown) that also connects to the Internet. This email client builds an email as before Send it to the receiver. Therefore, it can be seen that the steps of S5B to S8B in Figure 3 now take place at the sender. This can reduce the process demands set on the server.

The recipient receives the email in his client from email and can process the email as in figure 4.

However, the present invention also covers the alternative of functions with box 322 of the Figure 2 provided in the receiver once the email is Receive from server. That is, in this modification, decryption of data, data decompression, generation of a MD hash value and validation there, all this is carried out in the receptor. However, a secure link is established with the server as before, but in this case only the key to Encrypted session is sent to the server. After it password check as before, the S320 modules and S321 re-decrypt the session key which, in this case, is return to receiver Encrypted data is decrypted using the decrypted session key, an unpacked MD value, generated and reviewed its validity against the MD hash value received in the email. Therefore, it can be seen that steps from S108B to S113B in Figure 4 Now they occur in the receiver. This can reduce the demands of the process established on the server.

It will be appreciated that the two modifications mentioned above can be implanted at the same time. But nevertheless, with the present invention, the encryption of the session key, in combination with the receiver key, takes place in the server.

         \ newpage
      

It will be appreciated that a group of users can Sign up to receive emails when required. For example, him IT department of a company can register all employees. In this case, in the event that the verification of password fails on the server, the reference to other passwords in that group.

In the embodiments of the invention that require special software installed for the issuer or the receiver, as those skilled in the art know, this may download from the server during the registration process and then install.

It will be appreciated that since the correct password of the receiver to decrypt the data in the Blowfish algorithm and correct decryption is effectively checked validating the MD hash value, password checking during the link between the receiver and the server in step 102A can exempted, if required.

It will also be appreciated that if decryption does not succeeds, server 300 can be set to perform other checks to try to get the correct password, for example, looking for old passwords of the receiver and trying each one of them to decipher the data. If one of the passwords produces the correct MD hash value, then the decryption has succeeded. However, if none of those passwords works, then the receiver is not the receiver that intended or the data was corrupted during the transfer.

If the receiver does not have a password and is not yet registered on server 300, the server can generate a shot password that it sends to the receiver through any secure and appropriate means, for example, secure mail or through a secure link or through secure email, requiring the user to change their password to a secure password to use it thereafter.

With the present invention, the identities of the sender and receiver can be verified so that the sender can send data to a receiver that does not have special software installed, so that the receiver is sure of the origin of the data. In addition, encryption and decryption attempts are introduced, which can allow a sender to check if a receiver has received and decrypted the data and can allow the receiver Check if the data you expect to receive has already been delivered.

The transmitter and receiver device may have many ways, a non-exclusive list that includes, for example, a computer, a PDA or any other portable device, a Laptop, a mobile phone. The server is preferably a computer, although it can also be a type Alternative computing device.

It will be seen that with the present invention, neither the sender or receiver know the other's password, these are They keep on the server. Consequently, the level of security required by the sender and the receiver is not as high as others known ways to transfer data in a secure way.

With the present invention, the server maintains the specific information of the receiver, such as a password, that use the server in an encryption process. The server gets this information from a data source, which has a list of receiver identifications and specific information of the receiver, which is kept secret. The specific information of the receiver can understand a password, a passphrase, a PIN number, a hash value or any other information that goes to be used to verify identity.

The network used with the present invention can be the Internet, a local intranet like an Ethernet network, a network telephone, a radio network or any other type of network for transfer data Preferably, when using the Internet, a Secure SSL connection is used between the server and the sender and / or Between the server and the receiver.

Sender and receiver can be identified at server through your email addresses (or other network addresses). However, they can also have identification of users who are not related to their network addresses The server can have a list of network addresses in your database and / or you can have a list of user identifications, where the network address and / or User IDs are associated with information specific secret of the recipient.

In an embodiment of the present invention, the server 300 may include a single secret code for the server and that only the server knows. This secret code can be included in blowfish decryption and encryption modules. The secret code can be used in encryption in addition to using the information specific to the receiver. These two information documents can concatenated simply to use them in the encryption process. The use of secret code provides an improved level of security To the system.

It will be appreciated that the server does not need to retain the session key or any data sent to the receiver. These can be stored in a volatile memory on the server and be overwritten when other data and keys are encrypted. This has the advantage that the server does not need to have a lot of available memory to store old data and possibly redundant and / or keys.

The carrier device may comprise a transient medium, for example, a magnetic or acoustic signal, electromagnetic, RF, microwave, optical, electrical (for example, an IP TCP signal over an IP network such as the Internet), or a device carrier such as a floppy disk, CD ROM, hard drive, or device programmable memory

While the invention has been described in terms of what your preferred embodiments are currently, it will be clear to experts in the field that can be done several changes in preferred embodiments without leaving the scope of the invention, which is defined by the claims. The present invention can find application, for example, with mobile phone providers that can distribute reports monthly to mobile phone users safely, the Mobile phone user connects to the server to retrieve the encrypted report. Similarly, banks can distribute details of incoming payments to your customers that simply can connect to the server as described above to retrieve those details, distributing the details so safe.

Claims (25)

1. A method of encrypting and transferring data between a sender (100) and a receiver (200) using a network, the method Understand the steps of: - A server (300) that receives from the sender (100) a receiver identifier; - Set a specific encryption key for transfer (310) specific for the transfer; - Encrypt the data using the password specific transfer encryption (309); - The server (300) that accesses the information specific to the receiver (306) according to the identifier of the receiver sent by the sender and the encryption (314), with the information specific to the receiver, said encryption key specific to transfer; - Transfer the encrypted data and password specific encryption of the encrypted transfer over the network so that Received by the receiver (200); Characterized by: - the server receives the password from the receiver specific encryption of the encrypted transfer and the identifier of the receiver; Y - the server that accesses the information specific to the receiver (306) according to the identifier of the receiver sent by the receiver to decrypt the encryption key specific encrypted transfer (320); Y - decrypt the encrypted data using the encryption key specific to the decrypted transfer (323).

           \ vskip1.000000 \ baselineskip
        

2. A method according to claim 1 which It also includes establishing a communication link (111, 302) between the sender and the server and send said receiver identifier to server. 3. A method according to claim 2 which It also includes establishing the communication link between sender and server to be a secure link. 4. A method according to claim 2 or 3 which It also includes establishing the communication link between the issuer and the server subject to a server review of the password of the issuer (305). 5. A method according to any claim previous which also includes establishing a communication link (211, 302) between the receiver and the server and send said receiver to server identifier. 6. A method according to claim 5 which It also includes establishing the communication link between receiver and server to be a secure link. 7. A method according to claim 5 or 6 which It also includes establishing the communication link between the receiver and server subject to a password revision of the receiver over password (305). 8. A method according to any claim previous where the encryption key setting Specific transfer takes place at the issuer and the key to Specific transfer encryption set is sent to server. 9. A method according to any claim previous where the data encryption using the encryption key Specific transfer takes place at the issuer. 10. A method according to claim 9 wherein the sender receives the specific encryption key from the server encrypted transfer and the sender transfers the encrypted data and the specific encryption key of the encrypted transfer to the receiver on the network. 11. A method according to any of the claims 1 to 7 wherein the receiver receives from the server the decrypted transfer specific encryption key and the decryption of encrypted data using the encryption key specific of the decrypted transfer takes place in the receiver. 12. A method according to any of the claims 1 to 7 wherein the establishment of the key of specific encryption of the transfer takes place in the server. 13. A method according to claim 12 previous where to encrypt the data using the encryption key Specific transfer takes place on the server.

           \ newpage
        

14. A method according to claim 13 in where the server transfers the encrypted data and the encrypted key specific to the encrypted transfer to the receiver over the network. 15. A method according to any of the claims 1 to 10 and 12 to 14 wherein the decryption of the encrypted data using the specific encryption key of the decrypted transfer takes place on the server and the server Transfer the decrypted data to the receiver. 16. A method according to any claim previous which also includes: - set a code value (307) of message authentication (MAC) for data prior to encryption; - transfer the MAC value together with the data encryption and transfer-specific encryption key encrypted; and set a MAC value (325) for the data after decrypt and validate (326) against the transferred MAC value.

           \ vskip1.000000 \ baselineskip
        

17. A method according to any preceding claim wherein encrypting the transfer-specific encryption key employs one or more public key encryption methods, a blowfish algorithm, and a secret code of the
server. 18. A method of operating a server (300) to Encrypt and transfer data between a sender (100) and a receiver (200) Using a network, the method includes the following steps: - receive from the sender (100) an identifier of the receiver; - access the specific information of the receiver (306) according to the receiver identifier sent by the sender and encrypt (314), with the specific information of the receiver, a transfer specific encryption key that is used to encrypt data; Characterized by - receive the encryption key from the receiver (200) specific to the encrypted transfer and the identifier of the receiver after the encrypted data and the encryption key specific encrypted transfer have been transferred over the network for the receiver to receive; Access specific receiver information (306) according to the issuer identifier sent by the issuer to decrypt the specific encryption key of the transfer encrypted

           \ vskip1.000000 \ baselineskip
        

19. A method of operating a server according to the claim 18 further comprising setting on the server (310) a specific transfer specific encryption key to the transference. 20. A method of operating an agreement server with claim 18 further comprising receiving from the issuer a specific encryption key from transfer to transfer; and transfer the specific encryption key from the encrypted transfer to the issuer. 21. A method of operating an agreement server with one of claims 18 to 20 which further includes encrypting the data on the server (309) using the encryption key specific to the transfer. 22. A method of operating a server according to any one of claims 18 to 21 including transferring the encrypted data and the specific encryption key of the encrypted transfer over the network for reception by the
receiver. 23. A method to operate an agreement server with any of claims 18 to 22 which further includes transfer to the receiver the specific encryption key of the decrypted transfer. 24. A method to operate an agreement server with any of claims 18 to 22 which further includes decrypt the encrypted data on the server (323) using the Specific encryption key of the decrypted transfer. 25. A computer medium for a method of Encrypt and transfer data between a sender (100) and a receiver (200) Using a network, the medium includes: - computer code to receive from the issuer a receiver identifier and set an encryption key transfer specific (S7B) specific to the transfer; - computer code to encrypt the data using the specific encryption key of the transfer (S8B); - computer code to access the receiver specific information (S10B) according to the identifier of the receiver sent by the sender and the encryption (S11B), with the specific information of the receiver, said encryption key transfer specific; - computer code to transfer the data encryption and transfer-specific encryption key encrypted over the network (S12B) for reception by the receiver; characterized by - a computer code to receive from receiver (S101B) the specific encryption key of the transfer encrypted and the receiver identifier and to access the receiver specific information (S105B) according to the identifier of the receiver sent by the receiver to describe the key of specific encryption of the encrypted transfer (S106B); Y computer code to decrypt the data encryption (S108B) using the specific encryption key of the decrypted transfer.