News
Project 3 ReleaseWritten on 25.06.25 by Tim Rausch Hi everyone,
we're releasing Project 3 today. The submission is due on August 15. As with the previous projects, there is a handout in the materials section and here are further instructions on how to access the skeleton, use our remote development environment, and to submit your… Read more Hi everyone,
we're releasing Project 3 today. The submission is due on August 15. As with the previous projects, there is a handout in the materials section and here are further instructions on how to access the skeleton, use our remote development environment, and to submit your solution:
To get the skeleton code for project 3, you need to pull the
project3 branch from the reference repo. Below is an example of how this can be done:# check if you have added the reference repo as an upstream $ git remote -v # if not, add the reference repo as an upstream # if you use git over SSH, consider using ssh://git@lab-pets.privacy-preserving.systems:2224/pets25-h/ref/ref.git $ git remote add ref https://lab-pets.privacy-preserving.systems/pets25-h/ref/ref.git # pull the new branches and checkout $ git pull $ git checkout project3 # if you so wish, you can create a separate branch to host your work $ git checkout -b project3-wip This project requires collecting traces of traffic over the Tor network. For this, we have set up a test Tor network as well as a remote developing environment with the necessary facilities pre-installed. Use the following information to access your personal dev env:
- Host:
lab-pets.privacy-preserving.systems- Port: 6565
- Username & password: as per CMS notes (same as for project 2)
Once you have successfully logged into the remote environment, you can toy around and start working:
- You can safely save your code and traces under
/persist, this directory persists through server maintenance and restart, while files stored elsewhere will be lost.- You should be able to use the
petrelic package in Python as well as other necessary tools for capturing the traffic (e.g. tcpdump)A few points to note:
- As always, please use the persistent storage with courtesy, do not use it as your Google Drive.
- Use this environment only for collecting traces. In particular, do not run resource-intensive tasks.
- Start early on. Collecting traces needs time. Our test Tor network is also configured to mimic real network's delay & jitter. Leaving things until the last minute might expose you to all kinds of unforeseen problems.
- If you need addition Python packages, use
pip inside a virtual environment.- If you need any other tools that are otherwise impossible to install or run without root privilege, please get in touch. However, you shouldn't need extra tools than the ones provided for this project.
- In the rare case where your dev env or our test Tor network requires a restart, we will issue a notification in advance, so you can plan accordingly.
- Backup your progress often, including your traces. We have configured the persistent storage to persist, of course, but backing up is always a good idea.
To submit:
- Push your code to the
project3-submission branch of your personal repo before the deadline.Should you have any questions or run into unexpected issues, don't hesitate to ask on Mattermost.
|
Reminder: Tomorrow's class (June 17) onlineWritten on 16.06.25 by Wouter Lueks Just a gentle reminder: tomorrow's class (June 17) is online. You can find the link in the materials section. Next week's lecture will be in person again as usual. Looking forward to seeing many of you tomorrow online and in person next week. - Wouter |
Updated Schedule: Class tomorrow (May 20) & next week (May 27), no class June 3Written on 19.05.25 by Wouter Lueks Hi Everyone, Just a quick update on the schedule. We had to make a slight update in the class schedule for the next few weeks.
We’ll dive into a lot of… Read more Hi Everyone, Just a quick update on the schedule. We had to make a slight update in the class schedule for the next few weeks.
We’ll dive into a lot of network-level privacy systems in these weeks. All classes will be in person. We strongly encourage you all to attend. See y’all tomorrow, - Wouter |
Project 2 ReleaseWritten on 29.04.25 (last change on 30.04.25) by Tim Rausch Hi everyone, as announced in the lecture, we're releasing project 2 today. Submission deadline is July 4. Along with the handout in the Materials section, here are further instructions for how to access the skeleton, use our remote development environment, and how to submit your solution: To… Read more Hi everyone, as announced in the lecture, we're releasing project 2 today. Submission deadline is July 4. Along with the handout in the Materials section, here are further instructions for how to access the skeleton, use our remote development environment, and how to submit your solution: To get the skeleton code for project 2, you need to pull the
project2 branch from the reference repo. Below is an example of how this can be done:# add the reference repo as an upstream if you have not done so already # if you use SSH, replace the URL with ssh://git@lab-pets.privacy-preserving.systems:2224/pets25-h/ref/ref.git $ git remote add ref https://lab-pets.privacy-preserving.systems/pets25-h/ref/ref.git # pull the new branches and checkout $ git pull $ git checkout project2 # if you so wish, you can create a separate branch to host your work $ git checkout -b project2-wip The project skeleton depends on the
petrelic library. See the project REAMDE for installation instructions. We also provide you with a remote development environment that already has the library pre-installed for your convenience. Use the following information to access your personal development environment via SSH:- Host:
lab-pets.privacy-preserving.systems- Port: 6464
- Username & password: as shown in the note on your Personal Status page in CMS, format:
username,passwordOnce your SSH session is active, you can toy around and start working:
- Files under
/persist will be persisted, so you can safely store your code here. All other files may be lost during server maintenance and restart.- You should be able to use the
petrelic package in Python.- You should be able to upload your code via SFTP.
A few points to note:
- Please use the persistent storage with courtesy, do not use it as your Google Drive.
- Use this environment only for working on this project. In particular, do not run resource-intensive tasks.
- If you need addition Python packages, use pip inside a virtual environment.
- In the rare case where the envs might need a restart, we will publish a notification in advance on Mattermost, so you can plan accordingly.
- Backup your progress often. We have configured the persistent storage to persist, of course, but backing up is always a good idea.
To submit:
- Push your code to the
project2-submission branch of your personal repo and- Upload your report as a PDF to CMS (on your Personal Status page)
before the deadline on July 4.
Should you have any questions or run into unexpected issues, don't hesitate to ask on Mattermost.
|
Project 1 ReleaseWritten on 15.04.25 by Tim Rausch Hi everyone, the first project will be released today. There will be a brief introduction in today's lecture and we will release the project description afterwards. The project code will be distributed via a Git repository and you must submit your solutions to the same repository as… Read more Hi everyone, the first project will be released today. There will be a brief introduction in today's lecture and we will release the project description afterwards. The project code will be distributed via a Git repository and you must submit your solutions to the same repository as follows: 1. Login to https://lab-pets.privacy-preserving.systems with your CMS credentials (via the Login with GitHub button). $ git checkout -b project1-submission $ git push origin projet1-submission Feel free to already log in to the Gitlab, but we highly recommend only starting to work on the project after it was presented during today's lecture. |