![]() ![]() GPG is an encryption toolbox, it is not an encryption algorithm! GPG is capable of producing both Public and Symmetric encryption. ".Can gpg encryption be harder to crack with GPU?." This suggests that Public Key cryptography is not required? You seem to be implying that Public Key cryptography is needed/desired by stating 3 gpg keys? You have quite a bit of confusion to work through here: You can put files there from any application like MS Office or Email client, and they will be automatically encrypted. If this is a risk, then you may prefer LUKS, because in that case you don't need to think about encryption all the time. Only you know, if this is an important risk to you. You can forget to encrypt some file and save it there in the plain form. When you encrypt every file separately, the file system remains unencrypted. But still you have to deal with the whole partition. You can optimize backups slightly if you use btrfs. ![]() In case of LUKS, for backups you would need to encrypt/decrypt the whole partition. To create backups you don't need to know the key and thus it can be easier to implement. You can check what has changed and each time backup only changed files. Only you know, if disclosing such information about your files makes any risk to you.Ĭreating backups in case 1 is much easier. In case of LUKS such information is not available to the attacker. do the files contain images, or videos, or a e-books, or saved web page, etc. This can give the attacker an information about what kind of data are encrypted (with high probability, but still not 100% sure), e.g. If you encrypt and store each file separately, the attacker will know how many files are there and how big they are. From this perspective there is no difference if you use a single file or image as a container or if you encrypt thousands or millions of files separately. Means, even if the attacker knows the contents of some files before and after encryption, it will not help to find the encryption key. Non-breakable means that even if you use the computing power in the whole world, the brute-forcing will take much more time than the Universe exists.ĪES is resistant to preimage attacks. The main difference is usability.Īll of the named methods can use AES, which is considered non-breakable. TLDR: From the cryptographic perspective, all your approaches can provide the same strength. In general I think luks made lots of compromise to speed it up, so encrypting files by gpg will be stronger. But for a cloud stored image we do not know when to react.Ĭan gpg encryption be harder to crack with GPU? Does it make difference if there are multiple files or just a single image? If someone cracked a single file or obtained clear text of one file, does it mean they can crack other files easier encrypt by the same gpg key? I think it should not be the case. Can they normally crack it in months or in years? Luks in general is ok for disk encryption because once the disk is stolen we can respond to it: start to change credentials to invalid as much as possible the information contained in the disk as an example. I do not know how hard it can be if one can use lots of GPUs to crack it. I often saw people were trying to use GPU to crack the luks partition since it is using some master key to encrypt bloks and the info stored in the first sector can help it even if one choose detached header. I would like to know which one is the most difficult one to defeat. We do not care if the decryption and encryption can be slower. However, here I do not want to discuss the robustness or convince. Personally I would say 1st is more robust because it is unlikely all files are corrupted at the same time. Let's assume the users' local systems are bulletproof. The header and keys are distributed offline. ![]() Everyone can hold a copy of the header and a pwd to a slot. We can use luks2 image with detached header.We can put files in a ext4 or btrfs image then encrypt it with 3 public keys.We can encrypted hundreds files by 3 public keys.Then we would like to encrypt the files or an small disk image (6-8gb). The cloud has very limited security measures so we consider all the files stored in it are public exposed. The update rate is very low, 1 per month. The total amount of data is small (<5gb in total). 3 people need to share some data through cloud. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |