Page 2 of 2

Re: [OPEN] Decryption time too long

Posted: Mon Jul 22, 2019 5:30 am
by erikdubois
That is strange...

I did it on real metal and on vb.

There is a difference in time for sure.

/boot should be on a separate partition with EXT2 non-encrypted. No flags.

That is the clue for a fast boot.

Just retried this morning. Still boots on 8 seconds. That is the fastest we can boot.

For me that is fast enough.

Re: [OPEN] Decryption time too long

Posted: Tue Jul 23, 2019 1:03 am
by fhins
Did you test this using KDE? I tested twice exactly the way you showed on the video, and wasn't any faster.

Re: [OPEN] Decryption time too long

Posted: Tue Jul 23, 2019 9:29 am
by erikdubois
Not KDE - I suppose you can see what I used in the video?



ArcoLinux

Re: [OPEN] Decryption time too long

Posted: Tue Jul 23, 2019 3:55 pm
by fhins
That's exactly my point. I tested this on KDE, May be i3 system setup is different than Plasma! Is it?

Re: [OPEN] Decryption time too long

Posted: Tue Jul 23, 2019 4:20 pm
by erikdubois
The packages are different - plasma is huge compared with i3.

the bigger it is - common sense - the longer it takes to decrypt?

only thing is compare notes

I will make a video about it and then we can compare again

plasma full or plasma minimal?

Re: [OPEN] Decryption time too long

Posted: Tue Jul 23, 2019 10:39 pm
by erikdubois
Again proof that on Plasma it take also 8 seconds to boot with encryption



Can it be your hardware?

Re: [OPEN] Decryption time too long

Posted: Thu Jul 25, 2019 4:26 am
by fhins
I reinstalled it on on my test 120 GB SSD hard drive again and it worked this time. it took about 6 seconds to get to the login screen. I'm not sure what I did wrong before! The only thing different was I gave 1000 MB to boot the first time, but but this time I designated 500 MB to boot. Could that have been the cause? Is this method of enrcryption setup as strong as if you encrypt the entire hard drive, including the boot?

Also how much do I need to designate to boot for on a 550 GIB or 1 TB SSD hard drive. Is 500 MB enough for both or is there a ratio that I can use for different size hard drives?

Thanks again for your tutorial videos, very informative! :D

Re: [OPEN] Decryption time too long

Posted: Thu Jul 25, 2019 6:14 am
by erikdubois
fhins wrote:
Thu Jul 25, 2019 4:26 am
I reinstalled it on on my test 120 GB SSD hard drive again and it worked this time. it took about 6 seconds to get to the login screen. I'm not sure what I did wrong before! The only thing different was I gave 1000 MB to boot the first time, but but this time I designated 500 MB to boot. Could that have been the cause? Is this method of encryption setup as strong as if you encrypt the entire hard drive, including the boot?

Also how much do I need to designate to boot for on a 550 GIB or 1 TB SSD hard drive. Is 500 MB enough for both or is there a ratio that I can use for different size hard drives?

Thanks again for your tutorial videos, very informative! :D
.
The only thing different was I gave 1000 MB to boot the first time, but but this time I designated 500 MB to boot
Could that have been the cause?

no

Is this method of enrcryption setup as strong as if you encrypt the entire hard drive, including the boot?

no - boot is not included - as a result more vulnerable - up for debate - either boot in 8 seconds or 18 seconds - your choice

Also how much do I need to designate to boot for on a 550 GIB or 1 TB SSD hard drive. Is 500 MB enough for both or is there a ratio that I can use for different size hard drives?

See the content of boot here it is 60MB - hence 500MB is 10 times as much as needed - enough reserve - does not depend on size of harddisk - does not become bigger because of the size of your harddisk.

Let us make a different topic for new questions, so future users will find it as well.

Re: [SOLVED] Decryption time too long

Posted: Mon Jul 29, 2019 6:24 pm
by BloodWolf
Hey. I know this isn't exactly a solution but if the time taken to decrypt is becoming a regular issue for you and encryption is required then I would suggest not encrypting the entire system at all.

Instead just install it normally and use veracrypt to create encrypted volumes/files that store the data you need to keep secure until you can find a proper solution. This means you get the performance benefits of an un-encrypted system and the portability of encrypted volumes with the security of encryption.

I hope this helps as a sort of stop-gap method until you can fix your issue.