ecryptfs-setup-private urandom reading error check fails

Bug #1539553 reported by halfgaar on 2016-01-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eCryptfs
Low
Unassigned

Bug Description

The shell script to setup a private directory reads from /dev/urandom and pipes it through od. The error handler on it only checks the result of od, not the reading from urandom. On failure, random_data=00000.

Related branches

Tyler Hicks (tyhicks) wrote :

Thanks for reporting this bug!

I've made it a regular, public bug because 1) this was already mentioned on the ecryptfs mailing list and 2) there's no security impact.

The random_data variable does not contain random bytes used for a key or anything along those lines. It is simply being used to perform a sanity check on the newly set up eCryptfs mount point. If random_data contains zeros, it is still a valid test to verify reading and writing to the mount point.

Changed in ecryptfs:
importance: Undecided → Low
status: New → Confirmed
information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers