TW201329776A - System and method for protection of file content security - Google Patents

Abstract

The present invention provides a method and system for protection of File content security. The methods includes: When you need to upload files, set files encryption type and the authorized users, then upload files; According to the encryption type described, encrypt files uploaded; Stored the files address and the encryption type and the authorized users information in the database configuration table; When users need to download the encrypted files, the authorized users information in the database configuration table will determine whether the users have the permission to download the encrypted files, without the permission, the users will be refused to download the files, Otherwise, users are granted to download the files; The encrypted files are downloaded to the client; Establish an independent storage in the client, decrypt the encrypted file according to the type of encryption in database configuration table, save the files in the independent storage at last.

Description

Method and system for protecting file content security

The present invention relates to a method and system for securing archive content during file transfer.

With the development of the Internet, the Internet and our daily lives are getting closer and closer, and we are used to transferring files over the Internet. Based on information security considerations, we don't want files to be stolen by others. The common method is to encrypt files. Traditional encryption methods include symmetric encryption and asymmetric encryption algorithms, but almost all cryptosystems are now breakable. It is easy for a third party to decipher the ciphertext through a certain algorithm, which will inevitably bring certain security risks to the user to transfer the file. Therefore, it is necessary to provide a more secure file transmission protection system.

In view of the above, it is necessary to provide a method and system for protecting the security of archive content in order to achieve content security during file transfer.

The method for protecting file content security includes the following steps: uploading step: when uploading a file, setting an file encryption type and an authorized user, and uploading the file; and encrypting: encrypting the uploaded file according to the encryption type; saving Step: storing the file upload address, encryption type, and authorized user information in the database configuration table; determining step: when the encrypted file needs to be downloaded, determining whether the user has permission to download the encrypted file according to the database configuration table information The file, if there is no permission, refuses to download, if there is permission, it is granted to download; download step: download the encrypted file to the user; decryption step: establish an independent storage area on the user side, according to the database configuration table The encryption type of the file decrypts the encrypted file to the independent storage area.

The protection file content security system, the system includes: an uploading module, configured to: when the file needs to be uploaded, set an encryption type and a user permission to download the file, and upload the file; the encryption module is configured to be used according to the The encryption type encrypts the uploaded file; the save module is used to store the file upload address, the encryption type, and the download user permission related information into the database configuration table; the judgment module is used when the encrypted file needs to be downloaded. According to the database configuration table information, it is judged whether the user has the permission to download the encrypted file, and if there is no permission, the download is refused, and if there is permission, the download is granted; and the download module is used to download the encrypted file to the file. The user terminal and the decryption module are configured to establish an independent storage area on the user end, and decrypt the encrypted file into the independent storage area according to the encryption type of the file in the database configuration table.

Compared with the prior art, the system and the method realize double protection of the file content by encrypting the file content and obtaining the data inventory, thereby ensuring that the file is more secure in the transmission process.

FIG. 1 is a functional block diagram of a preferred embodiment of a system for protecting file content security according to the present invention. The system is used for providing security for protecting file content during file transmission. The system includes an uploading module 10, an encryption module 12, a saving module 14, a determining module 16, a downloading module 18, and a decrypting module 20.

The uploading module 10 is configured to set an encryption type and a user permission for downloading the file, and upload the file, where the encryption type may be symmetric encryption or asymmetric encryption, or may be other encryption types. Symmetric encryption means that the same key can be used for encryption and decryption of information. The same encryption algorithm is used for encryption and decryption, also known as key encryption. The commonly used symmetric encryption algorithm is AES (Advanced Encryption Standard, AES), DEA. Encryption algorithms such as (Data Encryption Algorithm). An asymmetric encryption algorithm requires two keys: a public key and a private key. The public key is a pair with the private key. If the public key is used to encrypt the data, the corresponding private key can be used to decrypt it. If the private key is used to encrypt the data, the corresponding public key can be used. Decrypt. Because encryption and decryption use two different keys, this algorithm is called an asymmetric encryption algorithm.

The encryption module 12 is configured to encrypt the file uploaded by the user according to the encryption type selected by the user.

The encryption module 12 can also set the file parameters to record the size of the file when encrypting, so as to compare the file size during decryption and determine whether the file has been modified. In the process of encryption, we define a parameter to perform byte conversion on the original file size. When decrypting, we also use this parameter to perform byte conversion on the decrypted file size to determine whether the size of the files before and after is consistent.

The encryption module 12 can also be used to redefine the file type after encryption, so as to determine whether it is a previously encrypted file when decrypting. The encrypted file will be removed from the original file type and re-defined as a new file type, thus hiding the original file type.

The saving module 14 is configured to store the file upload address, the encryption type, and the download user permission information into the database configuration table for the user to download the file.

The judging module 16 judges whether the user has the permission to download the file according to the database configuration table information, and refuses to download if there is no permission, and grants the download if there is permission.

The download module 18 is configured to download the encrypted file to the client.

The decryption module 20 is configured to establish an independent storage area on the user end, and decrypt the encrypted file to the independent storage area according to the encryption type of the file in the database configuration table, and the encryption type may be symmetric encryption or asymmetric encryption. Other encryption types are also available, and the decryption module 20 selects the corresponding decryption algorithm to decrypt.

The decryption module 20 can also determine whether the file has been modified by comparing the encrypted file and the file size of the file parameter record that needs to be decrypted after downloading. In the process of encryption, we define a parameter to perform byte conversion on the original file size. When decrypting, this parameter also performs byte conversion on the decrypted file size to determine the file before encryption and the decryption after downloading. The file size is the same. If they are inconsistent, the user cannot be decrypted.

The decryption module 20 can also compare the newly defined file type of the encrypted file with the file type of the file to be decrypted after downloading, and determine whether the file is encrypted by the application before, and the encrypted file will remove the original file type. Re-defining a new file type, this hides the original file type. When we decrypt the encrypted file, we can judge whether the file to be decrypted after downloading is encrypted by our application according to the new file type. If not, the user is prompted to decrypt the file.

The system may also include a dedicated reader 22 for viewing the decrypted file content without performing other operations, and automatically deleting the decrypted file after viewing.

2 is a flow chart of a preferred embodiment of the method for securing archive content according to the present invention.

Step S200: When the file needs to be uploaded, the uploading module 10 receives the encryption type selected by the user and sets an authorized user of the file. The encryption type may be symmetric encryption or asymmetric encryption, or may be other encryption types. Symmetric encryption means that the same key can be used for encryption and decryption of information. The same encryption algorithm is used for encryption and decryption, also known as key encryption. The commonly used symmetric encryption algorithm is AES (Advanced Encryption Standard, AES), DEA. Encryption algorithms such as (Data Encryption Algorithm). An asymmetric encryption algorithm requires two keys: a public key and a private key. The public key is a pair with the private key. If the public key is used to encrypt the data, the corresponding private key can be used to decrypt it. If the private key is used to encrypt the data, the corresponding public key can be used. Decrypt. Because encryption and decryption use two different keys, this algorithm is called an asymmetric encryption algorithm. The above settings are used to determine whether the user has download permission when downloading the file and select the corresponding decryption method according to the encryption type.

Step S202: The encryption module 12 encrypts the file uploaded by the user according to the encryption type selected by the user.

The encrypting step S202 may further include: the encryption module 12 sets the file parameter to record the size of the file when encrypting, so as to compare the size of the encrypted file after the encrypted file and the downloaded file, and determine whether the file has been modified. In the process of encryption, a parameter is defined to perform byte conversion on the original file size. When decrypting, the parameter size of the file to be decrypted after downloading is also converted by the parameter to determine whether the size of the file before and after is consistent.

The encryption step S202 may further include: the encryption module 12 re-defines the file type after the encryption, so as to determine whether the file to be decrypted after the download is a previously encrypted file. The encrypted file will be removed from the original file type and redefined as a new file type, thus hiding the original file type.

Step S204: The save module 14 stores the file server address, the encryption type, and the authorized user information stored in the file after the file is uploaded into the database configuration table.

Step S206: When downloading the file, the database configuration table information determining module 16 determines whether the user has permission to download the file. If there is no permission, the operation flow is ended, and if there is permission, the download is permitted, and the process proceeds to step S208.

Step S208: The download module 18 downloads the encrypted file to the client.

Step S210: The decryption module 20 establishes an independent storage area on the user side, and decrypts the file to the established independent storage area according to the encryption type of the file. In this step, the file is decrypted according to the encryption type of the file recorded in the database configuration table, and the encryption type may be other encryption types such as symmetric encryption and asymmetric encryption, and the decryption module selects the corresponding decryption algorithm to decrypt.

The decrypting step S210 may further include: the decryption module 20 compares the files that need to be decrypted after being encrypted and downloaded according to the file size recorded in the file parameter set in step S202, and determines whether the file has been modified. In the process of encryption, we define a parameter to perform byte conversion on the original file size. When decrypting, we also use this parameter to perform byte conversion on the file size that needs to be decrypted after downloading to determine the size of the encrypted file and The size of the files that need to be decrypted after downloading is consistent. If they are inconsistent, the user cannot be decrypted.

The decrypting step S210 may further include: the decryption module 20 determines whether it is a previously encrypted file by comparing whether the new file type redefined in step S202 and the type of the file to be decrypted are consistent. The encrypted file will be removed from the original file type and redefined as a new file type. This hides the original file type. When we decrypt the encrypted file, we can decrypt the file type and redefine the file according to the need. Whether the file type is consistent to determine whether the file to be decrypted is a previously encrypted file, and if not, the user cannot be decrypted.

After the step S210, the foregoing embodiment may further include step S212: viewing the decrypted file by using a dedicated reader, the reader can only view the file content and cannot perform other operations, and automatically delete the decrypted file after viewing.

