Adding PETS (2020-2026)

_conferences/pets.md

@@ -0,0 +1,17 @@
+---
+title: PETS
+custom_css: pets-badges
+---
+
+The annual Privacy Enhancing Technologies Symposium (PETS) introduced artifact
+evaluation in 2020.
+
+### Overview of changes
+
+- 2025: switch to <a class="pets-artifact-badge">Artifact: Available</a>, <a class="pets-artifact-badge">Artifact: Functional</a>, and  <a class="pets-artifact-badge">Artifact: Reproduced</a> badges introduction of Artifact Award
+  Runner-ups, introduction of Distinguished Artifact Reviewers
+- 2024: switch to <a class="pets-artifact-badge">Artifact: Available</a> and <a class="pets-artifact-badge">Artifact: Reproduced</a> badges
+- 2022: introduction of Artifact Award
+- 2020: introduction of a single <img src ="{{ site.baseurl }}/images/pets-badge-artifact-2020.png" alt="artifact"> badge
+
+For more details, refer to the respective call for artifacts.

_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.

_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.

_conferences/pets2020/organizers.md

@@ -0,0 +1,5 @@
+---
+title: Organizers
+order: 20
+redirect_to: https://petsymposium.org/cfp20.php
+---

_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 <a href="https://petsymposium.org/popets/2020/">PETS 2020 proceedings</a>.
+
+<table>
+  <thead>
+    <tr>
+      <th>Title</th>
+      <th>Artifact URL</th>
+    </tr>
+  </thead>
+  <tbody>
+  {% for artifact in page.artifacts %}
+    <tr>
+      <td>
+        {% if artifact.paper_url %}
+          <a href="{{artifact.paper_url}}">{{artifact.title}}</a>
+        {% else %}
+          {{ artifact.title }}
+        {% endif %}
+      </td>
+      <td>
+        {% if artifact.artifact_url %}
+          <a href="{{artifact.artifact_url}}"><img src ="{{ site.baseurl }}/images/pets-badge-artifact-2020.png" alt="artifact"></a>
+        {% endif %}
+      </td>
+    </tr>
+  {% endfor %}
+  </tbody>
+</table>

_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.

_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.

_conferences/pets2021/organizers.md

@@ -0,0 +1,5 @@
+---
+title: Organizers
+order: 20
+redirect_to: https://petsymposium.org/cfp21.php
+---