Review History


All reviews of published articles are made public. This includes manuscript files, peer review comments, author rebuttals and revised materials. Note: This was optional for articles submitted before 13 February 2023.

Peer reviewers are encouraged (but not required) to provide their names to the authors when submitting their peer review. If they agree to provide their name, then their personal profile page will reflect a public acknowledgment that they performed a review (even if the article is rejected). If the article is accepted, then reviewers who provided their name will be associated with the article itself.

View examples of open peer review.

Summary

  • The initial submission of this article was received on March 15th, 2024 and was peer-reviewed by 2 reviewers and the Academic Editor.
  • The Academic Editor made their initial decision on April 25th, 2024.
  • The first revision was submitted on May 30th, 2024 and was reviewed by 2 reviewers and the Academic Editor.
  • A further revision was submitted on July 4th, 2024 and was reviewed by 1 reviewer and the Academic Editor.
  • The article was Accepted by the Academic Editor on July 13th, 2024.

Version 0.3 (accepted)

· Jul 13, 2024 · Academic Editor

Accept

The reviewer agreed to accept the paper and I agree with them

[# PeerJ Staff Note - this decision was reviewed and approved by Sedat Akleylek, a 'PeerJ Computer Science' Section Editor covering this Section #]

Reviewer 1 ·

Basic reporting

no comment

Experimental design

no comment

Validity of the findings

no comment

Cite this review as

Version 0.2

· Jun 23, 2024 · Academic Editor

Minor Revisions

The manuscript shows potential but needs revision to address the identified issues. A comprehensive review focusing on grammatical correctness, consistency in verb tenses, and the refinement of expressions is necessary to elevate the manuscript's quality.

[# PeerJ Staff Note: The review process has identified that the English language must be improved. PeerJ can provide language editing services if you wish - please contact us at [email protected] for pricing (be sure to provide your manuscript number and title). Your revision deadline is always extended while you undergo language editing. #]

Reviewer 1 ·

Basic reporting

Although the authors have made various optimizations and improvements in this version, the manuscript still faces some unresolved issues:
1. There are still some grammatical errors in the manuscript, such as line 37. To ensure the delicacy and rigor of the manuscript, the authors need to re-review the entire text to improve its overall quality.
2. The use of tenses in the manuscript appears to be quite chaotic, such as the present tense on line 117 and past tense on line 119 within the related work section. It is recommended that the authors carefully review the entire manuscript again to ensure consistency and accuracy in verb tense usage.
3. There is still room for improvement in certain expressions in the manuscript, such as line 33. To ensure the manuscript's high quality, the authors should re-check the manuscript.

Experimental design

no comment

Validity of the findings

no comment

Cite this review as

Reviewer 2 ·

Basic reporting

no comment

Experimental design

no comment

Validity of the findings

no comment

Additional comments

The authors have addressed the concerns I raised.

Cite this review as

Version 0.1 (original submission)

· Apr 25, 2024 · Academic Editor

Major Revisions

The manuscript explores a meaningful topic in the realm of cloud storage, namely searchable encryption, yet several crucial aspects require improvement. Firstly, the research work lacks thoroughness in highlighting differences from previous studies and overlooks key literature, such as a reference employing a multiset hash function for verifiability of search results, diminishing its academic value. Secondly, the organizational structure and writing standards need refinement to enhance readability and clarity. Thirdly, ambiguities in algorithm syntax and security definitions hinder comprehension, while the security analysis section lacks formal rigor. Moreover, questions arise regarding the motivation and contributions of the work, the practicality of the system model, and the role of blockchain immutability in ensuring reliable search results. Addressing these concerns will bolster the manuscript's academic rigor and contribution to the field.

[# PeerJ Staff Note: It is PeerJ policy that additional references suggested during the peer-review process should only be included if the authors are in agreement that they are relevant and useful #]

Reviewer 1 ·

Basic reporting

In the context of cloud storage, searchable encryption has significant practicality, and the topic discussed in this manuscript is very meaningful. However, there are still several aspects that need to be improved.
1. The research work of the manuscript is slightly insufficient, failing to highlight the differences from previous studies, and missing some key literature, such as the reference with DOI: 10.1109/TCC2022.3170362.

**PeerJ Staff Note:** It is PeerJ policy that additional references suggested during the peer-review process should only be included if the authors are in agreement that they are relevant and useful

In this scheme, the authors also employed a multiset hash function to achieve verifiability of search results. The insufficient research in the manuscript has to some extent weakened its academic value and persuasiveness.
2. The organizational structure of the manuscript still needs to be optimized, lacking clear section arrangements and content introductions, making it difficult for readers to quickly grasp the context and key points of the article while reading.
3. The writing standards of the manuscript also need to be improved. For example, using some abbreviations is not standardized enough, which may confuse readers in understanding.
4. In terms of algorithm syntax definition, the sources of K_2 and K_3 are not clearly explained, which increases the difficulty for readers to understand the algorithm.
5. In the security definition section, the definition of the leakage function is missing, resulting in a lack of the necessary theoretical basis for security analysis.
6. The security analysis section of the manuscript appears to be not formal enough, lacking rigorous mathematical derivation and proof, which affects the persuasiveness of the article.
7. The format of references is not uniform, and some references lack key information such as page numbers, which to some extent affects the academic rigor of the manuscript.

Experimental design

no comment

Validity of the findings

no comment

Cite this review as

Reviewer 2 ·

Basic reporting

no comment

Experimental design

no comment

Validity of the findings

no comment

Additional comments

1. Unclear motivation and contributions. This work is motivated by the need to verify the search results, and one of the main contributions is to enable reliable verification of phrase search results, as stated by the authors. However, the recent proposal [9] has enabled the data user to verify the phrase search results even when the server is malicious and tries to fabricate the verification. What is the difference between [9] and this work?

2. Impractical system model. In the defined model, the blockchain is responsible for performing computation for a phrase search in parallel. It generates the verification value in order to validate the search results generated by the server. This requires a certain computational capability, which the blockchain is not assumed to have in a common setting. The blockchain in the defined model is actually a trusted entity needed to perform computational tasks, which is impractical in the real world. Besides, the authors consider the data user to be not trustworthy as it may falsify verification results for financial gain. Why the data user can benefit from it?

3. Another question. The authors say that due to the immutability of data on the blockchain, the composite index stored and search results calculated by the blockchain are reliable. Why the immutability of blockchain can ensure that the search results are reliable? Isn't the reliability of the results guaranteed by the algorithm?

Cite this review as

All text and materials provided via this peer-review history page are made available under a Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.