In summary, the present invention complies with the requirements of the invention patent and submits a patent application according to law. The above is only the preferred embodiment of the present invention, and the scope of the present invention is not limited to the above-described embodiments, and equivalent modifications or variations made by those skilled in the art in light of the spirit of the present invention are It should be covered by the following patent application.

10. . . Upload module

12. . . Cryptographic module

14. . . Save module

16. . . Judging module

18. . . Download module

20. . . Decryption module

twenty two. . . Reader

S200. . . Set file encryption type and authorized users, and upload files

S202. . . Encrypt the uploaded file

S204. . . Store the file upload address, encryption type, and authorized user information in the database configuration table.

S206. . . Determine if the user has permission to download the file

S208. . . Download file to client

S210. . . Establish an independent storage area on the user side, decrypt the file to the established independent storage area

S212. . . View the decrypted file with a dedicated reader

1 is a functional block diagram of a preferred embodiment of a system for securing file content according to the present invention.

2 is a flow chart of a preferred embodiment of the method for securing archive content according to the present invention.

S200. . . Set file encryption type and authorized users, and upload files

S202. . . Encrypt the uploaded file

S204. . . Store the file upload address, encryption type, and authorized user information in the database configuration table.

S206. . . Determine if the user has permission to download the file

S208. . . Download file to client

S210. . . Establish an independent storage area on the user side, decrypt the file to the established independent storage area

S212. . . View the decrypted file with a dedicated reader

Claims (12)

A method of securing archive content, the method comprising the steps of:
Upload step: When you need to upload files, set the file encryption type and authorized users, and upload files;
Encryption step: encrypting the uploaded file according to the encryption type;
The saving step: storing the file upload address, the encryption type, and the authorized user information in the database configuration table;
Judgment step: when the encrypted file needs to be downloaded, it is judged according to the database configuration table information whether the user has the permission to download the encrypted file, and if there is no permission, the download is refused, and if there is permission, the download is permitted;
Download step: download the encrypted file to the client;
Decryption step: establishing a separate storage area on the user side, and decrypting the encrypted file to the independent storage area according to the encryption type of the file recorded in the database configuration table. The method for protecting the content of the file as described in claim 1, wherein the encrypting step further comprises: setting an file parameter during encryption to record the size of the file. The method for protecting the content security of the file according to the second aspect of the patent application, wherein the decrypting step further comprises: comparing the encrypted file according to the file size recorded by the file parameter set at the time of encryption, and comparing the encrypted file after downloading Whether the size is the same, so as to determine whether the file has been changed, if the change, the user is unable to decrypt. The method for protecting the content of a file as described in claim 1 or 2, wherein the encrypting step further comprises: re-defining the file type after the encrypted file. The method for protecting file content security according to claim 4, wherein the decrypting step further comprises: comparing whether the file type re-defined after encryption is consistent with the downloaded file type to be decrypted, and determining the downloaded Whether the file to be decrypted is a previously encrypted file, if not, the user cannot be decrypted. The method for protecting the content security of the file as described in claim 1, wherein the method further comprises the following steps after the decrypting step:
Use a dedicated reader to view the decrypted file. The reader can only view the contents of the file, and cannot perform other operations. After the view, the decrypted file is automatically deleted. A system for protecting the security of archive content, wherein the system comprises:
The uploading module is configured to set an encryption type and a user permission to download the file when uploading the file, and upload the file;
An encryption module, configured to encrypt the uploaded file according to the encryption type;
The saving module is configured to store the file upload address, the encryption type, and the download user permission related information into the database configuration table;
The judging module is configured to judge whether the user has permission to download the encrypted file according to the information of the database configuration table when downloading the encrypted file, and refuse to download if there is no permission, and grant the download if there is permission;
The download module is configured to download the encrypted file to the user end;
The decryption module is configured to establish an independent storage area on the user end, and decrypt the encrypted file into the independent storage area according to the encryption type of the file in the database configuration table. The system for protecting the content of the file as described in claim 7 , wherein the encryption module is further configured to set a file parameter to record the size of the file when encrypting. The system for protecting the content of the file as described in claim 8 , wherein the decryption module is further configured to compare the encrypted file and the file to be decrypted after the download according to the file size recorded by the file parameter set during encryption. Size, to determine whether the file has been changed, if changed, prompt the user can not decrypt. The system for protecting the content of the file as described in claim 7 or 8, wherein the encryption module is further configured to redefine the file type of the encrypted file. The system for protecting the content of the file as described in claim 10, wherein the decryption module is further configured to compare the file type redefined by the encrypted file with the file type that needs to be decrypted after downloading, and determine whether it is previously encrypted. The file, if not, prompts the user to not decrypt. The system for protecting the content of the file as described in claim 7 of the patent application, wherein the system further comprises a special reader, the reader can only view the content of the file and cannot perform other operations, and automatically delete the decrypted file after viewing.