diff --git a/_conferences/pets.md b/_conferences/pets.md new file mode 100644 index 0000000..7c56250 --- /dev/null +++ b/_conferences/pets.md @@ -0,0 +1,33 @@ +--- +title: PETS +--- + + + +The annual Privacy Enhancing Technologies Symposium (PETS) introduced artifact +evaluation in 2020. + +### Overview of changes + +- 2026: clarification for badges requirements, modification of the + [`ARTIFACT_APPENDIX.md`](./pets2026/ARTIFACT-APPENDIX.md), introduction of an + [FAQ](./pets2026/faq.md), sharing of [repository examples for Docker and other + resources](https://github.com/PoPETS-AEC/examples-and-other-resources) . +- 2025: switch to Artifact: Available, Artifact: Functional, and Artifact: Reproduced badges, introduction of + Artifact Award Runner-ups, introduction of Distinguished Artifact Reviewers. +- 2024: switch to Artifact: Available and Artifact: Reproduced badges. +- 2022: introduction of Artifact Award. +- 2020: introduction of a single artifact badge. + +For more details, refer to the respective call for artifacts. \ No newline at end of file diff --git a/_conferences/pets2020/aec-call.md b/_conferences/pets2020/aec-call.md new file mode 100644 index 0000000..f66b85a --- /dev/null +++ b/_conferences/pets2020/aec-call.md @@ -0,0 +1,38 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Guidelines + +For PoPETs 2020, we'll be doing a soft start with artifact reviews and will only +be performing very basic checks for the proper documentation, licensing, and +compilation of artifacts rather than doing an in-depth analysis of the source +code and the reproducibility of results in the paper. For all artifacts, authors +should submit the following: + +- A copy of your paper or a brief description of how the artifact is relevant to + it. +- A link to where the artifacts are publicly hosted. + +For source code submissions, authors should additionally submit the following: + +- Licenses that allow the code to be made public and used by other groups + wishing to reproduce or build on the results. +- A build environment such as a virtual machine or a Docker container that has + been configured with all the prerequisites necessary to build and run the + code. +- If the code is interpreted, some simple inputs so that the reviewers can + verify that the code runs. We want to make sure that the code will execute + without error, not that the outputs are necessarily correct. +- A README or other documentation that describes how to build and/or run the + code. Reviewers should be able to build compiled code in the provided + environment by following instructions in a README or INSTALL file. For + interpreted code, the program(s) should run without error on the provided + inputs. + +For dataset submissions, authors should additionally submit the following: + +- Clear documentation that would allow researchers working on similar problems + to re-use the dataset for their work. +- Optionally, data processing scripts. \ No newline at end of file diff --git a/_conferences/pets2020/index.md b/_conferences/pets2020/index.md new file mode 100644 index 0000000..9f7446c --- /dev/null +++ b/_conferences/pets2020/index.md @@ -0,0 +1,29 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +This year, we've formed an artifact review committee for the purpose of +collecting, evaluating, and displaying any artifacts related to accepted papers +and we encourage you to submit your artifacts for review. The goal of this +process is to provide a way for authors to share any work beyond the contents of +the paper itself that aid in the reproducibility of results and allow other +researchers or community members to build on the work reflected in the paper. + +Possible artifacts include (but are not limited to): + +- source code (e.g., system implementations, proof of concepts) +- datasets (e.g., network traces, raw study data) +- scripts for data processing or simulations +- machine-generated proofs +- formal specifications +- build environments (e.g., VMs, Docker containers, configuration scripts) + +Submission of artifacts is encouraged but optional, and artifacts will be +evaluated by the artifact review committee so that we can provide feedback on +possible bugs in the build environment, readability of documentation, and +appropriate licensing. After your artifact has been approved by the committee, +we will accompany the paper link on +[petsymposium.org](https://petsymposium.org/) with a link to the artifact along +with an artifact badge so that interested readers can find and use your hard +work. \ No newline at end of file diff --git a/_conferences/pets2020/organizers.md b/_conferences/pets2020/organizers.md new file mode 100644 index 0000000..f2d36b3 --- /dev/null +++ b/_conferences/pets2020/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 20 +redirect_to: https://petsymposium.org/cfp20.php +--- \ No newline at end of file diff --git a/_conferences/pets2020/results.md b/_conferences/pets2020/results.md new file mode 100644 index 0000000..dc32f60 --- /dev/null +++ b/_conferences/pets2020/results.md @@ -0,0 +1,123 @@ +--- +title: Results +order: 30 +artifacts: + + - paper_url: "https://petsymposium.org/2020/files/papers/issue4/popets-2020-0059.pdf" + title: "PriFi: Low-Latency Anonymity for Organizational Networks" + artifact_url: "https://github.com/dedis/prifi" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue3/popets-2020-0054.pdf" + title: "dPHI: An improved high-speed network-layer anonymity protocol" + artifact_url: "https://github.com/AlexB030/dPHI" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0019.pdf" + title: "Protecting against Website Fingerprinting with Multihoming" + artifact_url: "https://github.com/sebhenri/HyWF" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0023.pdf" + title: "A Framework of Metrics for Differential Privacy from Local Sensitivity" + artifact_url: "https://pleak.io/wiki/" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue4/popets-2020-0058.pdf" + title: "Automatic Discovery of Privacy-Utility Pareto Fronts" + artifact_url: "https://github.com/amzn/differential-privacy-bayesian-optimization" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue4/popets-2020-0075.pdf" + title: "Secure Evaluation of Quantized Neural Networks" + artifact_url: "https://github.com/anderspkd/SecureQ8" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue3/popets-2020-0043.pdf" + title: "Tik-Tok: The Utility of Packet Timing in Website Fingerprinting Attacks" + artifact_url: "https://github.com/msrocean/Tik_Tok" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue1/popets-2020-0013.pdf" + title: "Website Fingerprinting with Website Oracles" + artifact_url: "https://github.com/pylls/wfwo" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue4/popets-2020-0066.pdf" + title: "Effective writing style transfer via combinatorial paraphrasing" + artifact_url: "https://gitlab.com/ssg-research/mlsec/parchoice/" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0025.pdf" + title: "Differentially Private SQL with Bounded User Contribution" + artifact_url: "https://github.com/google/differential-privacy" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0033.pdf" + title: "Mind the Gap: Ceremonies for Applied Secret Sharing" + artifact_url: "https://git-crysp.uwaterloo.ca/ckomlo/VerifiableSecretSharing" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue3/popets-2020-0055.pdf" + title: "Tandem: Securing Keys by Using a Central Server While Preserving Privacy" + artifact_url: "https://github.com/spring-epfl/tandem" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0017.pdf" + title: "NoMoATS: Towards Automatic Detection of Mobile Tracking" + artifact_url: "https://athinagroup.eng.uci.edu/projects/nomoads/" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0021.pdf" + title: "The TV is Smart and Full of Trackers: Measuring Smart TV Advertising and Tracking" + artifact_url: "https://athinagroup.eng.uci.edu/projects/smarttv/" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0024.pdf" + title: "Secure and Scalable Document Similarity on Distributed Databases: Differential Privacy to the Rescue" + artifact_url: "https://github.com/schoppmp/private-knn" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue3/popets-2020-0053.pdf" + title: "Protecting Private Inputs: Bounded Distortion Guarantees With Randomised Approximations" + artifact_url: "https://github.com/pahfat/PoPETs2020.git" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue4/popets-2020-0070.pdf" + title: "When Speakers Are All Ears: Characterizing Misactivations of IoT Smart Speakers" + artifact_url: "https://github.com/djdubois/smart-speakers-study" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0039.pdf" + title: "A Tale of Two Trees: One Writes, and Other Reads. Optimized Oblivious Accesses to Large-Scale Blockchains" + artifact_url: "https://github.com/TEE-3/T3" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0020.pdf" + title: "Explaining the Technology Use Behavior of Privacy-Enhancing Technologies: The Case of Tor and JonDonym" + artifact_url: "https://pape.science/paper/HPR20pets/" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue2/popets-2020-0016.pdf" + title: "A Comparative Measurement Study of Web Tracking on Mobile and Desktop Environments" + artifact_url: "https://github.com/jun521ju/PETS2020_Web_Tracking" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue1/popets-2020-0004.pdf" + title: "The Privacy Policy Landscape After the GDPR" + artifact_url: "https://github.com/wi-pi/GDPR" + + - paper_url: "https://petsymposium.org/2020/files/papers/issue3/popets-2020-0049.pdf" + title: "Mitigator: Privacy policy compliance using trusted hardware" + artifact_url: "https://git-crysp.uwaterloo.ca/miti/mitigator" + +--- + +Results obtained from PETS 2020 proceedings. + + + + + + + + + + {% for artifact in page.artifacts %} + + + + + {% endfor %} + +
TitleArtifact URL
+ {% if artifact.paper_url %} + {{artifact.title}} + {% else %} + {{ artifact.title }} + {% endif %} + + {% if artifact.artifact_url %} + artifact + {% endif %} +
diff --git a/_conferences/pets2021/aec-call.md b/_conferences/pets2021/aec-call.md new file mode 100644 index 0000000..7d11b3a --- /dev/null +++ b/_conferences/pets2021/aec-call.md @@ -0,0 +1,48 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Guidelines + +- All submitted artifacts should be relevant to their corresponding PoPETs + paper. Please provide a copy of your paper or a brief description of how the + artifact is relevant to it in your submission. +- Many papers have several artifacts (e.g., multiple source code repositories, + datasets, build environments), which is great! Please keep in mind that we'll + need a single link to put on the PETS website and that all artifacts + associated with your paper should be discoverable from that link. +- All submitted artifacts should be submitted by providing a link to where the + artifacts are publicly hosted. +- Please include a README with your submission that briefly explains the type + and purpose of the artifact (e.g., whether it's a proof of concept + implementation, scripts for generating graphs, or datasets for reproducing + results). +- All artifacts must be immediately available to the public and **should not** + be behind any kind of paywall or restricted access. If the artifact requires + you as an author to manually approve requests for access, it is not public and + will not qualify as a PoPETs artifact submission. If you have concerns or + questions about this please contact us directly. + +### Source Code Submissions + +- All source code should be accompanied by a README or other documentation that describes how to build and/or run the code. Reviewers will provide feedback on the clarity of the instructions and attempt to follow them and build and/or run the code. +- Any source code submissions should be accompanied with a build environment such as a virtual machine (recommended) or a Docker container that has been configured with all the dependencies and prerequisites necessary to build the code. +- If you use a virtual machine, please state how many resources it will consume and any configuration steps that are required. Your virtual machine should not usually have to download additional dependencies when you run your install scripts. If that is the case, reassess your build process and consider making changes to limit the amount of network resources needed. +- If the code is in a compiled language, the code should compile in the provided build environment by performing the provided instructions. +- If the code is interpreted, please provide some simple inputs so that the reviewers can verify that the code runs without error. We want to make sure that the code will execute without error, not that the outputs are necessarily correct. +- Compilation and setup should be automated as much as possible. Ideally, there will be one script that builds your software and runs your tests. +- Please ensure your code has an open source license and clearly states this information. The following resources may help you to choose a license: + - For a clear, easy to follow guide see: [https://choosealicense.com/](https://choosealicense.com/) + - For more in-depth detail on open source and copy-left licenses, see [https://www.gnu.org/licenses/license-list.en.html](https://www.gnu.org/licenses/license-list.en.html) and [https://opensource.org/licenses](https://opensource.org/licenses) +- Our goal with these artifacts is for them to be useful as far into the future as possible. Some tips on improving the longevity of your source code artifact are: + - Include the versions of your software's dependencies wherever possible + - Mention specific hashes of git commits that match the state your artifact was in at the time of submission + - Virtual machines will last longer than Docker files and allow researchers to more accurately reproduce your exact execution environment (though the tradeoff is that they will be larger) + +### Dataset Submissions + +- All datasets should be clearly documented in a way that would allow researchers working on similar problems to re-use the dataset for their work. +- If the dataset includes survey results, please provide a copy of the original survey. This is vital for replication studies and helping researchers interpret the context of your results. +- If the dataset is very large (> 10 MB) please state so in the README or documentation. +- It's encouraged to accompany the data with processing scripts that produce any graphs or statistical output that appear in the paper. diff --git a/_conferences/pets2021/index.md b/_conferences/pets2021/index.md new file mode 100644 index 0000000..9123c54 --- /dev/null +++ b/_conferences/pets2021/index.md @@ -0,0 +1,28 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +PoPETs reviews and publishes digital artifacts related to its accepted papers. +This process aids in the reproducibility of results and allows others to build +on the work described in the paper. Artifact submissions are requested from +authors of all accepted papers, and although they are optional, we strongly +encourage you to submit your artifacts for review. + +Possible artifacts include (but are not limited to): + +- Source code (e.g., system implementations, proof of concepts) +- Datasets (e.g., network traces, raw study data) +- Scripts for data processing or simulations +- Machine-generated proofs +- Formal specifications +- Build environments (e.g., VMs, Docker containers, configuration scripts) + +Artifacts are evaluated by the artifact review committee. The committee +evaluates the artifacts to ensure that they provide an acceptable level of +utility, and feedback is given to the authors. Issues considered include +software bugs, readability of documentation, and appropriate licensing. After +your artifact has been approved by the committee, we will accompany the paper +link on [petsymposium.org](https://petsymposium.org/) with a link to the +artifact along with an artifact badge so that interested readers can find and +use your hard work. \ No newline at end of file diff --git a/_conferences/pets2021/organizers.md b/_conferences/pets2021/organizers.md new file mode 100644 index 0000000..2476ecc --- /dev/null +++ b/_conferences/pets2021/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 20 +redirect_to: https://petsymposium.org/cfp21.php +--- \ No newline at end of file diff --git a/_conferences/pets2021/results.md b/_conferences/pets2021/results.md new file mode 100644 index 0000000..b719282 --- /dev/null +++ b/_conferences/pets2021/results.md @@ -0,0 +1,136 @@ +--- +title: Results +order: 30 +artifacts: + + - paper_url: "https://petsymposium.org/2021/files/papers/issue1/popets-2021-0008.pdf" + title: "Scaling up Differentially Private Deep Learning with Fast Per-Example Gradient Clipping" + artifact_url: "https://github.com/ppmlguy/fastgradclip" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0063.pdf" + title: "Private Stream Aggregation with Labels in the Standard Model" + artifact_url: "https://github.com/johanernst/khPRF-PSA" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0019.pdf" + title: "Automated Extraction and Presentation of Data Practices in Privacy Policies" + artifact_url: "https://github.com/um-rtcl/piextract_dataset" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0069.pdf" + title: "Privacy Preference Signals: Past, Present and Future" + artifact_url: "https://github.com/mhils/pets2021-privacy-preference-signals/" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue3/popets-2021-0040.pdf" + title: "Growing synthetic data through differentially-private vine copulas" + artifact_url: "https://github.com/alxxrg/copula-shirley" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue1/popets-2021-0011.pdf" + title: "Falcon: Honest-Majority Maliciously Secure Framework for Private Deep Learning" + artifact_url: "https://github.com/snwagh/falcon-public" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0015.pdf" + title: "Privacy-Preserving Multiple Tensor Factorization for Synthesizing Large-Scale Location Traces with Cluster-Specific Features" + artifact_url: "https://github.com/PPMTF/PPMTF" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0032.pdf" + title: "Face-Off: Adversarial Face Obfuscation" + artifact_url: "https://github.com/wi-pi/face-off" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0068.pdf" + title: "SoK: Efficient Privacy-preserving Clustering" + artifact_url: "https://github.com/encryptogroup/SoK_ppClustering" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0018.pdf" + title: "EL PASSO: Efficient and Lightweight Privacy-preserving Single Sign On" + artifact_url: "https://github.com/Zhiyi-Zhang/PS-Signature-and-EL-PASSO" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0076.pdf" + title: "Residue-Free Computing" + artifact_url: "https://larkema.github.io/residuefree/" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0027.pdf" + title: "A calculus of tracking: theory and practice" + artifact_url: "https://github.com/giorgioditizio/calculus_of_tracking" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0033.pdf" + title: "Déjà vu: Abusing Browser Cache Headers to Identify and Track Online Users" + artifact_url: "https://github.com/mishravikas/PETS_dejavu" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue3/popets-2021-0056.pdf" + title: "ML-CB: Machine Learning Canvas Block" + artifact_url: "https://osf.io/shbe7/" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue3/popets-2021-0048.pdf" + title: "Fast Privacy-Preserving Punch Cards" + artifact_url: "https://github.com/SabaEskandarian/PunchCard" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue3/popets-2021-0039.pdf" + title: "Unlinkable Updatable Hiding Databases and Privacy-Preserving Loyalty Programs" + artifact_url: "https://gitlab.uni.lu/APSIA/uuhd-ppls" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0024.pdf" + title: "Privacy-Preserving & Incrementally-Deployable Support for Certificate Transparency in Tor" + artifact_url: "https://github.com/rgdd/ctor/tree/master/artifact" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0066.pdf" + title: "LogPicker: Strengthening Certificate Transparency against covert adversaries" + artifact_url: "https://github.com/logpicker/prototype" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0070.pdf" + title: "SwapCT: Swap Confidential Transactions for Privacy-Preserving Multi-Token Exchanges" + artifact_url: "https://github.com/SwapCT/SwapCT" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0061.pdf" + title: "HashWires: Hyperefficient Credential-Based Range Proofs" + artifact_url: "https://github.com/novifinancial/hashwires" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue3/popets-2021-0045.pdf" + title: "Who Can Find My Devices? Security and Privacy of Apple's Crowd-Sourced Bluetooth Location Tracking System" + artifact_url: "https://github.com/seemoo-lab/openhaystack" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0017.pdf" + title: "Website Fingerprinting in the Age of QUIC" + artifact_url: "https://github.com/jpcsmith/wf-in-the-age-of-quic" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue2/popets-2021-0029.pdf" + title: "GANDaLF: GAN for Data-Limited Fingerprinting" + artifact_url: "https://github.com/traffic-analysis/gandalf" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0078.pdf" + title: "Domain name encryption is not enough: privacy leakage via IP-based website fingerprinting" + artifact_url: "https://homepage.np-tokumei.net/publication/publication_2021_popets" + + - paper_url: "https://petsymposium.org/2021/files/papers/issue4/popets-2021-0071.pdf" + title: "Multiparty Homomorphic Encryption from Ring-Learning-With-Errors" + artifact_url: "https://github.com/ldsec/lattigo-pets21" + + +--- + +Results obtained from PETS 2021 proceedings. + + + + + + + + + + {% for artifact in page.artifacts %} + + + + + {% endfor %} + +
TitleArtifact URL
+ {% if artifact.paper_url %} + {{artifact.title}} + {% else %} + {{ artifact.title }} + {% endif %} + + {% if artifact.artifact_url %} + artifact + {% endif %} +
diff --git a/_conferences/pets2022/aec-call.md b/_conferences/pets2022/aec-call.md new file mode 100644 index 0000000..4c13f6c --- /dev/null +++ b/_conferences/pets2022/aec-call.md @@ -0,0 +1,77 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Guidelines + + +- All submitted artifacts should be relevant to their corresponding PoPETs + paper. Please provide a copy of your paper or a brief description of how the + artifact is relevant to it in your submission. +- Many papers have several artifacts (e.g., multiple source code repositories, + datasets, build environments), which is great! Please keep in mind that we'll + need a single link to put on the PETS website and that all artifacts + associated with your paper should be discoverable from that link. +- All submitted artifacts should be submitted by providing a link to where the + artifacts are publicly hosted. +- Please include a README with your submission that briefly explains the type + and purpose of the artifact (e.g., whether it's a proof of concept + implementation, scripts for generating graphs, or datasets for reproducing + results). +- All artifacts must be immediately available to the public and **should not** + be behind any kind of paywall or restricted access. If the artifact requires + you as an author to manually approve requests for access, it is not public and + will not qualify as a PoPETs artifact submission. If you have concerns or + questions about this please contact us directly. + +### Source Code Submissions + +- All source code should be accompanied by a README or other documentation that + describes how to build and/or run the code. Reviewers will provide feedback on + the clarity of the instructions and attempt to follow them and build and/or + run the code. +- Any source code submissions should be accompanied with a build environment + such as a virtual machine (recommended) or a Docker container that has been + configured with all the dependencies and prerequisites necessary to build the + code. +- If you use a virtual machine, please state how many resources it will consume + and any configuration steps that are required. Your virtual machine should not + usually have to download additional dependencies when you run your install + scripts. If that is the case, reassess your build process and consider making + changes to limit the amount of network resources needed. +- If the code is in a compiled language, the code should compile in the provided + build environment by performing the provided instructions. +- If the code is interpreted, please provide some simple inputs so that the + reviewers can verify that the code runs without error. We want to make sure + that the code will execute without error, not that the outputs are necessarily + correct. +- Compilation and setup should be automated as much as possible. Ideally, there + will be one script that builds your software and runs your tests. +- Please ensure your code has an open source license and clearly states this + information. The following resources may help you to choose a license: + - For a clear, easy to follow guide see: [https://choosealicense.com/](https://choosealicense.com/) + - For more in-depth detail on open source and copy-left licenses, see + [https://www.gnu.org/licenses/license-list.en.html](https://www.gnu.org/licenses/license-list.en.html) and + [https://opensource.org/licenses](https://opensource.org/licenses) +- Our goal with these artifacts is for them to be useful as far into the future + as possible. Some tips on improving the longevity of your source code artifact + are: + - Include the versions of your software's dependencies wherever possible + - Mention specific hashes of git commits that match the state your artifact + was in at the time of submission + - Virtual machines will last longer than Docker files and allow researchers to + more accurately reproduce your exact execution environment (though the + tradeoff is that they will be larger) + +### Dataset Submissions + +- All datasets should be clearly documented in a way that would allow + researchers working on similar problems to re-use the dataset for their work. +- If the dataset includes survey results, please provide a copy of the original + survey. This is vital for replication studies and helping researchers + interpret the context of your results. +- If the dataset is very large (> 10 MB) please state so in the README or + documentation. +- It's encouraged to accompany the data with processing scripts that produce any + graphs or statistical output that appear in the paper. diff --git a/_conferences/pets2022/artifact-award.md b/_conferences/pets2022/artifact-award.md new file mode 100644 index 0000000..ab14b6f --- /dev/null +++ b/_conferences/pets2022/artifact-award.md @@ -0,0 +1,5 @@ +--- +title: Artifact Award +order: 20 +redirect_to: https://petsymposium.org/artifact-award.php +--- \ No newline at end of file diff --git a/_conferences/pets2022/index.md b/_conferences/pets2022/index.md new file mode 100644 index 0000000..008213a --- /dev/null +++ b/_conferences/pets2022/index.md @@ -0,0 +1,24 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +PoPETs reviews and publishes digital artifacts related to its accepted papers. This process aids in the reproducibility of results and allows others to build on the work described in the paper. Artifact submissions are requested from authors of all accepted papers, and although they are optional, we strongly encourage you to submit your artifacts for review. + +Possible artifacts include (but are not limited to): + +- Source code (e.g., system implementations, proof of concepts) +- Datasets (e.g., network traces, raw study data) +- Scripts for data processing or simulations +- Machine-generated proofs +- Formal specifications +- Build environments (e.g., VMs, Docker containers, configuration scripts) + +Artifacts are evaluated by the artifact review committee. The committee +evaluates the artifacts to ensure that they provide an acceptable level of +utility, and feedback is given to the authors. Issues considered include +software bugs, readability of documentation, and appropriate licensing. After +your artifact has been approved by the committee, we will accompany the paper +link on [petsymposium.org](https://petsymposium.org/) with a link to the +artifact along with an artifact badge so that interested readers can find and +use your hard work. \ No newline at end of file diff --git a/_conferences/pets2022/organizers.md b/_conferences/pets2022/organizers.md new file mode 100644 index 0000000..d06ea07 --- /dev/null +++ b/_conferences/pets2022/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 20 +redirect_to: https://petsymposium.org/cfp22.php +--- \ No newline at end of file diff --git a/_conferences/pets2022/results.md b/_conferences/pets2022/results.md new file mode 100644 index 0000000..ff182cb --- /dev/null +++ b/_conferences/pets2022/results.md @@ -0,0 +1,228 @@ +--- +title: Results +order: 30 +artifacts: + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0126.pdf" + title: "On the Challenges of Developing a Concise Questionnaire to Identify Privacy Personas" + artifact_url: "https://tudatalib.ulb.tu-darmstadt.de/handle/tudatalib/3490" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0081.pdf" + title: "Mixnet optimization methods" + artifact_url: "https://github.com/ibenguir/mixim_pets" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0087.pdf" + title: "OrgAn: Organizational Anonymity with Low Latency" + artifact_url: "https://github.com/zhtluo/organ" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0083.pdf" + title: "Leveraging Strategic Connection Migration-Powered Traffic Splitting for Privacy" + artifact_url: "https://github.com/inspire-group/comps" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0018.pdf" + title: "Circuit-PSI with Linear Complexity via Relaxed Batch OPPRF" + artifact_url: "https://aka.ms/2PC-Circuit-PSI" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0119.pdf" + title: "Keeping Privacy Labels Honest" + artifact_url: "https://github.com/Keeping-Privacy-Labels-Honest/Main" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0086.pdf" + title: "User-friendly yet rarely read: A case study on the redesign of an online HIPAA authorization" + artifact_url: "https://github.com/chatbot-study/chatbot" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0094.pdf" + title: "Privacy-Preserving and Efficient Verification of the Outcome in Genome-Wide Association Studies" + artifact_url: "https://github.com/SpidLab/GWAS-Verification" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0020.pdf" + title: "Polymath: Low-Latency MPC via Secure Polynomial Evaluations and its Applications" + artifact_url: "https://github.com/lu562/Polymath_artifact" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0012.pdf" + title: "OmniCrawl: Comprehensive Measurement of Web Tracking With Real Desktop and Mobile Browsers" + artifact_url: "https://github.com/OmniCrawl/OmniCrawl" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0130.pdf" + title: "Replay (Far) Away: Exploiting and Fixing Google/Apple Exposure Notification Contact Tracing" + artifact_url: "https://github.com/OSUSecLab/GAENPlus" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0132.pdf" + title: "Privately Connecting Mobility to Infectious Diseases via Applied Cryptography" + artifact_url: "https://github.com/IAIK/CoronaHeatMap" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0103.pdf" + title: "On the Feasibility of Linking Attack to Google/Apple Exposure Notification Framework" + artifact_url: "https://github.com/nomokazu/linking-attack-poc" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0077.pdf" + title: "Are You Really Muted?: A Privacy Analysis of Mute Buttons in Video Conferencing Apps" + artifact_url: "https://github.com/wi-pi/VCAMuteButton_PoPETS" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0070.pdf" + title: "Privacy accounting εconomics: Improving differential privacy composition via a posteriori bounds" + artifact_url: "https://doi.org/10.6084/m9.figshare.19330649" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0017.pdf" + title: "Differentially private partition selection" + artifact_url: "https://github.com/google/differential-privacy/blob/main/common_docs/partition_selection.md" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue2/popets-2022-0052.pdf" + title: "d3p - A Python Package for Differentially-Private Probabilistic Programming" + artifact_url: "https://github.com/DPBayes/d3p" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0110.pdf" + title: "ATOM: Ad-network Tomography" + artifact_url: "https://vitalstatistix.cs.uiowa.edu:2443/maaz/atom-archive" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0030.pdf" + title: "Setting the Bar Low: Are Websites Complying With the Minimum Requirements of the CCPA?" + artifact_url: "https://cbw.sh/static/archives/ccpa_2022_pets.tar.gz" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0060.pdf" + title: "A Multi-Region Investigation of Use and Perceptions of Smart Home Devices" + artifact_url: "https://github.com/sameer-patil/shd-popets" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0109.pdf" + title: "LLAMA: A Low Latency Math Library for Secure Inference" + artifact_url: "https://github.com/mpc-msri/EzPC/tree/master/FSS" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0123.pdf" + title: "Hidden Issuer Anonymous Credential" + artifact_url: "https://gitlab.inria.fr/mgestin/hiac_docker_implementation.git" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0028.pdf" + title: "DataProVe: Fully Automated Conformance Verification Between Data Protection Policies and System Architectures" + artifact_url: "https://github.com/Dataprove/Dataprovetool/" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0066.pdf" + title: "Integrating Privacy into the Electric Vehicle Charging Architecture" + artifact_url: "https://code.fbi.h-da.de/seacop/daa-pnc-tamarin" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0112.pdf" + title: "Machine Learning with Differentially Private Labels: Mechanisms and Frameworks" + artifact_url: "https://github.com/inspire-group/LabelDP" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0025.pdf" + title: "Masking Feedforward Neural Networks against Power Analysis Attacks" + artifact_url: "https://gitlab.com/athanasiou.k/masked-nn-lib" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0102.pdf" + title: "A Global Survey of Android Dual-Use Applications Used in Intimate Partner Surveillance" + artifact_url: "https://github.com/majed-almansoori/IPS-dual-use-android-apps" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue2/popets-2022-0033.pdf" + title: "Are iPhones Really Better for Privacy? A Comparative Study of iOS and Android Apps" + artifact_url: "https://www.platformcontrol.org/" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue2/popets-2022-0057.pdf" + title: "Analyzing the Feasibility and Generalizability of Fingerprinting Internet of Things Devices" + artifact_url: "https://github.com/dilawer11/iot-device-fingerprinting" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0121.pdf" + title: "Formalizing and Estimating Distribution Inference Risks" + artifact_url: "https://github.com/iamgroot42/FormEstDistRisks" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0023.pdf" + title: "Disparate Vulnerability to Membership Inference Attacks" + artifact_url: "https://github.com/spring-epfl/disparate-vulnerability" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0072.pdf" + title: "Athena: Probabilistic Verification of Machine Unlearning" + artifact_url: "https://github.com/inspire-group/unlearning-verification" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0079.pdf" + title: "Deletion Inference, Reconstruction, and Compliance in Machine (Un)Learning" + artifact_url: "https://github.com/gaoji7777/DeleteLeakage" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0085.pdf" + title: "On Defeating Graph Analysis of Anonymous Transactions" + artifact_url: "https://gitlab.com/siccegge/research-notebooks/-/tree/master/ELRWY22" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0088.pdf" + title: "FingerprinTV: Fingerprinting Smart TV Apps" + artifact_url: "https://github.com/UCI-Networking-Group/fingerprintv" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0092.pdf" + title: "Watch Over Your TV: A Security and Privacy Analysis of the Android TV ecosystem" + artifact_url: "https://gitlab.com/s3lab-rhul/watch-over-your-tv-paper" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue2/popets-2022-0034.pdf" + title: "Building a Privacy-Preserving Smart Camera System" + artifact_url: "https://github.com/siis/CaCTUs" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0107.pdf" + title: "gOTzilla: Efficient Disjunctive Zero-Knowledge Proofs from MPC in the Head, with Application to Proofs of Assets in Cryptocurrencies" + artifact_url: "https://github.com/GMU-Crypto/gOTzilla" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0120.pdf" + title: "Zswap: zk-SNARK Based Non-Interactive Multi-Asset Swaps" + artifact_url: "https://anonymous.4open.science/r/zswap-E332/" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0021.pdf" + title: "Privacy-preserving FairSwap: Fairness and Privacy Interplay" + artifact_url: "https://github.com/Prezzy/pFairSwap" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0069.pdf" + title: "I know what you did on Venmo: Discovering privacy leaks in mobile social payments" + artifact_url: "https://github.com/STEELISI/SENMO" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0005.pdf" + title: "MLEFlow: Learning from History to Improve Load Balancing in Tor" + artifact_url: "https://github.com/hdarir2/mleflow" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0026.pdf" + title: "From \"Onion Not Found\" to Guard Discovery" + artifact_url: "https://github.com/numbleroot/from-onion-not-found-to-guard-discovery" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue2/popets-2022-0040.pdf" + title: "Increasing Adoption of Tor Browser Using Informational and Planning Nudges" + artifact_url: "https://osf.io/wyrhc/" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue3/popets-2022-0074.pdf" + title: "Trace Oddity: Methodologies for Data-Driven Traffic Analysis on Tor" + artifact_url: "https://github.com/DistriNet/DLTC" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue1/popets-2022-0022.pdf" + title: "If You Like Me, Please Don’t \"Like\" Me: Inferring Vendor Bitcoin Addresses From Positive Reviews" + artifact_url: "https://www.wim.uni-mannheim.de/ths/research/data" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue4/popets-2022-0114.pdf" + title: "Flexible and scalable privacy assessment for very large datasets, with an application to official governmental microdata" + artifact_url: "https://github.com/nunesgh/bvm-library" + + - paper_url: "https://petsymposium.org/2022/files/papers/issue2/popets-2022-0058.pdf" + title: "Visualizing Privacy-Utility Trade-Offs in Differentially Private Data Releases" + artifact_url: "https://github.com/priyakalot/ViP-demo" + + +--- + +Results obtained from PETS 2022 proceedings. + + + + + + + + + + {% for artifact in page.artifacts %} + + + + + {% endfor %} + +
TitleArtifact URL
+ {% if artifact.paper_url %} + {{artifact.title}} + {% else %} + {{ artifact.title }} + {% endif %} + + {% if artifact.artifact_url %} + artifact + {% endif %} +
diff --git a/_conferences/pets2023/aec-call.md b/_conferences/pets2023/aec-call.md new file mode 100644 index 0000000..4c13f6c --- /dev/null +++ b/_conferences/pets2023/aec-call.md @@ -0,0 +1,77 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Guidelines + + +- All submitted artifacts should be relevant to their corresponding PoPETs + paper. Please provide a copy of your paper or a brief description of how the + artifact is relevant to it in your submission. +- Many papers have several artifacts (e.g., multiple source code repositories, + datasets, build environments), which is great! Please keep in mind that we'll + need a single link to put on the PETS website and that all artifacts + associated with your paper should be discoverable from that link. +- All submitted artifacts should be submitted by providing a link to where the + artifacts are publicly hosted. +- Please include a README with your submission that briefly explains the type + and purpose of the artifact (e.g., whether it's a proof of concept + implementation, scripts for generating graphs, or datasets for reproducing + results). +- All artifacts must be immediately available to the public and **should not** + be behind any kind of paywall or restricted access. If the artifact requires + you as an author to manually approve requests for access, it is not public and + will not qualify as a PoPETs artifact submission. If you have concerns or + questions about this please contact us directly. + +### Source Code Submissions + +- All source code should be accompanied by a README or other documentation that + describes how to build and/or run the code. Reviewers will provide feedback on + the clarity of the instructions and attempt to follow them and build and/or + run the code. +- Any source code submissions should be accompanied with a build environment + such as a virtual machine (recommended) or a Docker container that has been + configured with all the dependencies and prerequisites necessary to build the + code. +- If you use a virtual machine, please state how many resources it will consume + and any configuration steps that are required. Your virtual machine should not + usually have to download additional dependencies when you run your install + scripts. If that is the case, reassess your build process and consider making + changes to limit the amount of network resources needed. +- If the code is in a compiled language, the code should compile in the provided + build environment by performing the provided instructions. +- If the code is interpreted, please provide some simple inputs so that the + reviewers can verify that the code runs without error. We want to make sure + that the code will execute without error, not that the outputs are necessarily + correct. +- Compilation and setup should be automated as much as possible. Ideally, there + will be one script that builds your software and runs your tests. +- Please ensure your code has an open source license and clearly states this + information. The following resources may help you to choose a license: + - For a clear, easy to follow guide see: [https://choosealicense.com/](https://choosealicense.com/) + - For more in-depth detail on open source and copy-left licenses, see + [https://www.gnu.org/licenses/license-list.en.html](https://www.gnu.org/licenses/license-list.en.html) and + [https://opensource.org/licenses](https://opensource.org/licenses) +- Our goal with these artifacts is for them to be useful as far into the future + as possible. Some tips on improving the longevity of your source code artifact + are: + - Include the versions of your software's dependencies wherever possible + - Mention specific hashes of git commits that match the state your artifact + was in at the time of submission + - Virtual machines will last longer than Docker files and allow researchers to + more accurately reproduce your exact execution environment (though the + tradeoff is that they will be larger) + +### Dataset Submissions + +- All datasets should be clearly documented in a way that would allow + researchers working on similar problems to re-use the dataset for their work. +- If the dataset includes survey results, please provide a copy of the original + survey. This is vital for replication studies and helping researchers + interpret the context of your results. +- If the dataset is very large (> 10 MB) please state so in the README or + documentation. +- It's encouraged to accompany the data with processing scripts that produce any + graphs or statistical output that appear in the paper. diff --git a/_conferences/pets2023/artifact-award.md b/_conferences/pets2023/artifact-award.md new file mode 100644 index 0000000..ab14b6f --- /dev/null +++ b/_conferences/pets2023/artifact-award.md @@ -0,0 +1,5 @@ +--- +title: Artifact Award +order: 20 +redirect_to: https://petsymposium.org/artifact-award.php +--- \ No newline at end of file diff --git a/_conferences/pets2023/index.md b/_conferences/pets2023/index.md new file mode 100644 index 0000000..9123c54 --- /dev/null +++ b/_conferences/pets2023/index.md @@ -0,0 +1,28 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +PoPETs reviews and publishes digital artifacts related to its accepted papers. +This process aids in the reproducibility of results and allows others to build +on the work described in the paper. Artifact submissions are requested from +authors of all accepted papers, and although they are optional, we strongly +encourage you to submit your artifacts for review. + +Possible artifacts include (but are not limited to): + +- Source code (e.g., system implementations, proof of concepts) +- Datasets (e.g., network traces, raw study data) +- Scripts for data processing or simulations +- Machine-generated proofs +- Formal specifications +- Build environments (e.g., VMs, Docker containers, configuration scripts) + +Artifacts are evaluated by the artifact review committee. The committee +evaluates the artifacts to ensure that they provide an acceptable level of +utility, and feedback is given to the authors. Issues considered include +software bugs, readability of documentation, and appropriate licensing. After +your artifact has been approved by the committee, we will accompany the paper +link on [petsymposium.org](https://petsymposium.org/) with a link to the +artifact along with an artifact badge so that interested readers can find and +use your hard work. \ No newline at end of file diff --git a/_conferences/pets2023/organizers.md b/_conferences/pets2023/organizers.md new file mode 100644 index 0000000..5eddf1e --- /dev/null +++ b/_conferences/pets2023/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 20 +redirect_to: https://petsymposium.org/cfp23.php +--- \ No newline at end of file diff --git a/_conferences/pets2023/results.md b/_conferences/pets2023/results.md new file mode 100644 index 0000000..f6661be --- /dev/null +++ b/_conferences/pets2023/results.md @@ -0,0 +1,283 @@ +--- +title: Results +order: 30 +artifacts: + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0047.pdf" + title: "DeepSE-WF: Unified Security Estimation for Website Fingerprinting Defenses" + artifact_url: "https://github.com/veichta/DeepSE-WF" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0057.pdf" + title: "RPM: Robust Anonymity at Scale" + artifact_url: "https://github.com/lu562/MP-SPDZ" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0048.pdf" + title: "iPET: Privacy Enhancing Traffic Perturbations for Secure IoT Communications" + artifact_url: "https://github.com/akshayeshenoi/ipet" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0077.pdf" + title: "RAVEN: Stateless Rapid IP Address Variation for Enterprise Networks" + artifact_url: "https://github.com/liangw89/RAVEN/tree/main" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0099.pdf" + title: "Evaluating practical QUIC website fingerprinting defenses for the masses" + artifact_url: "https://github.com/spring-epfl/quic-wf-defenses" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0125.pdf" + title: "Data-Explainable Website Fingerprinting with Network Simulation" + artifact_url: "https://explainwf-popets2023.github.io/" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0005.pdf" + title: "On the Privacy Risks of Deploying Recurrent Neural Networks in Machine Learning Models" + artifact_url: "https://github.com/yunhaoyang234/Membership-Attack-Privacy-Preserving" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0124.pdf" + title: "Differentially Private Simple Genetic Algorithms" + artifact_url: "https://gitlab.uwaterloo.ca/t3humphr/dp-simple-ga" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0070.pdf" + title: "Towards Sentence Level Inference Attack Against Pre-trained Language Models" + artifact_url: "https://github.com/KangGu96/Adv_decoder" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0044.pdf" + title: "Heads in the Clouds? Measuring Universities’ Migration to Public Clouds: Implications for Privacy & Academic Freedom" + artifact_url: "https://git.aperture-labs.org/Cloudheads/cloudheadschecker" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0035.pdf" + title: "Multi-Party Replicated Secret Sharing over a Ring with Applications to Privacy-Preserving Machine Learning" + artifact_url: "https://github.com/anbaccar/RSS_ring_ppml" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0091.pdf" + title: "Private Collection Matching Protocols" + artifact_url: "https://github.com/spring-epfl/private-collection-matching" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0090.pdf" + title: "Secure and Accurate Summation of Many Floating-Point Numbers" + artifact_url: "https://github.com/chennyc/floating_point_summation.git" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0085.pdf" + title: "VESPo: Verified Evaluation of Secret Polynomials, with application to dynamic proofs of retrievability" + artifact_url: "https://github.com/jgdumas/vespo" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0054.pdf" + title: "Strengthening Privacy-Preserving Record Linkage using Diffusion" + artifact_url: "https://github.com/youzheheng/2022_PoPETS" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0082.pdf" + title: "SoK: Membership Inference is Harder Than we Previously Thought" + artifact_url: "https://bitbucket.org/srecgrp/sok-membership-inference-public/" + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0108.pdf" + title: "Exploring the Privacy Risks of Adversarial VR Game Design" + artifact_url: "https://github.com/metaguard/metadata" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0093.pdf" + title: "Practical Delegatable Anonymous Credentials From Equivalence Class Signatures" + artifact_url: "https://github.com/mobilesec/DAC-from-EQS" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0097.pdf" + title: "Attribute-based Single Sign-On. Secure, Private, and Efficient" + artifact_url: "https://github.com/aicis/fresco-outsourcing/tree/macro-bench" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0011.pdf" + title: "Understanding Person Identification Through Gait" + artifact_url: "https://git.scc.kit.edu/ps-chair/understanding-person-identification-through-gait-popets-2023" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0010.pdf" + title: "Individualized PATE: Differentially Private Machine Learning with Individual Privacy Guarantees" + artifact_url: "https://github.com/secret-pets-submitter/individualized-pate-pets-submission-" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0088.pdf" + title: "Data Security on the Ground: Investigating Technical and Legal Requirements under the GDPR" + artifact_url: "https://github.com/tau200/gdpr_master" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0121.pdf" + title: "GDPRxiv: Establishing the State of the Art in GDPR Enforcement" + artifact_url: "https://github.com/lawfulcomputing/GDPRxiv/" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0029.pdf" + title: "Lox: Protecting the Social Graph in Bridge Distribution" + artifact_url: "https://git-crysp.uwaterloo.ca/iang/lox" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0081.pdf" + title: "Examining the Hydra: Simultaneously Shared Links in Tor and the Effects on its Performance" + artifact_url: "https://gitlab.com/spahl/hydra-popets2023" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0014.pdf" + title: "Designing a Location Trace Anonymization Contest" + artifact_url: "https://github.com/PPMTFPlus/PPMTFPlus" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0095.pdf" + title: "Robust Fingerprint of Privacy-Preserving Location Trajectories" + artifact_url: "https://github.com/spid-lab/Robust-Fingerprint-of-Location-Trajectories-Under-Differential-Privacy" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0032.pdf" + title: "Privacy-Aware Adversarial Network in Human Mobility Prediction" + artifact_url: "https://github.com/YutingZhan/Mo-PAE" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0049.pdf" + title: " Creative beyond TikToks: Investigating Adolescents’ Social Privacy Management on TikTok" + artifact_url: "https://osf.io/z8d3w/" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0120.pdf" + title: "On the Role and Form of Personal Information Disclosure in Cyberbullying Incidents" + artifact_url: "https://osf.io/9xtpc/" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0058.pdf" + title: " Private Sampling with Identifiable Cheaters" + artifact_url: "https://gitlab.inria.fr/cesabate/privatesampling-exp" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0084.pdf" + title: " Convolutions in Overdrive: Maliciously Secure Convolutions for MPC" + artifact_url: "https://github.com/sec-stuttgart/MP-SPDZ-convolution-triples" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0068.pdf" + title: "Ruffle: Rapid 3-Party Shuffle Protocols" + artifact_url: "https://osf.io/z8d3w/" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0126.pdf" + title: "Verifiable Distributed Aggregation Functions" + artifact_url: "https://github.com/cloudflareresearch/doplar/tree/cjpatton/PoPETS-2023.4-Artifact" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0069.pdf" + title: "Story Beyond the Eye: Glyph Positions Break PDF Text Redaction" + artifact_url: "https://github.com/maxwell-bland/deredaction" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0103.pdf" + title: "Disparate Vulnerability in Link Inference Attacks against Graph Neural Networks" + artifact_url: "https://github.com/dzhong2/DSV_Graph.git" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0101.pdf" + title: "Locality-Sensitive Hashing Does Not Guarantee Privacy! Attacks on Google's FLoC and the MinHash Hierarchy System" + artifact_url: "https://github.com/fturati/floc-minhash-attacks" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0016.pdf" + title: " StyleID: Identity Disentanglement for Anonymizing Faces" + artifact_url: "https://github.com/minha12/StyleID" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0062.pdf" + title: "Two-Cloud Private Read Alignment to a Public Reference Genome" + artifact_url: "https://github.com/sindhujamohan9/TwoCloudShuffledBWT" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0116.pdf" + title: "Compact and Divisible E-Cash with Threshold Issuance" + artifact_url: "https://github.com/aniampio/TI-OfflineEcash" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0020.pdf" + title: "HeLayers: A Tile Tensors Framework for Large Neural Networks on Encrypted Data" + artifact_url: "https://ibm.github.io/helayers/" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0041.pdf" + title: "Private Graph Extraction via Feature Explanations" + artifact_url: "https://github.com/iyempissy/graph-stealing-attacks-with-explanation" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0052.pdf" + title: "Usability and Enforceability of Global Privacy Control" + artifact_url: "https://github.com/privacy-tech-lab/gpc-optmeowt" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0087.pdf" + title: "Blocking JavaScript without Breaking the Web: An Empirical Investigation" + artifact_url: "https://github.com/hadiamjad/Blocking-JavaScript-without-Breaking-the-Web" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0098.pdf" + title: "On the Robustness of Topics API to a Re-Identification Attack" + artifact_url: "https://github.com/nikhiljha95/topics-api-simulator" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0112.pdf" + title: "Your DRM Can Watch You Too: Exploring the Privacy Implications of Browsers (mis)Implementations of Widevine EME" + artifact_url: "https://anonymous.4open.science/r/widevine_eme_fingerprinting-880C" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0008.pdf" + title: "TWo-IN-one-SSE: Fast, Scalable and Storage-Efficient Searchable Symmetric Encryption for Conjunctive and Disjunctive Boolean Queries" + artifact_url: "https://github.com/SEAL-IIT-KGP/TWINSSE" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue4/popets-2023-0106.pdf" + title: "Attacks on Encrypted Response-Hiding Range Search Schemes in Multiple Dimensions" + artifact_url: "https://github.com/cloudsecuritygroup/ers-attacks" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0022.pdf" + title: "FrodoPIR: Simple, Scalable, Single-Server Private Information Retrieval" + artifact_url: "https://github.com/brave-experiments/frodo-pir" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0086.pdf" + title: "DPrio: Efficient Differential Privacy with High Utility for Prio" + artifact_url: "https://github.com/DPrio-PoPETs/dprio" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue2/popets-2023-0055.pdf" + title: "A Unified Framework for Quantifying Privacy Risk in Synthetic Data" + artifact_url: "https://github.com/statice/anonymeter" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue3/popets-2023-0075.pdf" + title: "SoK: New Insights into Fully Homomorphic Encryption Libraries via Standardized Benchmarks" + artifact_url: "https://github.com/TrustworthyComputing/T2-FHE-Compiler-and-Benchmarks" + + + - paper_url: "https://petsymposium.org/2023/files/papers/issue1/popets-2023-0004.pdf" + title: "\"Revoked just now!\"Users' Behaviors Toward Fitness-Data Sharing with Third-Party Applications" + artifact_url: "https://osf.io/z6fw9/?view_only=dc5e1b32561e48248a97865b0f4dcf16" + +--- + +Results obtained from PETS 2023 proceedings. + + + + + + + + + + {% for artifact in page.artifacts %} + + + + + {% endfor %} + +
TitleArtifact URL
+ {% if artifact.paper_url %} + {{artifact.title}} + {% else %} + {{ artifact.title }} + {% endif %} + + {% if artifact.artifact_url %} + artifact + {% endif %} +
diff --git a/_conferences/pets2024/aec-call.md b/_conferences/pets2024/aec-call.md new file mode 100644 index 0000000..96a13a6 --- /dev/null +++ b/_conferences/pets2024/aec-call.md @@ -0,0 +1,129 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Guidelines + +- All submitted artifacts should be relevant to their corresponding PoPETs + paper. Please provide a copy of your paper or a brief description of how the + artifact is relevant to it in your submission. +- Many papers have several artifacts (e.g., multiple source code repositories, + datasets, build environments), which is great! Please keep in mind that we'll + need a single link to put on the PETS website and that all artifacts + associated with your paper should be discoverable from that link. +- All submitted artifacts should be submitted by providing a link to where the + artifacts are publicly hosted. Valid hosting options are institutional and + third-party digital repositories. Please do not use personal web pages. The + link should be persistent; for repositories that evolve over time (e.g., Git + repositories), please specify a specific commit-id or tag to be evaluated. +- Please include a README with your submission that briefly explains the type + and purpose of the artifact (e.g., whether it's a proof of concept + implementation, scripts for generating graphs, or datasets for reproducing + results). +- All artifacts must be immediately available to the public and should not be + behind any kind of paywall or restricted access. If the artifact requires you + as an author to manually approve requests for access, it is not public and + will not qualify as a PoPETs artifact submission. If you have concerns or + questions about this please contact us directly. + +### Source Code Submissions + +- All source code should be accompanied by a README or other documentation that + describes how to build and/or run the code. Reviewers will provide feedback on + the clarity of the instructions and attempt to follow them and build and/or + run the code. +- Any source code submissions should be accompanied with a build environment + such as a virtual machine (recommended) or a Docker container that has been + configured with all the dependencies and prerequisites necessary to build the + code. +- If you use a virtual machine, please state how many resources it will consume + and any configuration steps that are required. Your virtual machine should not + usually have to download additional dependencies when you run your install + scripts. If that is the case, reassess your build process and consider making + changes to limit the amount of network resources needed. +- If the code is in a compiled language, the code should compile in the provided + build environment by performing the provided instructions. +- If the code is interpreted, please provide some simple inputs so that the + reviewers can verify that the code runs without error. We want to make sure + that the code will execute without error, not that the outputs are necessarily + correct. +- Compilation and setup should be automated as much as possible. Ideally, there + will be one script that builds your software and runs your tests. +- Please ensure your code has an open source license and clearly states this + information. The following resources may help you to choose a license: + - For a clear, easy to follow guide see: + [https://choosealicense.com/](https://choosealicense.com/) + - For more in-depth detail on open source and copy-left licenses, see +- [https://www.gnu.org/licenses/license-list.en.html](https://www.gnu.org/licenses/license-list.en.html) + and +- [https://opensource.org/licenses](https://opensource.org/licenses) +- Our goal with these artifacts is for them to be useful as far into the future + as possible. Some tips on improving the longevity of your source code artifact + are: + - Include the versions of your software's dependencies wherever possible + - Mention specific hashes of git commits that match the state your artifact +- was in at the time of submission + - Virtual machines will last longer than Docker files and allow researchers to +- more accurately reproduce your exact execution environment (though the +- tradeoff is that they will be larger) +- Artifacts are not required to be able to run on all hardwares and OSes. If + your artifact requires any particular hardware / OS, please make it clear in + the submission. + +### Dataset Submissions + +- All datasets should be clearly documented in a way that would allow + researchers working on similar problems to re-use the dataset for their work. +- If the dataset includes survey results, please provide a copy of the original + survey. This is vital for replication studies and helping researchers + interpret the context of your results. +- If the dataset is very large (> 10 MB) please state so in the README or + documentation. +- It's encouraged to accompany the data with processing scripts that produce any + graphs or statistical output that appear in the paper. + +## Artifact Badges + +See [badges](/pets2024/badges). + +## What we expect from the authors of artifact submissions + +To ensure a smooth submission process, please follow these important guidelines. +Firstly, authors should fill out the [template.md](/pets2024/template.md) file +provided and include it in their artifacts. This will help the reviewer better +understand your work and ensure a seamless review process. Secondly, prompt +communication is essential. Authors are kindly reque sted to respond to reviews +and comments within a time span of two weeks. This will facilitate constructive +discussions and allow for timely feedback incorporation. Lastly, in the event +that changes are requested during the review process, we kindly ask authors to +endeavor to incorporate them, at least partially, within two weeks after the +request. Your cooperation in adhering to these guidelines will greatly +contribute to the efficiency and effectiveness of our submission and review +process. We eagerly anticipate receiving your high-quality contributions and +look forward to showcasing your research! + + +### What Makes a Good Review + +The goal of artifact review is to help ensure the artifacts are as useful as +possible. Towards this goal, the review should check for the following points. + +- Is the artifact publicly available at a permanent location? +- Documentations: + - Is the relationship between the artifact and the paper clear? + - If applicable, is the requirement for running the artifact clear? + - If applicable, are the instructions to run the artifact sufficient? + - If applicable, are the required dataset & packages publicly available? +- Reproducibility: In case that the authors choose "artifact reproduced" badge + option, the reviewers should also check that the experiments run and the + results displayed are similar to the ones in the paper. + +Artifact review process is interactive and we expect the authors to take into +account the reviewers' comments and modify their artifacts accordingly. As such, +the reviews should contain sufficient details for the authors to make the +appropriate changes; for example, if the code fails, then the review should +include the environment that it is run on and the error messages. After the +authors have fixed the issues, they will add a comment on the submission site, +at which point the reviewers can either approve the artifact or provide +additional comments for another round of revision. \ No newline at end of file diff --git a/_conferences/pets2024/artifact-award.md b/_conferences/pets2024/artifact-award.md new file mode 100644 index 0000000..8d71fd8 --- /dev/null +++ b/_conferences/pets2024/artifact-award.md @@ -0,0 +1,5 @@ +--- +title: Artifact Award +order: 30 +redirect_to: https://petsymposium.org/artifact-award.php +--- \ No newline at end of file diff --git a/_conferences/pets2024/badges.md b/_conferences/pets2024/badges.md new file mode 100644 index 0000000..fcb5567 --- /dev/null +++ b/_conferences/pets2024/badges.md @@ -0,0 +1,44 @@ +--- +title: Badges +order: 20 +--- + + + +For PETS 2024, each accepted artifact will be granted one of the following two +badges. During the submission, the authors must select which badge they want +their artifacts to be evaluated against. + +## Artifacts Available Artifact: Available + +This "Available" badge indicates that the artifacts are publicly available at a +permanent location with clear documentation on how it relates to the +corresponding paper and, if applicable, how to execute the artifact/evaluation +without execution error. This badge does *not* mean that the reviewers have +reproduced the results. Authors whose artifacts require extremely specialized +hardware or software are encouraged to choose this option. Similarly, authors +whose artifacts are "not reproducible" (e.g., outcomes of surveys) should also +select this option. + +## Artifacts Reproduced Artifact: Reproduced + +The "Reproduced" badge indicates everything the "Available" badge does and, in +addition, that the submitted artifacts reproduce the main findings of the paper. +Note that this does not necessarily cover all experiments/data presented in the +paper. To submit artifacts for this badge, the authors must specify the commands +to run the artifacts clearly and describe how to reproduce each main finding of +the paper. Also, they must highlight which results of the paper are not +reproducible with the given artifacts. The artifact's quality, structure, and +documentation must allow the reviewers to check whether the artifact works as +claimed in the paper. Even if the authors choose this option, the review +committee may request to grant only an "available" badge if the reviewers cannot +reproduce the results (e.g., lack of computational resources). \ No newline at end of file diff --git a/_conferences/pets2024/index.md b/_conferences/pets2024/index.md new file mode 100644 index 0000000..cb3f0cb --- /dev/null +++ b/_conferences/pets2024/index.md @@ -0,0 +1,28 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +PoPETs reviews and publishes digital artifacts related to its accepted papers. +This process aids in the reproducibility of results and allows others to build +on the work described in the paper. Artifact submissions are requested from +authors of all accepted papers, and although they are optional, we strongly +encourage you to submit your artifacts for review. + +Possible artifacts include (but are not limited to): + +- Source code (e.g., system implementations, proof of concepts) +- Datasets (e.g., network traces, raw study data) +- Scripts for data processing or simulations +- Machine-generated proofs +- Formal specifications +- Build environments (e.g., VMs, Docker containers, configuration scripts) + +Artifacts are evaluated by the artifact review committee. The committee +evaluates the artifacts to ensure that they provide an acceptable level of +utility, and feedback is given to the authors. Issues considered include +software bugs, readability of documentation, and appropriate licensing. After +your artifact has been approved by the committee, we will accompany the paper +link on [petsymposium.org](https://petsymposium.org) with a link to the artifact +along with an artifact badge so that interested readers can find and use your +hard work. \ No newline at end of file diff --git a/_conferences/pets2024/organizers.md b/_conferences/pets2024/organizers.md new file mode 100644 index 0000000..2cd85c5 --- /dev/null +++ b/_conferences/pets2024/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 30 +redirect_to: https://petsymposium.org/cfp24.php +--- \ No newline at end of file diff --git a/_conferences/pets2024/results.md b/_conferences/pets2024/results.md new file mode 100644 index 0000000..288e461 --- /dev/null +++ b/_conferences/pets2024/results.md @@ -0,0 +1,390 @@ +--- +title: Results +order: 40 +artifacts: + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0102.pdf" + title: "I still know it's you! On Challenges in Anonymizing Source Code" + artifact_url: "https://github.com/horlabs/anonymizer/tree/b20a4c96228260d130ddaa5bacb7b3c07048f99c" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0034.pdf" + title: "User-Controlled Privacy: Taint, Track, and Control" + artifact_url: "https://gitlab.ethz.ch/fhublet/ttc/tree/988c7ccf8a1da6d0b6b0e8f7de0b051551b31a3a" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0024.pdf" + title: "Data Isotopes for Data Provenance in DNNs" + artifact_url: "https://github.com/uchicago-sandlab/dataisotopes/tree/41680e8b1b0906fdef113a7f860ff70820c2df4e" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0089.pdf" + title: "PrivDNN: A Secure Multi-Party Computation Framework for Deep Learning using Partial DNN Encryption" + artifact_url: "https://github.com/LiangqinRen/PrivDNN/tree/a60ffc334f34a7541387329b701ae6922e64fc2e" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0014.pdf" + title: "Why Privacy-Preserving Protocols Are Sometimes Not Enough: A Case Study of the Brisbane Toll Collection Infrastructure" + artifact_url: "https://github.com/amiradavoudi/Tracing/tree/4b0b0577348145e77f9784df22b2c3411c826b2c" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0070.pdf" + title: "Attacking Connection Tracking Frameworks as used by Virtual Private Networks" + artifact_url: "https://github.com/bmixonba/network-alchemy-dev/tree/791986d9c09d2a0101eb73215a3d591fa05bc65c" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0101.pdf" + title: "What Does It Mean to Be Creepy? Responses to Visualizations of Personal Browsing Activity, Online Tracking, and Targeted Ads" + artifact_url: "https://github.com/UChicagoSUPERgroup/TrackingTransparencyPETS2024/tree/c4a153b597e7bf3697a11cf8c8d67ba4a6f4a88e" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0049.pdf" + title: "Traceable mixnets" + artifact_url: "https://github.com/agrawalprash/traceable-mixnets/releases/tag/v1" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0050.pdf" + title: "MixMatch: Flow Matching for Mixnet Traffic" + artifact_url: "https://github.com/mixnet-correlation/mixmatch-flow-matching-for-mixnet-traffic_popets-2024-2/tree/5159d2c21ad3e480955f3800ecbf4d2bd9cbe5d2" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0035.pdf" + title: "SGXonerated: Finding (and Partially Fixing) Privacy Flaws in TEE-based Smart Contract Platforms Without Breaking the TEE" + artifact_url: "https://github.com/initc3/SecretNetwork-Sandbox/" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0002.pdf" + title: "A Large-Scale Study of Cookie Banner Interaction Tools and their Impact on Users' Privacy" + artifact_url: "https://github.com/internet-sicherheit/A-Large-Scale-Study-of-Cookie-Banner-Interaction-Tools-and-Their-Impact-on-Users-Privacy/tree/97f1c9fc7e3970b154711b8f34e9579963465cd4" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0011.pdf" + title: "Supporting Informed Choices about Browser Cookies: The Impact of Personalised Cookie Banners" + artifact_url: "https://tudatalib.ulb.tu-darmstadt.de/handle/tudatalib/3927" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0012.pdf" + title: "Block Cookies, Not Websites: Analysing Mental Models and Usability of the Privacy-Preserving Browser Extension CookieBlock" + artifact_url: "https://dx.doi.org/20.50s0.11850/627400" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0015.pdf" + title: "Generalizable Active Privacy Choice: Designing a Graphical User Interface for Global Privacy Control" + artifact_url: "https://github.com/privacy-tech-lab/gpc-privacy-choice/releases/tag/v2.10.3" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0031.pdf" + title: "A Cautionary Tale: On the Role of Reference Data in Empirical Privacy Defenses" + artifact_url: "https://github.com/ckaplan100/PETS-2024/tree/aeb90296060292147cbdbea2889aa5ee3c86aa7a" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0131.pdf" + title: "Computational Differential Privacy for Encrypted Databases Supporting Linear Queries" + artifact_url: "https://github.com/FerranAlborch/RIPFEDP/tree/e74ba9efda74a4f7810902bc31482d33c724d323" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0090.pdf" + title: "Connecting the Dots: Tracing Data Endpoints in IoT Devices" + artifact_url: "https://github.com/jakariamd/IoT-Measurement/tree/45b59d4b27e2d422d6e404c80d31f607ca466fe6" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0026.pdf" + title: "SocIoTy: Practical Cryptography in Smart Home Contexts" + artifact_url: "https://github.com/tusharjois/socioty/tree/artifact_review" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0020.pdf" + title: "CoStricTor: Collaborative HTTP Strict Transport Security in Tor Browser" + artifact_url: "https://github.com/KillianDavitt/CoStricTor/tree/af48fadca30a24af5eba7a434029b62a11d35070" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0007.pdf" + title: "DeTorrent: An Adversarial Padding-only Traffic Analysis Defense" + artifact_url: "https://github.com/jkhollandjr/PETS_DeTorrent/tree/c08ad14c1e14539f22cf657dbb170524452e1283" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0081.pdf" + title: "GenAIPABench: A Benchmark for Generative AI-based Privacy Assistants" + artifact_url: "https://github.com/DAMSlabUMBC/GenAIPABench/tree/0a5fffcb00b92ba5a604e6b1b5127b1199e52919" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0084.pdf" + title: "Edge Private Graph Neural Networks with Singular Value Perturbation" + artifact_url: "https://github.com/TinaTangTingting/Eclipse/tree/e0a397133ae91a02f5b14169f0e0056dbcfbe6a9" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0075.pdf" + title: "TMI! Finetuned Models Leak Private Information from their Pretraining Data" + artifact_url: "https://github.com/johnmath/tmi-pets24/tree/4117d649adf496d68faded93f950f357d7e1e851" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0017.pdf" + title: "Privacy Preserving Feature Selection for Sparse Linear Regression" + artifact_url: "https://github.com/IBM/helayers-examples/tree/244408348746441a48cce0b698dd8078b71722d9" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0018.pdf" + title: "Model-driven Privacy" + artifact_url: "https://polybox.ethz.ch/index.php/s/RoJSS2ECAMww1br" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0054.pdf" + title: "Defining and Controlling Information Leakage in US Equities Trading" + artifact_url: "https://github.com/arthuramerico/toilc/tree/af1652de1f03a4c75a6316c1886420bf0f0e9f3f" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0111.pdf" + title: "Honesty is the Best Policy: On the Accuracy of Apple Privacy Labels Compared to Apps' Privacy Policies" + artifact_url: "https://github.com/masood/2024-pets-privacy-labels-policies/tree/61c31b3ee4caea4c74cc8f823370db8e485ad059" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0005.pdf" + title: "QUICKeR: Quicker Updates Involving Continuous Key Rotation" + artifact_url: "https://github.com/lawrencekhlim/QUICKeR/tree/QUICKeR-PoPETS-paper" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0069.pdf" + title: "Anonify: Decentralized Dual-level Anonymity for Medical Data Donation" + artifact_url: "https://github.com/lng-ng/anonify/tree/d0c87d0a9a0b5c926f403840e9697f3976345755" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0145.pdf" + title: "Privacy Protection Behaviors from a New Angle: Exploratory Analysis on a Russian Sample" + artifact_url: "https://osf.io/wnad8/" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0006.pdf" + title: "Efficiently Compiling Secure Computation Protocols From Passive to Active Security: Beyond Arithmetic Circuits" + artifact_url: "https://github.com/applied-crypto-lab/mal-ext-circuits/tree/4d1bbd232d717ff5e83bcaf191139f8861420aad" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0038.pdf" + title: "Multipars: Reduced-Communication MPC over Z2k" + artifact_url: "https://github.com/haslersn/multipars/tree/3d373038f28541f520db027724955f8d1fe49ec6" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0100.pdf" + title: "PRAC: Round-Efficient 3-Party MPC for Dynamic Data Structures" + artifact_url: "https://git-crysp.uwaterloo.ca/iang/prac/src/popets-repro" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0033.pdf" + title: "PRIVIC: A privacy-preserving method for incremental collection of location data" + artifact_url: "https://github.com/blitzwas/PRIVIC/tree/21a460cfbf102e9a3361daf16eae5502775b847f" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0087.pdf" + title: "Snail: Secure Single Iteration Localization" + artifact_url: "https://github.com/secret-snail/localization-server/tree/ab30546afa7c22c56f053ae620a084a0829476d3" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0068.pdf" + title: "SoK: Can Trajectory Generation Combine Privacy and Utility?" + artifact_url: "https://github.com/erik-buchholz/SoK-TrajGen/releases/tag/v2.0.0" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0120.pdf" + title: "Johnny Still Can't Opt-out: Assessing the IAB CCPA Compliance Framework" + artifact_url: "https://github.com/abubakaraziz/Assessing-IAB-CCPA-Framework/tree/835672bc86754febfa4534b151af35e70cdb7805" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0147.pdf" + title: "Evaluating Google's Protected Audience Protocol" + artifact_url: "https://github.com/Elena6918/PrAu-Simulation/tree/2cfd2bd03101967aa681f218efdce6cf5696dad6" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0076.pdf" + title: "CheckOut: User-Controlled Anonymization for Customer Loyalty Programs" + artifact_url: "https://github.com/MatthewGregoire42/LoyaltyPointsCrypto/tree/1a6cb047c60b78c60b15d206c3c183ed3eb6c9f2" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0107.pdf" + title: "SIGMA: Secure GPT Inference with Function Secret Sharing" + artifact_url: "https://github.com/neha-jawalkar/EzPC/tree/8f434400d3fbe6620ce4fae0507286e3c5928e8b" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0064.pdf" + title: "PLASMA: Private, Lightweight Aggregated Statistics against Malicious Adversaries" + artifact_url: "https://github.com/TrustworthyComputing/plasma/tree/c3ca8fac17ed6f41d737ece96bee43a5051f5b6b" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0023.pdf" + title: "Constant-Round Private Decision Tree Evaluation for Secret Shared Data" + artifact_url: "https://github.com/nann-cheng/PDTE/tree/b854a10438f696b047476a8d4787bf5a867fbbf4" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0021.pdf" + title: "DeVoS: Deniable Yet Verifiable Vote Updating" + artifact_url: "https://gitlab.uni.lu/APSIA/DeVoS/-/tree/f0320f8b39c3c0de4ebaa18ef7266d5d110aeb17" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0040.pdf" + title: "Delegated Private Matching For Compute" + artifact_url: "https://github.com/facebookresearch/Private-ID/tree/58af4eff6e2add0e46c88fb844bdab702954555f" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0004.pdf" + title: "Interest-disclosing Mechanisms for Advertising are Privacy-Exposing (not Preserving)" + artifact_url: "https://github.com/yohhaan/topics_analysis/releases/tag/petsymposium-artifact2024.1" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0092.pdf" + title: "FP-tracer: Fine-grained Browser Fingerprinting Detection via Taint-tracking and Multi-level Entropy-based Thresholds" + artifact_url: "https://github.com/soumboussaha/FP-tracer/tree/bbdede91500b0265e8cd3dd9cc0555efda3e62e7" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0128.pdf" + title: "Post-quantum XML and SAML Single Sign-On" + artifact_url: "https://github.com/PQSAML/index/tree/3b49d759fe3021b6ee6fc322999e483df427f8bd" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0028.pdf" + title: "On the Quality of Privacy Policy Documents of Virtual Personal Assistant Applications" + artifact_url: "https://github.com/UQ-Trust-Lab/Quper/tree/66bcac724f7083d28c29c87d529f66c3a81306b5" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0085.pdf" + title: "Investigating the Effect of Misalignment on Membership Privacy in the White-box Setting" + artifact_url: "https://github.com/microsoft/shadow-realignment-mia/tree/v2.0" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0078.pdf" + title: "Anonymous Complaint Aggregation for Secure Messaging" + artifact_url: "https://github.com/connorbelll/anonymous-tally/tree/15e71ddaf5e7c59c9d85022dc1d3dd344c0a216a" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0099.pdf" + title: "A Black-Box Privacy Analysis of Messaging Service Providers' Chat Message Processing" + artifact_url: "https://github.com/honeymessages" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0056.pdf" + title: "NOTRY: Deniable messaging with retroactive avowal" + artifact_url: "https://github.com/xxsqwe/notry/tree/8647801cebb3184e150d5b1c6a5fb1c0dbc7f4c7" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0105.pdf" + title: "Fantômas: Understanding Face Anonymization Reversibility" + artifact_url: "https://github.com/kit-ps/seba/tree/b5fe27c5b518ce69ee65ade5e14fc10521441c8" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0048.pdf" + title: "Website Data Transparency in the Browser" + artifact_url: "https://github.com/privacy-tech-lab/privacy-pioneer/releases/tag/v1.2.1" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0112.pdf" + title: "Raising the Bar: Improved Fingerprinting Attacks and Defenses for Video Streaming Traffic" + artifact_url: "https://github.com/trafnex/raising-the-bar/tree/7fd66eafd24fcadf7f6bd390e32d74a483f58e64" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0043.pdf" + title: "StyleAdv: A Usable Privacy Framework Against Facial Recognition with Adversarial Image Editing" + artifact_url: "https://github.com/minha12/StyleAdv/tree/fd42cb6121dccdade747ab37c085c218aee7bd5d" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0025.pdf" + title: "MAPLE: MArkov Process Leakage attacks on Encrypted Search" + artifact_url: "https://github.com/anonymous-repo-submission/artifact/tree/a2d5187b4d6e5fc75133aa0b0a7378c175ae3bde" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0095.pdf" + title: "PLAN: Variance-Aware Private Mean Estimation" + artifact_url: "https://github.com/ChristianLebeda/PLAN-experiments/tree/94470ac71ec6d45537edf3168c95dbf29c2ebd93" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0032.pdf" + title: "SWiSSSE: System-Wide Security for Searchable Symmetric Encryption" + artifact_url: "https://github.com/SWiSSSE-crypto/SWiSSSE/tree/c2c4d04b7fceacb34b1ab774a7c26cbdc866f6a1" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0123.pdf" + title: "Sloth: Key Stretching and Deniable Encryption using Secure Elements on Smartphones" + artifact_url: "https://github.com/lambdapioneer/sloth/tree/0bf22c5178808e75d1e3f2c01e090869b8c19f83" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0144.pdf" + title: "https://petsymposium.org/popets/2024/popets-2024-0123.pdf" + artifact_url: "https://github.com/YuanXun2024/VFLGAN/tree/5e9d319e4ba6a514b3416c10ed8b99565d679329" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0113.pdf" + title: "Decision-based Data Distribution (D³): Enabling Users to Minimize Data Propagation in Privacy-sensitive Scenarios" + artifact_url: "https://tudatalib.ulb.tu-darmstadt.de/handle/tudatalib/4236" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0119.pdf" + title: "Efficient Privacy-Preserving Machine Learning with Lightweight Trusted Hardware" + artifact_url: "https://github.com/HuangPZ/STAMP/tree/b7f9eab2b5d98da9883315075dd2a8066618a876" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0137.pdf" + title: "AUTOLYCUS: Exploiting Explainable Artificial Intelligence (XAI) for Model Extraction Attacks against Interpretable Models" + artifact_url: "https://github.com/acoksuz/AUTOLYCUS/tree/402bd2e407a82b49ffa7a0aebd2921563b0c101b" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0061.pdf" + title: "Differentially Private Functional Encryption" + artifact_url: "https://github.com/JasZal/differentially_private_functional_encryption/tree/725607f7f67f59deeaab5ec5c2a793ffbceefddf" + badge: "artifact-reproduced" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0060.pdf" + title: "Internet Users' Willingness to Disclose Biometric Data for Continuous Online Account Protection: An Empirical Investigation" + artifact_url: "https://github.com/das-group/CAuthN-Study-Dataset/tree/e1429b98c6053293ae86a2cf19c940572ae8f785" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0114.pdf" + title: "Summation-based Private Segmented Membership Test from Threshold-Fully Homomorphic Encryption" + artifact_url: "https://github.com/tjungND/caoe-cerberus-query/tree/654783f5629a28c9b3e9469fbc164fa3bbc862ab" + badge: "artifact-available" + + - paper_url: "https://petsymposium.org/popets/2024/popets-2024-0110.pdf" + title: "Revealing the True Cost of Locally Differentially Private Protocols: An Auditing Perspective" + artifact_url: "https://github.com/hharcolezi/ldp-audit/tree/5cd1c5d47c089c6ae55292e7ccb75b2677893c9a" + badge: "artifact-reproduced" +--- + + + +Results obtained from PETS 2024 proceedings. + + + + + + + + + + {% for artifact in page.artifacts %} + + + + + {% endfor %} + +
TitleArtifact URL
+ {% if artifact.paper_url %} + {{artifact.title}} + {% else %} + {{ artifact.title }} + {% endif %} + + {% if artifact.artifact_url %} + {% if artifact.badge contains "artifact-available" %} + Artifact: Available + {% endif %} + {% if artifact.badge contains "artifact-reproduced" %} + Artifact: Reproduced + {% endif %} + {% endif %} +
diff --git a/_conferences/pets2024/template.md b/_conferences/pets2024/template.md new file mode 100644 index 0000000..706c66c --- /dev/null +++ b/_conferences/pets2024/template.md @@ -0,0 +1,113 @@ +# Artifact Appendix + +Paper title: **Enter the title of your paper here** + +Artifacts HotCRP Id: **#Enter your HotCRP Id here** + +Requested Badge: Either **Available** or **Reproducible** + +## Description +A short description of your artifact and how it links to your paper. + +### Security/Privacy Issues and Ethical Concerns +If your artifacts hold any risk to the security or privacy of the reviewer's machine, specify them here, e.g., if your artifacts require a specific security mechanism, like the firewall, ASLR, or another thing, to be disabled for its execution. +Also, emphasize if your artifacts contain malware samples, or something similar, to be analyzed. +In addition, you must highlight any ethical concerns regarding your artifacts here. + +## Basic Requirements +Describe the minimal hardware and software requirements of your artifacts and estimate the compute time and storage required to run the artifacts. + +### Hardware Requirements +If your artifacts require specific hardware to be executed, mention that here. +Provide instructions on how a reviewer can gain access to that hardware through remote access, buying or renting, or even emulating the hardware. +Make sure to preserve the anonymity of the reviewer at any time. + +### Software Requirements +Describe the OS and software packages required to evaluate your artifact. +This description is essential if you rely on proprietary software or software that might not be easily accessible for other reasons. +Describe how the reviewer can obtain and install all third-party software, data sets, and models. + +### Estimated Time and Storage Consumption +Provide an estimated value for the time the evaluation will take and the space on the disk it will consume. +This helps reviewers to schedule the evaluation in their time plan and to see if everything is running as intended. +More specifically, a reviewer, who knows that the evaluation might take 10 hours, does not expect an error if, after 1 hour, the computer is still calculating things. + +## Environment +In the following, describe how to access our artifact and all related and necessary data and software components. +Afterward, describe how to set up everything and how to verify that everything is set up correctly. + +### Accessibility +Describe how to access your artifacts via persistent sources. +Valid hosting options are institutional and third-party digital repositories. +Do not use personal web pages. +For repositories that evolve over time (e.g., Git Repositories ), specify a specific commit-id or tag to be evaluated. +In case your repository changes during the evaluation to address the reviewer's feedback, please provide an updated link (or commit-id / tag) in a comment. + + +### Set up the environment +Describe how the reviews should set up the environment for your artifacts, including download and install dependencies and the installation of the artifact itself. +Be as specific as possible here. +If possible, use code segments to simply the workflow, e.g., + +```bash +git clone git@my_awesome_artifact.com/repo +apt install libxxx xxx +``` + +Describe the expected results where it makes sense to do so. + + + +### Testing the Environment +Describe the basic functionality tests to check if the environment is set up correctly. +These tests could be unit tests, training an ML model on very low training data, etc. +If these tests succeed, all required software should be functioning correctly. +Include the expected output for unambiguous outputs of tests. +Use code segments to simplify the workflow, e.g., +```bash +python envtest.py +``` + +## Artifact Evaluation +This section includes all the steps required to evaluate your artifact's functionality and validate your paper's key results and claims. +Therefore, highlight your paper's main results and claims in the first subsection. And describe the experiments that support your claims in the subsection after that. + +### Main Results and Claims +List all your paper's main results and claims that are supported by your submitted artifacts. + +#### Main Result 1: Name +Describe the results in 1 to 3 sentences. +Refer to the related sections in your paper and reference the experiments that support this result/claim. + +#### Main Result 2: Name +... + +### Experiments +List each experiment the reviewer has to execute. Describe: + - How to execute it in detailed steps. + - What the expected result is. + - How long it takes and how much space it consumes on disk. (approximately) + - Which claim and results does it support, and how. + +#### Experiment 1: Name +Provide a short explanation of the experiment and expected results. +Describe thoroughly the steps to perform the experiment and to collect and organize the results as expected from your paper. +Use code segments to support the reviewers, e.g., +```bash +python experiment_1.py +``` +#### Experiment 2: Name +... + +#### Experiment 3: Name +... + +## Limitations +Describe which tables and results are not reproducible with the provided artifacts. +Provide an argument why this is not included/possible. + +## Notes on Reusability +First, this section might not apply to your artifacts. +Use it to share information on how your artifact can be used beyond your research paper, e.g., as a general framework. +The overall goal of artifact evaluation is not only to reproduce and verify your research but also to help other researchers to re-use and improve on your artifacts. +Please describe how your artifacts can be adapted to other settings, e.g., more input dimensions, other datasets, and other behavior, through replacing individual modules and functionality or running more iterations of a specific part. \ No newline at end of file diff --git a/_conferences/pets2025/ARTIFACT-EVALUATION.md b/_conferences/pets2025/ARTIFACT-EVALUATION.md new file mode 100644 index 0000000..38844f2 --- /dev/null +++ b/_conferences/pets2025/ARTIFACT-EVALUATION.md @@ -0,0 +1,109 @@ +# Artifact Appendix + +Paper title: **Enter the title of your paper here** + +Artifacts HotCRP Id: **#Enter your HotCRP Id here** (not your paper Id, but the artifacts id) + +Requested Badge: Either **Available**, **Functional**, or **Reproduced** + +## Description +A short description of your artifact and how it links to your paper. + +### Security/Privacy Issues and Ethical Concerns (All badges) +If your artifact holds any risk to the security or privacy of the reviewer's machine, specify them here, e.g., if your artifact requires a specific security mechanism, like the firewall, ASLR, or another thing, to be disabled for its execution. +Also, emphasize if your artifact contains malware samples, or something similar, to be analyzed. +In addition, you should highlight any ethical concerns regarding your artifacts here. + +## Basic Requirements (Only for Functional and Reproduced badges) +Describe the minimal hardware and software requirements of your artifact and estimate the compute time and storage required to run the artifact. + +### Hardware Requirements +If your artifact requires specific hardware to be executed, mention that here. +Provide instructions on how a reviewer can gain access to that hardware through remote access, buying or renting, or even emulating the hardware. +Make sure to preserve the anonymity of the reviewer at any time. + +### Software Requirements +Describe the OS and software packages required to evaluate your artifact. +This description is essential if you rely on proprietary software or software that might not be easily accessible for other reasons. +Describe how the reviewer can obtain and install all third-party software, data sets, and models. + +### Estimated Time and Storage Consumption +Provide an estimated value for the time the evaluation will take and the space on the disk it will consume. +This helps reviewers to schedule the evaluation in their time plan and to see if everything is running as intended. +More specifically, a reviewer, who knows that the evaluation might take 10 hours, does not expect an error if, after 1 hour, the computer is still calculating things. + +## Environment +In the following, describe how to access our artifact and all related and necessary data and software components. +Afterward, describe how to set up everything and how to verify that everything is set up correctly. + +### Accessibility (All badges) +Describe how to access your artifact via persistent sources. +Valid hosting options are institutional and third-party digital repositories. +Do not use personal web pages. +For repositories that evolve over time (e.g., Git Repositories ), specify a specific commit-id or tag to be evaluated. +In case your repository changes during the evaluation to address the reviewer's feedback, please provide an updated link (or commit-id / tag) in a comment. + +### Set up the environment (Only for Functional and Reproduced badges) +Describe how the reviewers should set up the environment for your artifact, including downloading and installing dependencies and the installation of the artifact itself. +Be as specific as possible here. +If possible, use code segments to simply the workflow, e.g., + +```bash +git clone git@my_awesome_artifact.com/repo +apt install libxxx xxx +``` +Describe the expected results where it makes sense to do so. + +### Testing the Environment (Only for Functional and Reproduced badges) +Describe the basic functionality tests to check if the environment is set up correctly. +These tests could be unit tests, training an ML model on very low training data, etc.. +If these tests succeed, all required software should be functioning correctly. +Include the expected output for unambiguous outputs of tests. +Use code segments to simplify the workflow, e.g., +```bash +python envtest.py +``` + +## Artifact Evaluation (Only for Functional and Reproduced badges) +This section includes all the steps required to evaluate your artifact's functionality and validate your paper's key results and claims. +Therefore, highlight your paper's main results and claims in the first subsection. And describe the experiments that support your claims in the subsection after that. + +### Main Results and Claims +List all your paper's results and claims that are supported by your submitted artifacts. + +#### Main Result 1: Name +Describe the results in 1 to 3 sentences. +Refer to the related sections in your paper and reference the experiments that support this result/claim. + +#### Main Result 2: Name +... + +### Experiments +List each experiment the reviewer has to execute. Describe: + - How to execute it in detailed steps. + - What the expected result is. + - How long it takes and how much space it consumes on disk. (approximately) + - Which claim and results does it support, and how. + +#### Experiment 1: Name +Provide a short explanation of the experiment and expected results. +Describe thoroughly the steps to perform the experiment and to collect and organize the results as expected from your paper. +Use code segments to support the reviewers, e.g., +```bash +python experiment_1.py +``` +#### Experiment 2: Name +... + +#### Experiment 3: Name +... + +## Limitations (Only for Functional and Reproduced badges) +Describe which tables and results are included or are not reproducible with the provided artifact. +Provide an argument why this is not included/possible. + +## Notes on Reusability (Only for Functional and Reproduced badges) +First, this section might not apply to your artifacts. +Use it to share information on how your artifact can be used beyond your research paper, e.g., as a general framework. +The overall goal of artifact evaluation is not only to reproduce and verify your research but also to help other researchers to re-use and improve on your artifacts. +Please describe how your artifacts can be adapted to other settings, e.g., more input dimensions, other datasets, and other behavior, through replacing individual modules and functionality or running more iterations of a specific part. diff --git a/_conferences/pets2025/aec-call.md b/_conferences/pets2025/aec-call.md new file mode 100644 index 0000000..9010941 --- /dev/null +++ b/_conferences/pets2025/aec-call.md @@ -0,0 +1,116 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Guidelines + +- All submitted artifacts should be relevant to their corresponding PoPETs + paper. +- Please upload a copy of your paper. +- Many papers have several artifacts (e.g., multiple source code repositories, + datasets, build environments), which is great! Please keep in mind that we'll + need a single link to put on the PETS website and that all artifacts + associated with your paper should be discoverable from that one link. +- Please include a README.md file with your submission that briefly explains the + type and purpose of the artifact. At a prominent position in the README.md + file make clear to which paper the artifact belongs and how the artifact is + relevant to the paper. +- Please include the [ARTIFACT-EVALUATION.md](/pets2025/ARTIFACT-EVALUATION.md) file in + your artifact (either include it in the README.md file or add it as a separate + file.). It is important for the reviewers during the reviewing process. + Provide a direct link to that file at the submission page. + +### Source Code Submissions + +- All source code should be accompanied by a README.md or other documentation + that describes how to build and/or run the code. Reviewers will provide + feedback on the clarity of the instructions and attempt to follow them and + build and/or run the code. +- Any source code submissions should be accompanied with a build environment + such as a virtual machine or a Docker container that has been configured with + all the dependencies and prerequisites necessary to build the code. If you use + a virtual machine, please state how many resources it will consume and any + configuration steps that are required. Your virtual machine should not usually + have to download additional dependencies when you run your install scripts. If + that is the case, reassess your build process and consider making changes to + limit the amount of network resources needed. You can also use one of the VM + images provided by us, which you can spawn from within HotCRP. In this case + please provide the name of the used image. Please keep in mind that our VMs + are only available to the reviewers and you, to ease the process, and they are + not available to the public. Your artifact, however, should also be runnable + and helpful for the general public. Hence, your descriptions and scripts + should be as generic as possible. If your artifact runs on compute providers, + like AWS or similar, state the amount of money/coins required to run the + experiments and provide account credentials with enough coins. Our reviewers + won't invest their money or credit cards to setup accounts. If this cannot be + provided, provide an alternative way of running your artifact. If this is not + possible, reconsider your choices of badges (see below). +- If the code is in a compiled language, the code should compile in the provided + build environment by performing the provided instructions. +- Compilation and setup should be automated as much as possible. Ideally, there + will be one script that builds your software, runs your tests, and produces + the results in a comprehensible way. +- Please ensure that your code has a license and clearly states this + information. The following resources may help you to choose a license: + - For a clear, easy to follow guide see: [https://choosealicense.com/](https://choosealicense.com/). + - For more in-depth detail on open source and copy-left licenses, see + [https://www.gnu.org/licenses/license-list.en.html](https://www.gnu.org/licenses/license-list.en.html) and + [https://opensource.org/licenses](https://opensource.org/licenses). +- Our goal is that the artifacts are useful for as long as possible. Some tips + on improving the longevity of your source code artifact are: + - Include the versions of your software's dependencies wherever possible. + - Mention specific hashes of git commits that match the state your artifact + was in at the time of submission. + - Virtual machines and Docker images will last longer than Docker files and + allow researchers to more accurately reproduce your exact execution + environment (though the trade off is that they will be larger). + - Artifacts are not required to be able to run on all hardwares and OSes. If + your artifact requires any particular hardware/OS, please make it clear in + the submission. + +### Dataset Submissions + +- All datasets should be clearly documented in a way that allows researchers + working on similar problems to re-use the dataset for their work. +- If the dataset includes survey results, please provide a copy of the original + survey with raw results. This is vital for replication studies and helping + researchers interpret the context of your results. +- Please state the sizes of datasets in the documentation. +- It's encouraged to accompany the data with processing scripts that produce the + graphs or statistical output that appear in the paper. + +## Artifact Badges + +See [badges](/pets2025/badges). + +## What Makes a Good Submission + +To ensure a smooth submission process, please follow the following important +guidelines. Firstly, authors should fill out the +[ARTIFACT-EVALUATION.md](/pets2025/ARTIFACT-EVALUATION.md) file provided and +include it in their artifact (either in the README.md file or as a separate +file). Mention the badges you deem reasonable for your artifact and, if +necessary, describe which stages are simplified or skipped and why. This will +help the reviewer better understand your work and ensure a seamless review +process. Secondly, prompt communication is essential. Authors are kindly +requested to respond to reviews and comments within a time span of two weeks. +This will facilitate constructive discussions and allow for timely feedback +incorporation. Lastly, in the event that changes are requested during the review +process, we kindly ask authors to endeavor to incorporate them, at least +partially, within two weeks after the request. Your cooperation in adhering to +these guidelines will greatly contribute to the efficiency and effectiveness of +our submission and review process. We eagerly anticipate receiving your +high-quality contributions and look forward to showcasing your research! + +## What Makes a Good Review + +The goal of our artifact evaluation is to ensure the artifacts are as useful as +possible. Towards this goal, artifact evaluation process is interactive and we +expect the authors to take into account the reviewers' comments and modify their +artifacts accordingly. As such, the reviews should contain sufficient details +for the authors to make the appropriate changes; for example, if the code fails, +then the review should include the environment that it is run on and the error +messages. After the authors have fixed the issues, they will add a comment on +the submission site, at which point the reviewers can either approve the +artifact or provide additional comments for another rounds of revision. \ No newline at end of file diff --git a/_conferences/pets2025/artifact-award.md b/_conferences/pets2025/artifact-award.md new file mode 100644 index 0000000..8d71fd8 --- /dev/null +++ b/_conferences/pets2025/artifact-award.md @@ -0,0 +1,5 @@ +--- +title: Artifact Award +order: 30 +redirect_to: https://petsymposium.org/artifact-award.php +--- \ No newline at end of file diff --git a/_conferences/pets2025/badges.md b/_conferences/pets2025/badges.md new file mode 100644 index 0000000..2867398 --- /dev/null +++ b/_conferences/pets2025/badges.md @@ -0,0 +1,112 @@ +--- +title: Badges +order: 20 +--- + + + +Each accepted artifact can be granted up to three badges. During the submission, +the authors must select which badges they want their artifacts to be evaluated +against. We encourage the authors to choose the badges appropriately, to ease +the reviewing effort. Our understanding of the individual badges is aligned with +other conferences, e.g., [USENIX Security +Symposium](https://secartifacts.github.io/usenixsec2023/badges) + +## Artifact Available Artifact: Available + +The "Artifact Available" badge indicates that the artifact is publicly available +at a permanent location (not be behind any kind of paywall or restricted +access). If the artifact requires you as an author to manually approve requests +for access, it is not public and will not qualify for the "Artifact Available" +badge. If you have concerns or questions about this badge please contact us +directly. Valid hosting options are institutional and third-party digital +repositories. Please do not use personal web pages. The link should be +persistent; for repositories that evolve over time (e.g., Git repositories), +please specify a specific commit-id or tag to be evaluated. The reviewers check +that the artifact can be retrieved, and that it includes a license. The +reviewers check that the artifact is relevant to the paper. This badge does +*not* mean that the reviewers have reproduced the results or checked that the +code executes or that they have reproduced the results for full functionality. + +## Artifact Functional Artifact: Functional + +For the "Artifact Functional" badge the artifact should satisfy these criteria: + +- Documentation: It clearly documents how it relates to the paper, and how it + should be used. +- Completeness: It includes all the core contributions described in the paper. +- Exercisability: It includes the scripts and data needed to run the experiments + described in the paper. The software must be successfully executable? + +Some artifacts may not, by definition, be able to satisfy the completeness or +exercisability criteria. For instance, an artifact may have a proprietary +machine learning model as a key component of the system, and so, achieving +completeness may be difficult. Artifacts may rely on datasets that are too large +to be included, or contain personally identifiable information, and so, +satisfying exercisability is difficult. We guide authors below, using some +examples, on how they can still prepare their artifact to achieve this badge. +Additionally, some artifacts, such as longitudinal studies or hardware-based +contributions, may be infeasible for the Artifact Reproduced badge (see below), +as reviewers have limited time and only commodity hardware available. +Nevertheless, these authors can prepare their artifacts for the Artifact +Functional badge, as described in the examples: Examples + +Consider the experiments in your artifact as arranged in a pipeline of multiple +stages, such as data collection, data processing, and producing plots or tables +for the paper. The “Completeness” and “Exercisability” criteria require each +stage to be represented. Our key advice is to present each stage, including the +ones that cannot be fully run. These can be represented in either a simplified +manner or run on dummy data to check the functionality of the stage. If +possible, provide the expected outcome of the fully run stage such that +preceeding stages are performed on 'real' data again. In the following we +present some examples: + +- **Tools based on large machine learning (ML) models.** If an ML model is required + to execute the presented tool, the authors should provide it, unless it is + proprietary. Authors may use `git-lfs` to commit large model files to their + repository. If they can not share the model, we expect them to share a dummy + model, which may perhaps perform worse, but which can be used to test the + principle functionality of the presented tool. Ideally, authors should provide + the code to train the original model, though depending on the contributions of + the paper, it need not be executed. +- **Lengthy experiment runtimes.** Similar to the point above, even if the + experiment requires days or weeks of compute time on commodity hardware, the + "Artifact Functional" badge can be achieved. In such cases the authors should + also provide a simplified version of the experiment, which may run on less + training data or for fewer epochs of time, in order to enable the reviewers to + check the functionality of that stage. Authors should additionally provide + results of the full experiments in the repository, so that reviewers can + verify the functionality of the later stages with these results. +- **User studies, longitudinal studies and crawls.** Some studies cannot be repeated + within the reviewing process. However, the authors should provide the + evaluation scripts to reproduce the main results of the paper. Pseudonymized + raw data should also be provided, unless forbidden by legal requirements, + privacy, or ethical concerns. In such cases, a data set with dummy data should + be included. Reviewers should be able to execute the evaluation scripts on + either the pseudonymized raw data or dummy data. +- **Hardware-based contributions.** If the artifact requires certain hardware, + please request for it within the "hardware requirement" section in the + [ARTIFACT-EVALUATION.md](/pets2025/ARTIFACT-EVALUATION.md) template. If + special physical setups are required, the authors may simulate the hardware. + Authors should publish the raw results of the experiments, so that reviewers + can verify the remaining stages as functional. + +## Artifact Reproduced Artifact: Reproduced + +The "Artifact Reproduced" badge requires the core contributions of the paper to +be reproduced by the reviewers. Authors must specify the commands to run the +artifacts clearly and describe how to reproduce each core finding of the paper. +Best practice is to point out which part of the paper is reproduced by a given +script, e.g., name the table or figure. Also, the authors must highlight which +results of the paper are not reproducible with the given artifacts and argue +why. Note that minor additional experiments that do not significantly contribute +to the paper may not be included in the artifact. diff --git a/_conferences/pets2025/distinguished-artifact-reviewers.md b/_conferences/pets2025/distinguished-artifact-reviewers.md new file mode 100644 index 0000000..447ffdd --- /dev/null +++ b/_conferences/pets2025/distinguished-artifact-reviewers.md @@ -0,0 +1,5 @@ +--- +title: Distinguished Artifact Reviewers +order: 35 +redirect_to: https://petsymposium.org/reviewer-awards.php +--- diff --git a/_conferences/pets2025/index.md b/_conferences/pets2025/index.md new file mode 100644 index 0000000..c5fc523 --- /dev/null +++ b/_conferences/pets2025/index.md @@ -0,0 +1,29 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +PoPETs reviews and publishes digital artifacts related to its accepted papers. +This process aids in the reproducibility of results and allows others to build +on the work described in the papers. Artifact submissions are requested from +authors of all accepted papers, and although they are optional, we strongly +encourage you to submit your artifacts for review. + +Possible artifacts include (but are not limited to): + +- Source code (e.g., system implementations, proof of concepts) +- Datasets (e.g., network traces, raw study data) +- Scripts for data processing or simulations +- Machine-generated proofs +- Formal specifications +- Build environments (e.g., VMs, Docker containers, configuration scripts) + +Artifacts are evaluated by the artifact review committee. The committee +evaluates the artifacts to ensure that they provide an acceptable level of +utility. Issues considered include software bugs, readability of the +documentation, appropriate licensing, and the reproducibility of the results +presented in the paper. After your artifact has been approved by the committee, +we will accompany the paper link on +[petsymposium.org](https://petsymposium.org/) with a link to the artifact along +with the obtained artifact badges so that interested readers can find and use +your hard work. \ No newline at end of file diff --git a/_conferences/pets2025/organizers.md b/_conferences/pets2025/organizers.md new file mode 100644 index 0000000..52c60be --- /dev/null +++ b/_conferences/pets2025/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 30 +redirect_to: https://petsymposium.org/cfp25.php +--- \ No newline at end of file diff --git a/_conferences/pets2025/results.md b/_conferences/pets2025/results.md new file mode 100644 index 0000000..cd3f888 --- /dev/null +++ b/_conferences/pets2025/results.md @@ -0,0 +1,549 @@ +--- +title: Results +order: 40 +artifacts: + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0151.pdf" + title: "Tracker Installations Are Not Created Equal: Understanding Tracker Configuration of Form Data Collection" + artifact_url: "https://github.com/CybersecurityForDemocracy/trackers-not-equal/tree/11f90dc1711d604ea550137cf24d364c111055eb" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0063.pdf" + title: "Understanding Regional Filter Lists: Efficacy and Impact" + artifact_url: "https://github.com/internet-sicherheit/Understanding-Regional-Filter-Lists-Efficacy-and-Impact-/tree/a47d0eebd0df9dd2c5e78ca92c7217eebdc6df94" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0142.pdf" + title: "Sheep's clothing, wolfish impact: Automated detection and evaluation of problematic 'allowed' advertisements" + artifact_url: "https://github.com/Racro/AcceptableAds_PETS/tree/6a595bb33e0be56df1b2290fea8954f29c6da6e9" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0062.pdf" + title: "Automating Governing Knowledge Commons and Contextual Integrity (GKC-CI) Privacy Policy Annotations with Large Language Models" + artifact_url: "https://github.com/JakeC007/Automated_GKC-CI_Privacy_Policy_Annotations/tree/6e964c98b148d51d9ccdbf6a0cf1f06d93217ec1" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0077.pdf" + title: "RPKI-based Location-Unaware Tor Guard Relay Selection Algorithms" + artifact_url: "https://github.com/z-lu2017/TOR-RPKI/tree/83c4c84affa967100966c318ce0e585d6d369c2b" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0067.pdf" + title: "The Last Hop Attack: Why Loop Cover Traffic over Fixed Cascades Threatens Anonymity" + artifact_url: "https://github.com/Ti-ger/Last_Hop_Attack/tree/2e5ea768949f8689c9320d4f5d2002ff6b20e34c" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0046.pdf" + title: "Time-Efficient Locally Relevant Geo-Location Privacy Protection" + artifact_url: "https://github.com/chenxiunt/LocalRelevant_Geo-Obfuscation/tree/ebcd8afa1715e42baf29d21096e58c9365171cc1" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0008.pdf" + title: "SoK: Descriptive Statistics Under Local Differential Privacy" + artifact_url: "https://github.com/mad-lab-fau/sok-ldp-data-analysis/tree/df6372a45b9c98ae093cc48afe43c9b5aff29f33" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0076.pdf" + title: "Efficient Verifiable Differential Privacy with Input Authenticity in the Local and Shuffle Model" + artifact_url: "https://github.com/xQiratNL/VLDP/tree/v1.1.0" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0124.pdf" + title: "Optimal Piecewise-based Mechanism for Collecting Bounded Numerical Data under Local Differential Privacy" + artifact_url: "https://github.com/ZhengYeah/Optimal-GPM/releases/tag/v1.0.0" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0026.pdf" + title: "SoK: (Un)usable Privacy: the Lack of Overlap between Privacy-Aware Sensing and Usable Privacy Research" + artifact_url: "https://github.com/ISC-Lab/sok_artifact/commit/fd348c3661b8ef9be573f73482251a3594dd1d47" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0006.pdf" + title: "Identifying Privacy Personas" + artifact_url: "https://github.com/idiap/identifying-privacy-personas/tree/7fe0bf45025f07fc52a7b68affed8afc6e9a672" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0050.pdf" + title: "Echoes of Privacy: Uncovering the Profiling Practices of Voice Assistants" + artifact_url: "https://github.com/NEU-SNS/voice-assistants-pets25/tree/59ec90ef31d7b753b09a1a9fa2da3ecc68612af1" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0123.pdf" + title: "Improved Open-World Fingerprinting Increases Threat to Streaming Video Privacy but Realistic Scenarios Remain Difficult" + artifact_url: "https://github.com/timwalsh300/open-world-vf/releases/tag/PETS" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0164.pdf" + title: "Buy it Now, Track Me Later: Attacking User Privacy via Wi-Fi AP Online Auctions" + artifact_url: "https://github.com/lakewood999/ebay-mac-pipeline/tree/6c65c2485ed871d5d4002b0342097293cbf697d5" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0044.pdf" + title: "Towards Privacy-preserving and Fairness-aware Federated Learning Framework" + artifact_url: "https://github.com/anonymous141592/FHE-Fairness-aware-FL/tree/bf582bbf6c1460e725146ca4ffe1a5d1f3f5aa48" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0127.pdf" + title: "Unveiling Client Privacy Leakage from Public Dataset Usage in Federated Distillation" + artifact_url: "https://github.com/horanshi/Privacy_PDAFD/tree/6d327dcaa861a9ab7fd54af75dc79e4c18871604" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0108.pdf" + title: "Low-Cost Privacy-Preserving Decentralized Learning" + artifact_url: "https://github.com/dimiarbre/ZIP-DL/tree/artifact-submission" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0051.pdf" + title: "AnoFel: Supporting Anonymity for Privacy-Preserving Federated Learning" + artifact_url: "https://github.com/zghodsi/anofel/commit/244ea650a2c108183421b9b92c84aadb686db7f8" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0105.pdf" + title: "Panopticon: The Design and Evaluation of a Game that Teaches Data Science Students Designing Privacy" + artifact_url: "https://github.com/DataSmithLab/Panopticon/tree/236b792058b2cc65a43c55b624bb4649b4bbd328" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0144.pdf" + title: "Defining Privacy Engineering as a Profession" + artifact_url: "https://github.com/blues-lab/priv-eng-dataset/tree/ca35ffbb3c38ff7877c01ee92bfda29b2033ae6e" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0167.pdf" + title: "\"Do It to Know It\": Reshaping the Privacy Mindset of Computer Science Undergraduates" + artifact_url: "https://github.com/MaishaB/undergraduate-privacy-curriculum/tree/0a7f27a8b4220298040323fb100daa658583717b" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0070.pdf" + title: "DB-PAISA: Discovery-Based Privacy-Agile IoT Sensing+Actuation" + artifact_url: "https://github.com/sprout-uci/DB-PAISA/tree/5f1eaf424eb8734dce78c71422e25ea938ca747e" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0040.pdf" + title: "PrivacyGuard: Exploring Hidden Cross-App Privacy Leakage Threats In IoT Apps" + artifact_url: "https://github.com/PrivacyGuard-PETS/PrivacyGuard/tree/f9ad12ccbef7eb32e205abccfa7b64258a00e253" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0121.pdf" + title: "WatchWitch: Interoperability, Privacy, and Autonomy for the Apple Watch" + artifact_url: "https://github.com/seemoo-lab/watchwitch/tree/a4f77b704274f6e1f1e0e8319bf6c0d6465687e5" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0028.pdf" + title: "Janus: Fast Privacy-Preserving Data Provenance For TLS" + artifact_url: "https://github.com/jplaui/janus_artifacts/tree/a2390d6c69cff7a1b73e87b96ac4a05e70fcb55d" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0140.pdf" + title: "Path to Encrypted DNS with DDR: Adoption, Configuration Patterns, and Privacy Implications" + artifact_url: "https://doi.org/10.5281/zenodo.15685011" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0139.pdf" + title: "Akeso: Bringing Post-Compromise Security to Cloud Storage" + artifact_url: "https://github.com/etclab/akeso-artifact/tree/e08c958b95da04c32ae3f716bb49e7cc61c1e738" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0119.pdf" + title: "TEEMS: A Trusted Execution Environment based Metadata-protected Messaging System" + artifact_url: "https://git-crysp.uwaterloo.ca/iang/teems/src/popets-artifact/ARTIFACT-EVALUATION.md" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0173.pdf" + title: "Message Authentication Code with Fast Verification over Encrypted Data and Applications" + artifact_url: "https://github.com/ASEC-lab/auth-HE-retrieval/tree/876daf9bccc075b9e04ff071d4bb23093a710186" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0099.pdf" + title: "Teaching an Old Dog New Tricks: Verifiable FHE Using Commodity Hardware" + artifact_url: "https://github.com/mit-enclaves/argos/tree/65b74b4ca6597247d008cbf41480dd6ad5cea64f" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0022.pdf" + title: "BehaVR: User Identification Based on VR Sensor Data" + artifact_url: "https://github.com/UCI-Networking-Group/BehaVR/tree/516a1296a9bb9d8a8e6a90a4aaf8fa686d83101d" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0038.pdf" + title: "How Unique is Whose Web Browser? The role of demographics in browser fingerprinting among US users" + artifact_url: "https://github.com/aberke/fingerprinting-study/tree/7a776b99565e277f230dddfb9693c55ba3930da8" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0138.pdf" + title: "Intractable Cookie Crumbs: Unveiling the Nexus of Stateful Banner Interaction and Tracking Cookies" + artifact_url: "https://github.com/bannerclick/bannerclick/tree/v0.26.0_pets25_artifact" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0074.pdf" + title: "Onion-Location Measurements and Fingerprinting" + artifact_url: "https://github.com/pylls/ol-measurements-and-fp/tree/6fe53382235abc5daec8b7e6649f523fa78ce01c" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0007.pdf" + title: "Beyond the Request: Harnessing HTTP Response Headers for Cross-Browser Web Tracker Classification in an Imbalanced Setting" + artifact_url: "https://github.com/wolfrieder/http-response-classifier/tree/c57f88785fec19e54c8f4d9aa12f742834e3fd9a" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0053.pdf" + title: "Unmasking the Shadows: A Cross-Country Study of Online Tracking in Illegal Movie Streaming Services" + artifact_url: "https://edmond.mpg.de/dataset.xhtml?persistentId=doi:10.17617/3.STVMDI" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0135.pdf" + title: "SoK: Truncation Untangled: Scaling Fixed-Point Arithmetic for Privacy-Preserving Machine Learning to Large Models and Datasets" + artifact_url: "https://github.com/chart21/hpmpc/blob/7c4132243abf11c940b2a70aad875a6be6912402/measurements/configs/artifacts/truncation/ARTIFACT_EVALUATION.md" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0054.pdf" + title: "SpinML: Customized Synthetic Data Generation for Private Training of Specialized ML Models" + artifact_url: "https://github.com/bitzj2015/SpinML-Artifact/tree/f34b9a9ae65af22db10b799c1824677fef852585" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0088.pdf" + title: "Achieving Data Reconstruction Hardness and Efficient Computation in Multiparty Minimax Training" + artifact_url: "https://github.com/asu-crypto/ppgan/tree/1dcb7804720941b92a6504cbf2c6f81b1fcdb9f9" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0090.pdf" + title: "PIGEON: A High Throughput Framework for Private Inference of Neural Networks using Secure Multiparty Computation" + artifact_url: "https://github.com/chart21/hpmpc/tree/a07c3ff0b39222afe092231fd5ac25b8cae7ed7f" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0087.pdf" + title: "Differentially Private Release of Hierarchical Origin/Destination Data with a TopDown Approach" + artifact_url: "https://github.com/aidaLabDEI/TDA_hierarchical/tree/6f8d70bf6d5ef2b39cd099c65d3c4b4160231d73" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0097.pdf" + title: "Locally Differentially Private Frequency Estimation via Joint Randomized Response" + artifact_url: "https://github.com/ZhengYeah/JRR/releases/tag/v1.0.0" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0129.pdf" + title: "Estimating Group Means Under Local Differential Privacy" + artifact_url: "https://github.com/mad-lab-fau/ldp-group-mean/tree/9fe89f92f36af8973e6b59115030ac75d8f3cdac" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0002.pdf" + title: "Understanding Privacy Norms through Web Forms" + artifact_url: "https://github.com/UCI-Networking-Group/webform/tree/PoPETs-AE-v1" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0098.pdf" + title: "Learning Privacy from Visual Entities" + artifact_url: "https://github.com/graphnex/privacy-from-visual-entities/tree/ac9322e7c7b7860d8eea3b6ea9830518fa31c4ef" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0052.pdf" + title: "Surveillance Disguised as Protection: A Comparative Analysis of Sideloaded and In-Store Parental Control Apps" + artifact_url: "https://github.com/em4i/Surveillance-Disguised-as-Protection_Artifacts/tree/3d525b8246b87b30fd3290179f01b0eeb728e7b4" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0163.pdf" + title: "What WeChat Knows: Pervasive First-Party Tracking in a Billion-User Super-App Ecosystem" + artifact_url: "https://github.com/citizenlab/wechat-security-report/tree/artifact" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0056.pdf" + title: "Privacy Settings of Third-Party Libraries in Android Apps: A Study of Facebook SDKs" + artifact_url: "https://github.com/DavidRodriguezTorrado/PrivacySDKSettingsAnalyzer/tree/9db2f6514277983c9549acecf1ad4f302afb8802" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0042.pdf" + title: "The Impact of Default Mobile SDK Usage on Privacy and Data Protection" + artifact_url: "https://github.com/Impact-of-Mobile-SDK-Usage-on-Privacy/artifact/tree/feae392f07f8f8f4d73e9a10fa92c1e9c8f64927" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0029.pdf" + title: "Improving the Performance and Security of Tor’s Onion Services" + artifact_url: "https://github.com/BARC-Purdue/CenTor/tree/d2a9efe839df73de7aee87a317a8725b391e0042" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0060.pdf" + title: "Are Neuromorphic Architectures Inherently Privacy-preserving? An Exploratory Study" + artifact_url: "https://github.com/AyanaMoshruba/Neuromorphic_Privacy/tree/640708de29d6c8744397394b6f210975c34a53a7" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0015.pdf" + title: "High-Throughput Secure Multiparty Computation with an Honest Majority in Various Network Settings" + artifact_url: "https://github.com/chart21/hpmpc/tree/334f71c7986630cadb43dbbb8c6c7fba7f060809" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0055.pdf" + title: "Private Shared Random Minimum Spanning Forests" + artifact_url: "https://github.com/MarianDietz/secure-msf/tree/v0.1" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0017.pdf" + title: "Mastic: Private Weighted Heavy-Hitters and Attribute-Based Metrics" + artifact_url: "https://github.com/TrustworthyComputing/mastic/tree/pets-2025.1" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0061.pdf" + title: "Practical, Private Assurance of the Value of Collaboration via Fully Homomorphic Encryption" + artifact_url: "https://github.com/Ryndalf/Label-Encrypted/tree/e205bbf07135fb917536ba9383988a89a328d60c" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0078.pdf" + title: "MProve-Nova: A Privacy-Preserving Proof of Reserves Protocol for Monero" + artifact_url: "https://github.com/varunthakore/mprove-nova/tree/af9ed3424b523e86df161969cd4001e9e8e98417" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0168.pdf" + title: "Silent Splitter: Privacy for Payment Splitting via New Protocols for Distributed Point Functions" + artifact_url: "https://github.com/mapierce23/psa/tree/4c0b809ab30ffdf24a449754167e7bad9d90c2f5" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0089.pdf" + title: "GNNBleed: Inference Attacks to Unveil Private Edges in Graphs with Realistic Access to GNN Models" + artifact_url: "https://github.com/szyszyzys/GNNBleed/tree/77a91ddcb61c7d0ea145b303c8ce305a8e4d3961" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0093.pdf" + title: "A non-comparison oblivious sort and its application to private k-NN" + artifact_url: "https://github.com/sofianeazogagh/knn/tree/v2" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0166.pdf" + title: "MultiCent: Secure and Scalable Computation of Centrality Measures on Multilayer Graphs" + artifact_url: "https://github.com/encryptogroup/MultiCent/tree/v0.1.1" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0110.pdf" + title: "WaKA: Data Attribution using K-Nearest Neighbors and Membership Privacy Principles" + artifact_url: "https://github.com/patrickmesana/waka/tree/06740c9ab8c0d1b6a6821d487edff2b680309451" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0131.pdf" + title: "Aimless Onions: Mixing without Topology Information" + artifact_url: "https://github.com/kit-ps/aimless-onions/tree/b6774e5ff14b9c6f2ed1dbd834ef6969bcfbd24b" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0018.pdf" + title: "Real-world Deniability in Messaging" + artifact_url: "https://github.com/si-co/rwdm/tree/c81cb1d1517dc59bef1156934ebeee61129d11f6" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0081.pdf" + title: "Enhancing Metric Privacy With a Shuffler" + artifact_url: "https://github.com/andathan/metric_privacy_shuffle_model/tree/metric_shuffle_code_2" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0171.pdf" + title: "Non-Interactive Verifiable Aggregation" + artifact_url: "https://github.com/WeiqiNs/NIVA/tree/b6d9767a369cd2d876014ddddb53b77d4886f342" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0112.pdf" + title: "Stochastic Models for Remote Timing Attacks" + artifact_url: "https://github.com/Asterius27/SecPerf-Artifacts/tree/c31491f2cd8a1fa8c4557ecaa90f1e7d6ac90e7b" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0024.pdf" + title: "Searchable Encryption for Conjunctive Queries with Extended Forward and Backward Privacy" + artifact_url: "https://github.com/MonashCybersecurityLab/SDSSE/tree/v1.0.0-paper" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0169.pdf" + title: "More and Scammier Ads: The Perils of YouTube's Ad Privacy Settings" + artifact_url: "https://github.com/CybersecurityForDemocracy/youtube-ad-settings/tree/artifact-eval" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0148.pdf" + title: "Navigating Social Media Privacy: Awareness, Preferences, and Discoverability" + artifact_url: "https://github.com/STEELISI/Social-Media-Privacy-Awareness-Preferences-Discoverability/tree/81bf39637d8877b23ab6a881c9941e1013c5a651" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0157.pdf" + title: "Making Web Applications GDPR Compliant: A Comparative Evaluation of GDPR-Enforcement Frameworks" + artifact_url: "https://doi.org/10.5281/zenodo.15631563" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0133.pdf" + title: "Johnny Can't Revoke Consent Either: Measuring Compliance of Consent Revocation on the Web" + artifact_url: "https://github.com/Gayatri-Priyadarsini/Measuring-Compliance-of-Consent-Revocation-on-the-Web/tree/03a8c9bc38b289d32cade782ed95dca25a9a0861" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0152.pdf" + title: "Meta-Learn to Unlearn: Enhanced Exact Machine Unlearning in Recommendation Systems with Meta-Learning" + artifact_url: "https://github.com/alshabae/EEMU/tree/7d68bbd84309a4103b2b6f0ad99309299ae71909" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0101.pdf" + title: "Vote&Check: Secure Postal Voting with Reduced Trust Assumptions" + artifact_url: "https://inria.hal.science/hal-04813613" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0102.pdf" + title: "Does Coding Style Really Survive Compilation? Stylometry of Executable Code Revisited" + artifact_url: "https://github.com/sprlab/binary-stylometry/tree/artifact" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0034.pdf" + title: "PrePaMS: Privacy-Preserving Participant Management System for Studies with Rewards and Prerequisites" + artifact_url: "https://github.com/vs-uulm/prepams/tree/pets25.1" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0083.pdf" + title: "Wave Hello to Privacy - Efficient Mixed-Mode MPC using Wavelet Transforms" + artifact_url: "https://github.com/NillionNetwork/WaveHelloToPrivacy/tree/9d8165e78aa9814b4fbff3c4891c8af21f30ec5b" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0147.pdf" + title: "Okay Google, Where’s My Tracker? Security, Privacy, and Performance Evaluation of Google’s Find My Device Network" + artifact_url: "https://github.com/seemoo-lab/Artifacts-for-Okay-Google-Where-is-My-Tracker/tree/pets25-artifact-evaluation" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0122.pdf" + title: "An Analysis of Censorship Bias in LLMs" + artifact_url: "https://huggingface.co/collections/mohamedah/an-analysis-of-chinese-censorship-bias-in-llms-683f0916ef3fb0fc657372d9" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0012.pdf" + title: "DiDOTS: Knowledge Distillation from Large-Language-Models for Dementia Obfuscation in Transcribed Speech" + artifact_url: "https://github.com/domiwk/didots/tree/995364c938599cbdf4eb4384a7d701d2ee53c4a8" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0126.pdf" + title: "Robust and Efficient Watermarking of Large Language Models Using Error Correction Codes" + artifact_url: "https://github.com/luan-xiaokun/permumark/tree/c54393e523c0d14e65143331380a06a85744ffa6" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0146.pdf" + title: "HyDia: FHE-based Facial Matching with Hybrid Approximations and Diagonalization" + artifact_url: "https://github.com/n7koirala/image_matching/tree/1a2f0ab9457a5b1eb4461aa6af8a0ae8ae4a5ac9" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0020.pdf" + title: "EpiOracle: Privacy-Preserving Cross-Facility EarlyWarning for Unknown Epidemics" + artifact_url: "https://github.com/Yuan-Zhang-uestc/EpiOracleCode/commit/3ccebbf25539a7847b1bfd42a44af03e454a1eab" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0145.pdf" + title: "TimberStrike: Dataset Reconstruction Attack Revealing Privacy Leakage in Federated Tree-Based Systems" + artifact_url: "https://github.com/necst/TimberStrike/releases/tag/pets25-artifact-evaluation" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0134.pdf" + title: "AlphaFL: Secure Aggregation with Malicious² Security for Federated Learning against Dishonest Majority" + artifact_url: "https://github.com/Barkhausen-Institut/AlphaFL/tree/555426323ddbc2d0f463a5b84d3f8b2a9be3f231" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0043.pdf" + title: "Noiseless Privacy-Preserving Decentralized Learning" + artifact_url: "https://github.com/sacs-epfl/shatter/tree/shatter-pets-2025" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0030.pdf" + title: "Topology-Based Reconstruction Prevention for Decentralised Learning" + artifact_url: "https://data.4tu.nl/datasets/da119685-3288-4869-88c7-f8138066df66" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0080.pdf" + title: "OPPID: Single Sign-On with Oblivious Pairwise Pseudonyms" + artifact_url: "https://github.com/jmakr0/OPPID-artifacts/tree/artifact-review" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0065.pdf" + title: "VIMz: Private Proofs of Image Manipulation using Folding-based zkSNARKs" + artifact_url: "https://github.com/zero-savvy/vimz/tree/9505c178cd7767bdbd74857617a6968df699d8de" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0095.pdf" + title: "Client-Efficient Online-Offline Private Information Retrieval" + artifact_url: "https://github.com/vt-asaplab/pirex/tree/85090c619abbe2446c9b675a661ea0af322ab2c1" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0041.pdf" + title: "Re-visiting Authorized Private Set Intersection: A New Privacy-Preserving Variant and Two Protocols" + artifact_url: "https://github.com/markatou/Partial-APSI/tree/05fbf0f1faf8bd90e5f89b72421acfd3bb5c46ad" + badges: "available" + + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0118.pdf" + title: "PrivDiffuser: Privacy-Guided Diffusion Model for Data Obfuscation in Sensor Networks" + artifact_url: "https://github.com/sustainable-computing/PrivDiffuser/tree/26b17a921274b0224e8985d6be10945aedeb360f" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0149.pdf" + title: "Sybil-Resistant Parallel Mixnets" + artifact_url: "https://github.com/maya-kleinstein/Sybil-Resistant-Mixnet/tree/artifact" + badges: "available,functional,reproduced" + + - paper_url: "https://www.petsymposium.org/popets/2025/popets-2025-0129.pdf" + title: "Estimating Group Means Under Local Differential Privacy" + artifact_url: "https://github.com/mad-lab-fau/ldp-group-mean/tree/9fe89f92f36af8973e6b59115030ac75d8f3cdac" + badges: "available,functional,reproduced" + + - paper_url: "https://www.petsymposium.org/popets/2025/popets-2025-0143.pdf" + title: "Who’s Watching You Zoom? Investigating Privacy of Third-Party Zoom Apps" + artifact_url: "https://github.com/PERSUE-Lab-ASU/Zoom-Privacy-Data-Collection-Framework/tree/eaf7555062733fc710fb81d955b977871a42bdce" + badges: "available" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0071.pdf" + title: "PGUP: Pretty Good User Privacy for 5G-enabled Secure Mobile Communication Protocols" + artifact_url: "https://github.com/YYangNUS/PETS_PGUP/tree/e2e46ab3f6c3664fd7e548ad838cf093cc71fb95" + badges: "available,functional,reproduced" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0049.pdf" + title: "DiffPrivate: Facial Privacy Protection with Diffusion Models" + artifact_url: "https://github.com/minha12/DiffPrivate/tree/4f7e86c7308b4b09e04f1a619ec5e7c9afa0b939" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0154.pdf" + title: "Hypersphere Secure Sketch Revisited: Probabilistic Linear Regression Attack on IronMask in Multiple Usage" + artifact_url: "https://github.com/page0egap/probabilistic-linear-regression-attack-hypersphere-secure-sketch/tree/056cd39eaa2b52e400738dce0e039687b6ec7530" + badges: "available,functional" + + - paper_url: "https://petsymposium.org/popets/2025/popets-2025-0082.pdf" + title: "Maliciously Secure Circuit Private Set Intersection via SPDZ-Compatible Oblivious PRF" + artifact_url: "https://github.com/liang-xiaojian/McPSI/tree/4a1a3c0b9fcf6375e9c31849c34e389aa79920b9" + badges: "available,functional" + +--- + + + +Results obtained from PETS 2025 proceedings. + + + + + + + + + + {% for artifact in page.artifacts %} + + + + + {% endfor %} + +
TitleArtifact URL
+ {% if artifact.paper_url %} + {{artifact.title}} + {% else %} + {{ artifact.title }} + {% endif %} + + {% if artifact.artifact_url %} + {% if artifact.badges == "available" %} + Artifact: Available + {% elsif artifact.badges == "available,functional" %} + Artifact: Available, Functional + {% elsif artifact.badges == "available,functional,reproduced" %} + Artifact: Available, Functional, Reproduced + {% endif %} + {% endif %} +
+ diff --git a/_conferences/pets2026/ARTIFACT-APPENDIX.md b/_conferences/pets2026/ARTIFACT-APPENDIX.md new file mode 100644 index 0000000..bb5bfcd --- /dev/null +++ b/_conferences/pets2026/ARTIFACT-APPENDIX.md @@ -0,0 +1,271 @@ +# Artifact Appendix (Required for all badges) + +Paper title: **Enter the exact title of your PETS accepted paper here** + +Requested Badge(s): + - [ ] **Available** + - [ ] **Functional** + - [ ] **Reproduced** + +Authors can provide this content _either_ as a separate file in their artifact +_or_ as part of their existing documentation (e.g., `README.md`). In the latter +case, you should have the same section titles as in this template. + +This template includes several placeholders. When filling in this template for +their artifact, the authors should: + +1. Remove this note. +2. Delete the sections that are _not_ required for the badge(s) they are + applying for. +3. Omit suffixes of the form "(required/encouraged for badge ...)" from the + section titles. +4. Authors should not leave the placeholder descriptions initially provided with + this file into the submitted version with their artifact. + +While this template is provided for artifact review, you should write your +instructions for someone trying to reuse your artifact in the future (i.e., not +an artifact reviewer). + +## Description (Required for all badges) +Replace this with the following: + +1. List the paper that the artifact relates to (i.e., paper title, authors, + year, or even a BibTex cite). +2. A short description of your artifact and how it is relevant to your paper. + +### Security/Privacy Issues and Ethical Concerns (Required for all badges) + +Replace this with a description of security or privacy risks that your artifact +may hold for the machine of the person trying to evaluate or reuse your +artifact. This is especially relevant for artifacts that _disable a security +mechanism_, such as a firewall, ASLR, etc., to demonstrate an attack, as well as +to artifacts that _run vulnerable code_, such as exploits, malware samples, +etc., to demonstrate a vulnerability. + +User study artifacts that include anonymized transcripts or survey responses +should list the ethical review / IRB process followed to obtain participants' +consent to publishing this anonymized dataset. They may also list how +participants were compensated. + +## Basic Requirements (Required for Functional and Reproduced badges) + +For both sections below, if you are giving reviewers remote access to special +hardware (e.g., Intel SGX v2.0) or proprietary software (e.g., Matlab R2025a) +for the purpose of the artifact evaluation, do not provide these instructions +here but rather in the corresponding submission field on HotCRP. + +### Hardware Requirements (Required for Functional and Reproduced badges) + +Replace this with the following: + +1. A list of the _minimal hardware requirements_ to execute your artifact. If no + specific hardware is needed, then state "Can run on a laptop (No special + hardware requirements)". You may state how a researcher could gain access to + that hardware, e.g., by buying, renting, or even emulating it. +2. When applying for the "Reproduced" badge, list _the specifications of the + hardware_ on which the experiments reported in the paper were performed. This + is especially relevant in cases were results might be influenced by the + hardware used (e.g., latency, bandwidth, throughput experiments, etc.). + +### Software Requirements (Required for Functional and Reproduced badges) + +Replace this with the software required to run your artifact and its versions, +as follows. + +1. List the OS you used to run your artifact, along with its version (e.g., + Ubuntu 22.04). If your artifact can only run on a specific OS or a specific + OS version, list it and explain why here. In general, your artifact reviewers + will probably have access to a machine with a different OS or different OS + version than yours; they should still be able to run appropriately packaged + artifacts. +2. List the OS packages that your artifact requires, along with their versions. +3. Artifact packaging: If you use a container runtime (e.g., Docker) to run the + artifact, list the container runtime and its version (e.g., Docker 23.0.3). + If you use VMs, list the hypervisor (e.g., VirtualBox) to run the artifact. +4. List the programming language compiler or interpreter you used to run your + artifact (e.g., Python 3.13.7). Your Docker image or VM image should have + this version of the programming languages installed already. Your Dockerfile + should start from a base image with this programming language version. +5. List packages that your artifact depends on, along with their versions. For + example, Python-based privacy-preserving machine learning artifacts typically + require `numpy`, `scipy`, etc. You may point to a file in your artifact with + this list, such as a `requirements.txt` file. If you rely on proprietary + software (e.g. Matlab R2025a), list this here and consider providing access + to reviewers through HotCRP. +6. List any Machine Learning Models required to run your artifact, along with + their versions. If your model is hosted on a different repository, such as on + Zenodo, then your artifact should download it automatically (same for + datasets). If a required ML model is _not_ in your artifact, provide a dummy + model to demonstrate the functionality of the rest of your artifact. +7. List any datasets required to run your artifact. If any required dataset is + not in your artifact, you should provide a synthetic dataset that showcases + the expected data format. + +### Estimated Time and Storage Consumption (Required for Functional and Reproduced badges) + +Replace the following with estimated values for: + +- The overall human and compute times required to run the artifact. +- The overall disk space consumed by the artifact. + +This helps reviewers schedule the evaluation in their time plan and others in +general to see if everything is running as intended. This should also be +specified at a finer granularity for each experiment (see below). + +## Environment (Required for all badges) + +In the following, describe how to access your artifact and all related and +necessary data and software components. Afterward, describe how to set up +everything and how to verify that everything is set up correctly. + +### Accessibility (Required for all badges) + +Replace the following by a description of how to access your artifact via +persistent sources. Valid hosting options are institutional and third-party +digital repositories (e.g., GitHub, Gitlab, BitBucket, Zenodo, Figshare, etc.). +Please do not use personal web pages or cloud storage services like Google +Drive, Dropbox, etc. + +Note that once your artifact evaluation is finalized and a badge decision has +been made, artifact chairs will collect a stable and persistent reference to +your artifact to list on the website. For version-controlled repositories (e.g., +Git repositories), this will be a specific commit-id or tag. + +You _should not_ link to a specific commit here at submission time, as changes +will likely happen during the evaluation process to address the reviewers' +feedback, resulting in the link being out-of-date. Instead, you may link to the +latest commit in your branch (e.g. main) as follows: +https://github.com/PoPETS-AEC/example-docker-python-pip/tree/main + +### Set up the environment (Required for Functional and Reproduced badges) + +Replace the following by a description of how one should set up the environment +for your artifact, including downloading and installing dependencies and the +installation of the artifact itself (i.e., from the very first download or clone +command one should perform). Be as specific as possible here. If possible, use +code segments to simplify the workflow, e.g., + +```bash +git clone git@github.com:PoPETS-AEC/example-docker-python-pip.git +docker build -t example-docker-python-pip:main . +``` + +Describe the expected results where it makes sense to do so. + +### Testing the Environment (Required for Functional and Reproduced badges) + +Replace the following by a description of the basic functionality tests to check +if the environment is set up correctly. These tests could be unit tests, +training an ML model on very low training data, etc. If these tests succeed, all +required software should be functioning correctly. Use code segments to simplify +the workflow, e.g., + +Launch the Docker container, attach the current working directory (i.e., run +from the root of the cloned git repository) as a volume, set the context to be +that volume, and provide an interactive bash terminal: + +```bash +docker run --rm -it -v ${PWD}:/workspaces/example-docker-python-pip \ + -w /workspaces/example-docker-python-pip \ + --entrypoint bash example-docker-python-pip:main +``` + +Then within the Docker container, run: + +```bash +./test.sh +``` + +Include the expected output. + +## Artifact Evaluation (Required for Functional and Reproduced badges) + +This section should include all the steps required to evaluate your artifact's +functionality and validate your paper's key results and claims. Therefore, +highlight your paper's main results and claims in the first subsection. And +describe the experiments that support your claims in the subsection after that. + +### Main Results and Claims + +List all your paper's results and claims that are supported by your submitted +artifacts. + +#### Main Result 1: Name + +Describe the results in 1 to 3 sentences. Mention what the independent and +dependent variables are; independent variables are the ones on the x-axes of +your figures, whereas the dependent ones are on the y-axes. By varying the +independent variable (e.g., file size) in a given manner (e.g., linearly), we +expect to see trends in the dependent variable (e.g., runtime, communication +overhead) vary in another manner (e.g., exponentially). Refer to the related +sections, figures, and/or tables in your paper and reference the experiments +that support this result/claim. See example below. + +#### Main Result 2: Example Name + +Our paper claims that when varying the file size linearly, the runtime also +increases linearly. This claim is reproducible by executing our +[Experiment 2](#experiment-2-example-name). In this experiment, we change the +file size linearly, from 2KB to 24KB, at intervals of 2KB each, and we show that +the runtime also increases linearly, reaching at most 1ms. We report these +results in "Figure 1a" and "Table 3" (Column 3 or Row 2) of our paper. + +### Experiments +List each experiment to execute to reproduce your results. Describe: + - How to execute it in detailed steps. + - What the expected result is. + - How long it takes to execute in human and compute times (approximately). + - How much space it consumes on disk (approximately) (omit if <10GB). + - Which claim and results does it support, and how. + +#### Experiment 1: Name +- Time: replace with estimate in human-minutes/hours + compute-minutes/hours. +- Storage: replace with estimate for disk space used (omit if <10GB). + +Provide a short explanation of the experiment and expected results. Describe +thoroughly the steps to perform the experiment and to collect and organize the +results as expected from your paper (see example below). Use code segments to +simplify the workflow, as follows. + +```bash +python3 experiment_1.py +``` + +#### Experiment 2: Example Name + +- Time: 10 human-minutes + 3 compute-hours +- Storage: 20GB + +This example experiment reproduces +[Main Result 2: Example Name](#main-result-2-example-name), the following script +will run the simulation automatically with the different parameters specified in +the paper. (You may run the following command from the example Docker image.) + +```bash +python3 main.py +``` + +Results from this example experiment will be aggregated over several iterations +by the script and output directly in raw format along with variances and +standard deviations in the `output-folder/` directory. You will also find there +the plots for "Figure 1a" in `.pdf` format and the table for "Table 3" in `.tex` +format. These can be directly compared to the results reported in the paper, and +should not quantitatively vary by more than 5% from expected results. + + +## Limitations (Required for Functional and Reproduced badges) + +Describe which steps, experiments, results, graphs, tables, etc. are _not +reproducible_ with the provided artifact. Explain why this is not +included/possible and argue why the artifact should _still_ be evaluated for the +respective badges. + +## Notes on Reusability (Encouraged for all badges) + +First, this section might not apply to your artifacts. Describe how your +artifact can be used beyond your research paper, e.g., as a general framework. +The overall goal of artifact evaluation is not only to reproduce and verify your +research but also to help other researchers to re-use and extend your artifacts. +Discuss how your artifacts can be adapted to other settings, e.g., more input +dimensions, other datasets, and other behavior, through replacing individual +modules and functionality or running more iterations of a specific module. diff --git a/_conferences/pets2026/aec-call.md b/_conferences/pets2026/aec-call.md new file mode 100644 index 0000000..ef97f2a --- /dev/null +++ b/_conferences/pets2026/aec-call.md @@ -0,0 +1,142 @@ +--- +title: Call for Artifacts +order: 10 +--- + +## Artifact Submission Steps for Authors + +1. Please include the content of the + [`ARTIFACT-APPENDIX.md`](/pets2026/ARTIFACT-APPENDIX.md) file either within + your `README.md` file or as a separate file. The file is important for not + only reviewers during the evaluation process, but also for future researchers + attempting to re-use your artifact. This file has different, marked sections + for different badges. +2. Decide which badges you want to apply for. As we describe below, in general, + all submitted artifact should apply at least for "Artifact Available" badge, + unless doing so would endanger someone. Authors should apply to all the + badges for which they believe that their artifact meets the respective badge + requirements. +3. Ensure that you have filled out _all_ sections of the `ARTIFACT-APPENDIX.md` + file that are relevant for the badges that you apply for. +4. For your submission on HotCRP, you will need to provide a copy of your paper + and a direct link to the `ARTIFACT-APPENDIX.md` file. + +## Artifact Badges + +See [badges](/pets2026/badges). + +## Artifact Link + +When the artifact evaluation is over, a persistent and stable link pointing to +the final evaluated version of the artifact will be collected for each accepted +artifact. Depending on the hosting option picked, this is likely a link to a +specific Git commit/tag or a DoI for a Zenodo record, etc. This link and the +awarded badge(s) will be added to the website next to the corresponding paper +title. As updates to the artifact are likely to occur to address reviewers' +feedback, we will only collect this link after a final decision is made. + + +## What makes a Good Submission + +To ensure a smooth submission process, please follow these important guidelines: + +- **Alpha-test your artifact** from a fresh install or ask a friend to do so. + Fix potential issues that are uncovered before submission. +- As discussed in the FAQ, go through the + [resources and examples](https://github.com/PoPETS-AEC/examples-and-other-resources) + of artifact packaging (Dockerfiles etc.) that have been put together by the + artifact evaluation chairs. +- For the "Artifact Functional" and/or "Artifact Reproduced" badges, clear + documentation and mapping between claims, results, and experiments usually go + a long way in facilitating the evaluation. Ideally, reviewers should be able + to execute a single script to install, configure, and reproduce results. +- **Respond professionally to reviews and comments within one week.** +- **Incorporate requested changes, at least partially, within two weeks after + the request**. Partial progress should be evident to reviewers through version + control (Git commits or updates to Zenodo records etc.). Do _not_ leave + updates to the last minute. If some fixes require more time, authors _should_ + communicate a timeline by which these changes will be made for reviewers to + plan a re-evaluation. + +Your cooperation in adhering to these guidelines will greatly contribute to the +efficiency and effectiveness of your submission and review process. We eagerly +anticipate receiving your high-quality contributions and look forward to +showcasing your research! + +### Artifact Award + +Since PETS 2022, distinguished artifacts are recognized by an +[artifact award](https://petsymposium.org/artifact-award.php). The main +objective through that award is to reward authors who put a lot of effort into +the release of their artifact and to showcase exemplar submissions that +contribute to the open-science and reproducibility efforts of our community. + +Since PETS 2026, we provide explicit criteria for reviewers to judge whether an +artifact should be nominated for this award. Reviewers should consider the +artifact quality, completeness, documentation, ease of reuse, artifact maturity +and scope of its target audience, interactivity and responsiveness of authors, +etc. Ultimately, nominations are reviewed and ranked. + +Our suggestion to authors is to simply prepare and release their artifact in the +same way that they wish anyone in their field would do to facilitate adoption +and reproducibility by others. + +## What Makes a Good Review + +Artifact reviewers should familiarize themselves with the artifact call, the +aforementioned guidelines, and the format of the `ARTIFACT-APPENDIX.md` file. +Reviewers should reach out to artifact chairs with any questions. + +Towards the goal of contributing to open-science and reproducibility, the +artifact evaluation process is designed to be interactive; authors are expected +to take into account reviewers' comments and modify their artifact accordingly. +As such, reviewers are kindly asked to start their evaluation as early as +possible and to post reviews or comments regularly. Once authors communicate to +reviewers that issues were resolved, reviewers should then take another look and +either approve the artifact or provide additional comments until a final +decision is made. + +We provide practical tips for reviewers below: + +- **Start the evaluation early.** +- Notify artifact evaluation chairs **ASAP** if you are missing hardware or + resources to perform the evaluation. +- Post a preliminary review and update it as authors make edits. Adding an + "[EDIT]" tag or striking out the text of the prior review can indicate + modified and/or solved comments, etc. +- Provide a concise list of issues/suggestions first (this helps give an + overview to everyone), followed by more details (for the authors to make + changes). +- Explicitly number or name these issues/suggestions; doing so facilitates + future references to them in comments between authors and reviewers. +- If the code fails, include the environment that it is run on, the error + messages, and potential steps that were attempted to fix them. +- Actively participate in the discussions. +- Politely ping authors for updates or for a timeline if no response is received + to your comments after a week. +- Respond politely and professionally. +- Tag artifact evaluation chairs if you do not hear back from the authors, or if + something needs to be brought up to our attention. + +### Distinguished Artifact Reviewers + +Since PETS 2025, we recognize members of the artifact evaluation committee as +[distinguished artifact +reviewers](https://petsymposium.org/reviewer-awards.php), based on the following +criteria: + +- Timeliness, including responding to authors' updates. +- High quality reviews and discussions that significantly improve the artifact. +- Going above and beyond, such as by helping out with extra reviews, helping + with artifacts with special requirements, etc. + +### Volunteer for the Artifact Evaluation Committee + +We are looking for volunteers to serve on the artifact evaluation committee. As +a committee member, you will perform review of artifacts according to the +guidelines above. We are looking for volunteers who will be interested in +providing feedback on documentation and instructions, trying to get source code +to build, or have experience with re-using published datasets. Please fill out +the reviewer nomination form linked in the menu of the PETS website. + + diff --git a/_conferences/pets2026/badges.md b/_conferences/pets2026/badges.md new file mode 100644 index 0000000..5caef3c --- /dev/null +++ b/_conferences/pets2026/badges.md @@ -0,0 +1,179 @@ +--- +title: Badges +order: 20 +--- + + + +Each accepted artifact can be granted up to three badges. During submission, +authors must select which badges they want their artifacts to be evaluated +against. As we detail below, in general, all submitted artifact should apply at +least for "Artifact Available" badge, unless doing so would endanger someone. To +ease reviewing effort, we encourage authors to apply appropriately to all the +badges for which they believe requirements are met by their artifact. Our +interpretation of the individual badges is aligned with the one of [other +conferences](https://secartifacts.github.io/). If you have questions about which +badges to apply for, first go through the FAQ below and then please contact the +artifact evaluation chairs directly. + +## Artifact Available Artifact: Available + +For the "Artifact Available" badge, the reviewers check that the artifact is +publicly accessible, has a license and is relevant to the paper. + +Your artifact should be publicly accessible at a permanent location; it should +_not_ be behind any kind of paywall or restricted access or private repository. +If the artifact requires you as an author to manually approve requests for +access, it is not public and will not qualify for the "Artifact Available" +badge. Note that all components of your artifact should be publicly available +(e.g. source code, datasets, etc.). + +Valid hosting options are institutional and third-party digital repositories +(e.g., GitHub, Gitlab, BitBucket, Zenodo, Figshare, etc.). Do _not_ use personal +web pages or cloud storage services like Google Drive, Dropbox, etc. + +**All submitted artifacts should apply at least for "Artifact Available"**, +unless for some specific unusual situations when doing so could endanger +someone. For instance, if the artifact demonstrates exploiting a vulnerability +and the possible harms from releasing a proof of concept would outweigh the +benefits of making it available as part of a responsible disclosure process. In +this case, authors could apply for just the "Functional and Reproduced Badges". +If you wish to commercialize your project, you can and should still submit your +artifact for this badge, under restricted licensing, as discussed in the FAQ +below. + +The FAQ also provides resources on licensing, dealing with large files, and +linking to multiple repositories. + +### Checklist for "Available Badge": + +- [ ] Publicly available artifact with a single link. +- [ ] Presence of a license. +- [ ] Relevance to paper. +- [ ] Corresponding content from `ARTIFACT-APPENDIX.md` completed. + +This badge does _not_ mean that the reviewers have checked that the code +executes or that they have reproduced the results of the paper. + + +## Artifact Functional Artifact: Functional + + +To be awarded the "Artifact Functional" badge the artifact should satisfy these +criteria: + +- Documentation: The artifact clearly documents how it should be used (i.e., + installation + execution). +- Completeness: It includes all key components described in the paper. +- Exercisability: It includes the scripts and data needed to run the experiments + described in the paper. The software must successfully execute in the provided + environment. + +**Documentation:** The `ARTIFACT-APPENDIX.md` file within all source code +artifacts should describe how to build and/or run the code. Reviewers will +provide feedback on the clarity of the instructions and attempt to follow them +and build and run the code. + +**Completeness:** Consider the experiments in your artifact as arranged in a +pipeline of multiple stages, such as data collection, data processing, and +producing plots or tables for the paper. The "Completeness" criteria requires +each stage to be represented. For instance, an artifact may have a proprietary +machine learning model as a key component of the system, and so, achieving +completeness may be difficult. If you are unable to represent any stage, then +represent it in either a simplified manner or run it on dummy data, in order for +reviewers to check the functionality of the stage. Provide the expected outcome +of the fully run stage such that preceding stages are performed on 'real' data. +Under the FAQ, we have examples on how authors can still prepare their artifact +for the "Artifact Functional" badge in cases that involve licensing issues, +time, or resource constraints. + +**Exercisability:** All source code should be accompanied by a build environment +such as a Dockerfile or a virtual machine (VM) install script, with all the +dependencies (software _and_ datasets) necessary to build the code. Include and +pin the versions of your software dependencies. If the code is in a compiled +language, the code should compile in the provided build environment by running +the provided instructions. Compilation and setup should be automated as much as +possible. Ideally, there will be one script that builds your software, runs your +tests, and produces the results in a comprehensible way. + +To receive this badge, artifacts are _not_ required to be able to run on all +hardware and OSes. + +### Checklist for "Functional Badge": + +- [ ] Meets "Available Badge" requirements (except for unusual situations + discussed previously). +- [ ] Clear documentation is provided. +- [ ] Completeness criterion fulfilled (with potential limitations reasonably + argued). +- [ ] Exercisability criterion fulfilled (with potential limitations reasonably + argued). +- [ ] Corresponding content from `ARTIFACT-APPENDIX.md` completed. + +## Artifact Reproduced Artifact: Reproduced + + +The "Artifact Reproduced" badge requires the main claims of the paper to be +reproduced by the reviewers. Implicitly, an artifact awarded the "Artifact +Reproduced" badge needs to also meet the requirements of the "Artifact +Functional" badge. + +Authors must specify the commands to run the artifacts clearly and describe how +to reproduce each main claim of the paper. Best practice is to point out which +part of the paper is reproduced by a given script, e.g., name the table or +figure. Also, the authors must highlight which results of the paper are not +reproducible with the given artifact and explain why. Authors are encouraged to +contemplate how their artifact could be re-used by others in the future and +describe potential ways for improvement, etc. + +Authors are asked to automate as much of the execution of the experiments as +possible; manual effort from reviewers to run and interpret the results should +be minimized. For instance, if an experiment is performing a swap across +different parameters, a script automating it should be provided. Ideally, +results should also be automatically parsed and output in a comprehensible way, +as close to the output in the paper as possible (table or figure, etc.). + +To award the "Artifact Reproduced" badge, reviewers must be able to reproduce +the main claims of the paper with the provided artifact. As a rule of thumb, a +quantitative claim should generally be considered reproducible if the results +obtained by reviewers are within 5% of the reported value in the paper. That +being said, some artifact-specific factors may prevent this; in these cases, +artifact reviewers should also consider if the results that they obtain align +qualitatively with the claims made in the paper. It is the reviewer's role to +enforce that these quantitative and/or qualitative expectations are met before +awarding the "Artifact Reproduced" badge. + +Additionally, some experiments may by nature be harder to fully reproduced +during the timeframe of the artifact evaluation: e.g., take a while to run, need +several iterations, train a model on a large dataset, etc. In these cases, +authors should still provide the instructions and expected results for the +"long" version of the experiment, and also for a simplified one (e.g., fewer +iterations, smaller dataset, etc.). Indeed, even on a simplified version or +fewer runs, reviewers should still somewhat be able to look at the results and +the standard deviation, and check that results from the paper can be reproduced. + +Finally, some artifacts, such as longitudinal studies or hardware-based +contributions, may be infeasible for the “Artifact Reproduced” badge (see FAQ +below), as reviewers have limited time and only commodity hardware available. +Nevertheless, these authors can and should still prepare their artifacts for the +“Artifact Functional” badge. + +### Checklist for "Reproduced Badge": + +- [ ] Meets "Functional Badge" requirements. +- [ ] List of the core contributions and claims of the paper identified. +- [ ] Clear mapping between claims, experiments, and results provided. +- [ ] Minimal amount of manual effort required from reviewers, i.e., fair amount + of automation. +- [ ] Reviewers obtain reproducible results quantitatively (i.e., within 5% of + the claimed value) and/or qualitatively. +- [ ] Corresponding content from `ARTIFACT-APPENDIX.md` completed. \ No newline at end of file diff --git a/_conferences/pets2026/faq.md b/_conferences/pets2026/faq.md new file mode 100644 index 0000000..00a1c7c --- /dev/null +++ b/_conferences/pets2026/faq.md @@ -0,0 +1,233 @@ +--- +title: Frequently Asked Questions (FAQ) +order: 25 +--- + +## I want to commercialize my artifact. Should I still apply for any badges? + +IP protections and commercialization prospects should not inhibit authors from +applying for the "Artifact Available" badge. For instance, authors can choose +restrictive licenses that prohibit others from using their code. Alternately, +authors can design a smaller working prototype to demonstrate reproducibility of +the contributions of their paper. + +## Which license should I choose for my artifact? + +- For a clear, easy to follow guide see: [https://choosealicense.com/](https://choosealicense.com/) +- For more in-depth detail on open source and copy-left licenses, see + [https://www.gnu.org/licenses/license-list.en.html]() and + [https://opensource.org/licenses](https://opensource.org/licenses). +- Before you begin extending other authors' libraries, check that doing so would + comply with the terms of the license. + +## I need to upload a file that is larger than 100MB, but [GitHub does not allow that](https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github#about-size-limits-on-github). How can I make my file available? + +- If your file is at most 2GB, GitHub recommends + [using Git LFS](https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage). +- If your file is at most 50GB, then you should consider [hosting it as a record + on + Zenodo](https://support.zenodo.org/help/en-gb/1-upload-deposit/80-what-are-the-size-limitations-of-zenodo) + for example. Artifacts have also used + [Huggingface](https://huggingface.co/docs/hub/en/storage-limits) successfully + to host large ML models. +- If directly uploading your (compressed) file to one of the aforementioned + platforms does _not_ work, then you may split the file into multiple chunks. + You can also contact the artifact chairs if you have trouble with this step. +- Do _not_ use Google Drive or Dropbox links; they are not version-controlled or + persistent in any way. + +## My paper has several artifacts, such as one source code repository and few datasets, or multiple source code repositories for different purposes. What link should I use and submit? + +We will need a single link to put on the PETS website and all artifacts +associated with your paper should be discoverable from that one link. + +- If you have several Git repositories, we suggest using + [git submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules). + Reference specific hashes of Git commits when using Git submodules. +- If you are using Zenodo (or similar service) to host your datasets and a Git + repository for your code, ensure that your `README.md` in your Git repository + includes a link to the Zenodo record, and you may submit the link to your Git + repository for artifact evaluation. + +## I have a user study. How can I get the "Artifact Available" badge? + +An example of a +[good user study artifact](https://github.com/blues-lab/priv-eng-dataset/tree/ca35ffbb3c38ff7877c01ee92bfda29b2033ae6e) +is available here. Authors of papers with user studies can generally achieve the +"Artifact Available" badge, by including the following in their artifact: + +- User study questionnaire. +- If participants were informed of, and consented to, _anonymized_ transcript or + responses being released, explicitly mention this, and release these + transcripts or questionnaire responses. +- We also recommend including demographics of your user study participants. + +## I am designing a course or a game to teach privacy. How can I get the "Artifact Available" badge? + +Here are examples of artifacts regarding +[an undergraduate course](https://github.com/MaishaB/undergraduate-privacy-curriculum/tree/0a7f27a8b4220298040323fb100daa658583717b) +and a +[game](https://github.com/DataSmithLab/Panopticon/tree/236b792058b2cc65a43c55b624bb4649b4bbd328) +to teach privacy. + +For courses, thoroughly document the course structure, including the number of +lessons or modules, lesson titles, number and types of assessments. You should +also consider including: + + Written and programming exercises. +- Tutorials +- Assessments, including quizzes or exams. + +For games, document the game mechanics, game materials, setup instructions as +well as per-round instructions. You may include videos to supplement, but not +replace, your documentation. + +While in general we expect both game and course-related artifacts to be awarded +the "Artifact Available" badge, the aforementioned artifact included programming +exercises that could be fully exercised by the reviewers and was thus awarded +the "Artifact Functional" badge. + +## I don't have time to write a Dockerfile to build my project. Do you have examples? Should I upload a Dockerfile or a Docker image or both? + +Authors are encouraged to check out the [repository +examples](https://github.com/PoPETS-AEC/examples-and-other-resources) that have +been put together by the artifact evaluation chairs. + +These examples are in the form of GitHub repositories that include: + +- Dockerfiles for popular programming workflows, including Python-based + projects. +- GitHub Action workflows to _automatically_ generate a Docker image based on + the Dockerfile. Whenever the Dockerfile is changed, a new Docker image will be + released. That way, authors can focus on writing and releasing their + Dockerfile while reviewers can directly download the Docker image from the + "GitHub Container Registry" (or another registry like DockerHub if authors + follow resources we point to). + +Authors can fork these repositories, and use the fork as a starting point for +their artifact. For example, for Python-based projects, authors should modify +the `Dockerfile` and add the pinned versions of their dependencies to a +`requirements.txt` (or similar) file. + +Note that these resources are not comprehensive, so authors and reviewers are +not to interpret them as the only way to package an artifact; we also welcome +suggestions to these resources in the form of issues, pull requests, or direct +contributions. + +## Should I go for VMs or Docker? + +For most artifacts, we have found that a Dockerfile suffices. As in our response +to the question above, please check our [repository +examples](https://github.com/PoPETS-AEC/examples-and-other-resources) on GitHub. +If you use Docker: + +- Always include the Dockerfile and other scripts used to build the Docker image + in your artifact. +- Pin versions of dependencies as much as possible to avoid future breaking + changes (e.g., specify a specific hash rather than a loose `latest` tag for + the base image, same for dependencies versions). +- Note that if you do the above points, you do _not_ need to include both a +Dockerfile and a Docker image; we strongly prefer using a Dockerfile with pinned +versions. +- Finally, our example GitHub repository automatically generates a Docker image +from our (example) Dockerfile and publishes it as a "GitHub release", so you do +not need to worry about building and hosting the Docker image. + +VMs could be a better fit for artifacts that require multiple nodes +communicating with each other (you could also explore [Docker +Compose](https://docs.docker.com/compose/) if that fits your use case). If you +include a VM: + +- State the parameters used to create the VM, including the CPU architecture, + number of expected CPU cores, the amount of RAM to be given, maximum size of + the disk image that the VM was created with, BIOS/UEFI configuration. You + should also list any external virtualized hardware that needs to be + virtualized. +- Include the scripts or files required to build the VM image. +- Your VM should not usually have to download additional dependencies after you + run your installation scripts. If that is the case, reassess your build + process and consider making changes to limit the amount of network resources + needed. +- We provide artifact reviewers with VM instances that can be spawn from HotCRP + to perform the evaluation. Your artifact, however, should also be executable + in general, and not only on these VMs. Hence, your descriptions and scripts + should be as generic as possible. + +## My artifact runs on cloud computing platforms such as AWS EC2, etc., and requires access credentials. How can I prepare my artifact for review? + +Since PETS 2026, we have a dedicated submission field on HotCRP to allow authors +to specify account credentials, API access keys, etc. Authors should state the +amount of money/credits required to run the experiments and provide account +credentials with enough credits. Our reviewers are _not_ expected to invest +their money or provide their credit cards to set up accounts. + +If any form of credentials cannot be provided, provide an alternative way of +running your artifact; you may communicate with the artifact chairs. If this is +not possible, reconsider your choices of badges, as it may be impossible to +assess your artifact for the "Artifact Functional or Reproduced" badges. + +## My paper includes a dataset. How should I prepare the dataset? + +- Document your dataset so that others can reuse it. +- Add scripts to automatically download the dataset (if necessary), parse the + data, and produce the tables, graphs, or statistics that appear in the paper. +- If the dataset includes survey results, provide a copy of the original survey + with raw results. This is vital for replication studies and helping + researchers interpret the context of your results. + +Please refer to the instructions under one of the previous FAQs on how to upload +large files to your repository. + +## My paper involves a large machine learning (ML) model, or other such large files that are difficult to share. How can I get the "Artifact Functional" badge? + +If a large ML model, or other file is required to execute the presented tool, +the authors should include it within their artifact, unless it is proprietary. +If the dataset or model is not included in the artifact, authors must share a +synthetic dataset or dummy model, which may, perhaps perform worse, but which +can be used by other researchers to test the principle functionality of the +artifact. Authors should provide the code to train the original model, though +depending on the contributions of the paper, it need not be executed. + +Please refer to the instructions under one of the previous FAQs on how to upload +large files to your repository. + +## My experiment has a lengthy runtime or requires a large amount of compute resources. How can I get the "Artifact Functional" badge? + +Although experiments may require days or weeks of compute time on commodity +hardware, the "Artifact Functional" badge can usually still be achieved, by +following _each_ of the steps below. + +- Provide a simplified version of the experiments, which may run on fewer data + or fewer epochs of time, in order to enable the reviewers to check the + functionality of that stage. If the results of the simplified experiments + align with the ones reported in the paper, then authors can also aim for the + "Artifact Reproduced" badge. +- Provide instructions and results of the full experiment in the repository, so + that reviewers can verify the functionality of the later stages with these + results. + +## My paper involves a longitudinal study or crawl. How can I get the "Artifact Functional and Reproduced" badges? + +Authors should provide: + +- Anonymized raw data, unless forbidden by legal requirements, privacy, or + ethical concerns. In this case, authors should include a dataset with dummy or + synthetic data. Please follow the instructions above to upload large files to + your artifact. +- Evaluation scripts to reproduce the results of the paper. Reviewers should be + able to execute the evaluation scripts on either anonymized raw data or dummy + data. + +## My paper involves a hardware-based contribution. How can I prepare my artifact? + +- If the artifact requires GPU VMs, Trusted Execution Environments, IoT devices + and Smartphones, ensure that you indicate this at submission time. +- If other special hardware is required, then artifact chairs will attempt to + procure the hardware from other artifact evaluation committee members. If this + is not possible, then the artifact chairs may require authors to be involved + in a video call to evaluate the artifact for the "Artifact Functional" and + "Artifact Reproduced" badges. +- The authors may also simulate the hardware, though this can be challenging. +- Authors should additionally publish the raw results of the experiments, so + that reviewers can verify the remaining stages as functional. + diff --git a/_conferences/pets2026/index.md b/_conferences/pets2026/index.md new file mode 100644 index 0000000..b32f208 --- /dev/null +++ b/_conferences/pets2026/index.md @@ -0,0 +1,27 @@ +--- +title: Artifact Evaluation +order: 0 +--- + +PoPETs reviews and publishes digital artifacts related to its accepted papers. +This process aids in the reproducibility of results and allows others to build +on the work described in the papers. Artifact submissions are requested from +authors of all accepted papers, and although they are optional, we strongly +encourage you to submit your artifacts for review. + +Possible artifacts include (but are not limited to): + +- Source code (e.g., system implementation, proof of concepts) +- Datasets (e.g., network traces, raw study data) +- Machine-generated proofs +- Formal specifications +- Build environments (e.g., VMs, Docker containers, configuration scripts) +- User study questionnaires and aggregate, anonymized results + +Artifacts are evaluated by the artifact evaluation committee. Issues considered +include software bugs, readability of the documentation, appropriate licensing, +and the reproducibility of the results presented in the paper. After your +artifact has been approved by the committee, the paper link on +[petsymposium.org](https://petsymposium.org) will be accompanied by a link to +the artifact along with the obtained artifact badges so that interested readers +can find and build upon your work. \ No newline at end of file diff --git a/_conferences/pets2026/organizers.md b/_conferences/pets2026/organizers.md new file mode 100644 index 0000000..2a8ec2f --- /dev/null +++ b/_conferences/pets2026/organizers.md @@ -0,0 +1,5 @@ +--- +title: Organizers +order: 30 +redirect_to: https://petsymposium.org/cfp26.php +--- \ No newline at end of file diff --git a/images/pets-badge-artifact-2020.png b/images/pets-badge-artifact-2020.png new file mode 100644 index 0000000..e8e21ce Binary files /dev/null and b/images/pets-badge-artifact-2020.png differ