LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 05-12-2018, 01:32 PM   #1
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 836
Blog Entries: 3

Rep: Reputation: 297Reputation: 297Reputation: 297
Hardware based encryption with SSD's, how is this working in relation to Linux?


Hi, i have one of these SSD's, a CRUCIAL® MX500 SSD. It worked out of the box for installing Slackware onto, literally plug and play.


I noticed in the spec for this model it mentions hardware based encryption;
http://eu.crucial.com/eur/en/storage-ssd-mx500
Quote:
Hardware-based encryption: Keep personal files and confidential data restricted from hackers and thieves with AES 256-bit encryption that meets all industry standards, including Microsoft® eDrive, IEEE1667, and TCG Opal 2.0.
I'm wondering how does this work? I haven't setup any additional encryption such as LUKS, and wondering how this protects my data from those "hackers and thieves".

If i disconnect the SSD and plug it into another computer, will the contents be readable? There was no password setup or anything like this. I literally plugged it into my SATA-3 cable, formatted as ext4 and installed Slackware.

How does this hardware encryption do anything?
 
Old 05-12-2018, 11:16 PM   #2
ballsystemlord
Member
 
Registered: Aug 2014
Distribution: Devuan
Posts: 214

Rep: Reputation: Disabled
Based on what I have read, and I don't claim to be an expert on the subject (and I did said reading about HDDs, not SSDs, but I'm assuming that the methodologies are the same), the SSD encrypts the data with a key that is accessible only to it's circuits until you set one. You can change the password to something only you know, but that must be done in the BIOS. Thus the "Evil Maid" attack is prevented, or rather, made more difficult.
 
Old 05-13-2018, 11:31 AM   #3
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 836

Original Poster
Blog Entries: 3

Rep: Reputation: 297Reputation: 297Reputation: 297
How would i set a password for the SSD in BIOS though? There doesn't seem to be any option to do anything like this.
 
Old 05-13-2018, 04:44 PM   #4
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
There are BIOS schemes to set a password on a hdd. That functionality is built into the drive itself as part of the ATA command set. But it only locks the drive. It doesn't encrypt anything. When the laptop is shut down, it locks the drive with the password that is installed by the user.

On self-encrypting drives, there is an encryption code within the drive. On every shutdown the drive is encrypted. On every boot, the drive is decrypted.

Depending on the motherboard and BIOS, such drives can be locked using the ATA security command set, which makes the drive inaccessible and encrypted until the password is entered, at which point the unprotected internal cipher key will decrypt the drive.

But there is also--on self-encrypting drives--an 'activation' or 'access' key that can be set to protect the cipher key. This is done through BIOS extensions named, OPAL 2.0.

The user password decrypts the activation key which decrypts the cipher key which decrypts the data on the drive.
On each shutdown or power loss, the password must be entered again.

OPAL 2.0 permits many options not offered by simple drive locking, such as multiple passwords for different areas of the drive, so manufacturers can reserve portions of storage for recovery utilities, spyware and hypervisor trojans. Just speculating a bit.

The access passwords can be easily reset, rendering the data on the drive destroyed, but the drive still usable.

In the older ATA security lock scheme, it is possible to issue a secure erase command to erase the drive and unlock it so it can be reused.




http://www.electronicdesign.com/memo...isk-encryption

Both schemes are equally secure; as secure as the password.

Last edited by AwesomeMachine; 05-15-2018 at 04:05 PM.
 
Old 05-14-2018, 01:39 PM   #5
sevendogsbsd
Senior Member
 
Registered: Sep 2017
Distribution: FreeBSD
Posts: 2,252

Rep: Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011Reputation: 1011
To also add in, drive encryption at the hardware or OS level only protects the drive contents (data) if the drive or computer are stolen. It won't prevent data from being stolen in a "hack attack" when the system is running.
 
Old 05-14-2018, 05:35 PM   #6
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 836

Original Poster
Blog Entries: 3

Rep: Reputation: 297Reputation: 297Reputation: 297
Quote:
Originally Posted by sevendogsbsd View Post
To also add in, drive encryption at the hardware or OS level only protects the drive contents (data) if the drive or computer are stolen. It won't prevent data from being stolen in a "hack attack" when the system is running.
I'm already aware of that, as with any encryption such as LUKS, whilst things are open in memory and actively being decrypted, yes any local software can access and read the contents. I'm just confused about built-in encryption, as my UEFI/BIOS doesn't give any sort of option for setting a password to the SSD. In essence i'm failing to understand the point of hardware based encryption if you can't actually protect the data on there.

I had a look a my device listing in the BIOS for any options relating to setting a password for the SSD, but haven't seen anything allowing me to do so.
 
Old 05-15-2018, 04:11 PM   #7
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
To work, self encrypting drives need a compatible BIOS. But there should still be an option to password protect the drive even if the BIOS doesn't have OPAL 2.0 extensions (self-encrypting drive functionality).
 
  


Reply

Tags
encryption, hardware, ssd



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
SSD - Full disk encryption(nightmare) untitled Slackware 8 01-29-2018 12:00 PM
SSD - Full disk encryption(nightmare) untitled Slackware 1 01-26-2018 05:09 AM
luks encryption on ssd deNiro Slackware 6 07-15-2011 11:42 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 01:05 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration