Internships/ProjectIdeas/ImageAnonymization: Difference between revisions
DenisLunev (talk | contribs) |
DenisLunev (talk | contribs) |
||
| Line 1: | Line 1: | ||
=== Anonymization of virtual disk images === | === Anonymization of virtual disk images === | ||
'''Summary:''' Extend qemu-img utility to drop all data from the virtual disk while preserving image metadata | '''Summary:''' Extend qemu-img utility to drop all data from the virtual disk while preserving image metadata | ||
Revision as of 10:56, 27 January 2020
Anonymization of virtual disk images
Summary: Extend qemu-img utility to drop all data from the virtual disk while preserving image metadata
Virtual disk images like QCOW2 or QED comes into bad state during their lifecycle. This happens on the side of cloud or hosting provides and these images contains end-user (even not cloud provider) data. European cloud providers nowadays treat this under under terms of GDPR and these images could not be easily sent to developers for investigation.
The idea of this project is to drop all end-user data from images, including data blocks, memory inside internal snapshots etc. On the other hand, all bits and bytes of metadata of original image should be preserved even so-called "in-use" bit and other stuff.
It would be nice to have for QCOW2 disk formats but the task could be easily extended for other supported disk formats.
Links:
Details:
- Skill level: intermediate
- Language: C
- Mentor: Denis V. Lunev <den@openvz.org>
- Suggested by: Denis V. Lunev <den@openvz.org>