Abstract
We remark that the identity-based integrity auditing and data sharing scheme [IEEE TIFS, 14(2), 331-346, 2019] is awed. The scheme needs to introduce the sanitizer for sanitizing the sensitive information in the files from its employees. But we find the data owner cannot properly retrieve his data from the cloud server because the sanitized files are generated by simply replacing the sensitive information with stuffing strings, instead of using a reversible transformation to encrypt the files. In the proposed model, the auditor who is responsible for checking the data integrities of uploaded files from all clients, seems unnecessary because a transferred file between a client and a server is generally encrypted and signed via the default protocol (HTTPS), which suffices to ensure data integrity. Moreover, the over-sanitized files are usually considered useless because they cannot be utilized by other users for big data mining and big data analysis.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
