2,257
edits
Changes
Jump to navigation
Jump to search
Line 95:
Line 95: − + − TODO: Detailed description of the project.+ + + + + + + + + + + + − + − + − + −
→Anonymize image files
=== Anonymize image files ===
=== Anonymize image files ===
'''Summary:''' TODO: Short description of the project
'''Summary:''' Teach [[CRIT]] to remove sensitive information from images
When reporting a BUG it may be not acceptable for the reporter to send us raw images, as they may contain sensitive data. Need to teach CRIT to "anonymise" images for publication.
List of data to shred:
* Memory contents. For the sake of investigation, all the memory contents can be just removed. Only the sizes of pages*.img files are enough.
* Paths to files. Here we should keep the paths relations to each other. The simplest way seem to be replacing file names with "random" (or sequential) strings, BUT (!) keeping an eye on making this mapping be 1:1. Note, that file paths may also sit in sk-unix.img.
* Registers.
* Process names. (But relations should be kept).
* Contents of streams, i.e. pipe/fifo data, sk-queue, tcp-stream, tty data.
* Ghost files.
* Tarballs with tmpfs-s.
* IP addresses in sk-inet-s, ip tool dumps and net*.img.
'''Links:'''
'''Links:'''
* https://github.com/checkpoint-restore/criu/issues/360
* https://github.com/checkpoint-restore/criu/issues/360
* Wiki links to relevant material
* [[CRIT]]
* External links to mailing lists or web sites
* External links to mailing lists or web sites
'''Details:'''
'''Details:'''
* Skill level: beginner or intermediate or advanced
* Skill level: beginner
* Language: C
* Language: Python
* Mentor: Pavel Emelianov <xemul@virtuozzo.com>
* Mentor: Pavel Emelianov <xemul@virtuozzo.com>
* Suggested by: Pavel Emelianov <xemul@virtuozzo.com>
* Suggested by: Pavel Emelianov <xemul@virtuozzo.com>
=== Porting crit functionalities in GO ===
=== Porting crit functionalities in GO ===