Cs 161 project 2

• Cs 161 project 2. Weaver Fall 2019 CS 161 Computer Security Project 2 An End-to-End Encrypted File Sharing System Abstract:Wewanttodesignandimplementafilesharingsystem(likeDropbox 3. 40 bits or so). txt; Flag 3: shomil; This project may be done individually or in groups of two. To work with this option, you will need an EECS instructional account (you should have set one up in Homework 1). Next, create an EECS instructional class account for CS 161. CS 161 Project 3 . We recommend working in teams of two, since it helps to talk through many of the more challenging components of this project with a partner. Project 3 is due Friday, December 3, 11:59 PM PT. Jul 17, 2024 · CS 161 Summer 2023 Calendar; Policies; Resources. FromBytes() functions, from the Google UUID library. 2. You may work in teams of 1 or 2 students. Story. File Operations. CS 161 Fall 2022 Calendar Textbook Resources Queue Extensions Staff Policies. 8. Story; Project 2 Policies; Design Overview; Note for steps 2 & 4: These parts do not count against bandwidth CS 161: Computer Security. File modification: Every file is encrypted and authenticated using a unique pair of keys that are generated randomly. ; Complete the online Golang Tutorial. Slides; Recording; Ch. CS 161 Project 2 Story. UUID stands for Universal Unique Identifier, and is a unique 16-byte (128-bit) value. CS 161: Computer Security. Hash-Based Message Authentication Code (HMAC) Project 2 Sharing and Revocation In this section, you’ll design three instance methods to support sharing files with other users and revoking file access from other users. You signed in with another tab or window. The backend for this project exclusively uses single quotes for SQL queries. Contribute to brandonkho/cs161 development by creating an account on GitHub. In this project, you will apply the cryptographic primitives introduced in class to design and implement the client application for a secure file sharing system. 0: September 25, 2017 Introduction Storing les on a server and sharing them with friends and collaborators is very useful. CS 161 Fall 2024 Instructor: David Wagner / Lecture: 9:30-11AM Tu & Th, Hearst Annex A1 [Zoom, Playlist] Project 2 Spec Quiz (due 09/27) Thu Sep 26: 9 Project 2 Page 7 of 21 CS 161 – SP 19 2. You should strive to write clean, secure code. Go will automatically retrieve the dependencies defined in go. To do so, visit the EECS web account page, click “Login using your Berkeley CalNet ID,” then find the cs161 row and click “Get a new account. you should probably say who you took 61b with as Hug vs Hilfinger projects can vary a lot wrt difficulty. Getting Started; General Tips; Flag 1: dev; Flag 2: ip. Instructors: Raluca Ada Popa and Peyrin Kao Lecture: Project 2 Design. CS 161 Summer 2023 Calendar; Policies; Project 2. Logistics: Team size: Up to two students. It is expected that some tests will fail because you have not yet implemented all of the required functions. A Password-Based Key Derivation Function (PBKDF) is an appropriate way to deterministically derive a cryptographic key from a password/passphrase that has at least a moderate level of entropy (e. The adversary can view and record the content and metadata of all requests (set/get/delete) to the Datastore API . 22; Ch View proj2_design_draft. Skip to current week Option 2: Hive Setup . Hive Machine Setup; Staff; Project 1. Story; Project 2 Policies; Design Overview CS 161: Computer Security. During summer sessions, we still are not in charge of enrollment, however, this restriction is lifted and enrollment is open to non-majors. If the provided ciphertext is less than the length of one cipher block, then SymDec will panic. com The Project 2 - Starter Code defines 8 functions in proj2. Story; Project 2 Policies; Design Overview; Relevant lectures: 2 - x86 Assembly and Call Stack, 3 - Memory CS Computer 编程辅导, Code Help, WeChat: powcoder, CS tutor, powcoder@163. Project 1: Exploiting Memory Safety Vulnerabilities In this project, you will be exploiting a series of vulnerable programs on a virtual machine. CS 161 Fall 2023 Course Calendar Skip to current week. REGULUS - [REGU]lated [LU]nar [S]torage; 6. 2 Autograded Code . Alternatively, you may choose to run the vulnerable server on the Hive machines. Welcome to r/neurology home of science-based neurology for physicians, neuroscientists, and fans of neurology. A Secure File Sharing System Table of contents. 5 Password hashing function Password hashing functions, also known as password key derivation functions, are commonly used to You signed in with another tab or window. I’ll also note that project 1 and project 3 are different from typical cs projects because you’re not really coding anything but rather applying security exploits. g. Each group must submit writeup–two pages maximum, please. 4. Instead, the distribution looks more like a typical CS 161 exam curve. In particular, you will be implementing the following 8 functions: InitUser : Given a new username and password, create a new user. Reload to refresh your session. Project Description The project implements an end-to-end encrypted file sharing system, supporting user authentication, secure file storage, efficient file appending, and secure file sharing with controlled access and revocation. Library Functions. Using these resources and your knowledge of computer security, you will design a secure client application that satisfies all of the Design Requirements . Install Golang v1. In this project, you will be exploiting a series of vulnerable programs on a virtual machine. Getting Started; Project 2 and Project 2 Design Review slots have been The Project 2 - Starter Code defines 8 functions in client. . This part of the project can be done with one partner. Grading and Deliverables 1. Topics include multiple sclerosis, seizures/epilepsy, stroke, peripheral neurology, anatomy of the brain and nerves, parkinson's disease, huntington's disease, syncope, medical treatments, ALS, carpal tunnel syndrome, vertigo, migraines, cluster headaches, and more. /exploit accounts for this by running multiple times (which could take some time). CS 161 Home An End-to-End Encrypted File Sharing System In this project, you will apply the cryptographic primitives introduced in class to design and implement the client application for a secure file sharing system. CS 161 Spring 2018 Project 2: Secure File Store Please see the instructions and online documentation . This project has a story component. . Users can have multiple active user sessions at once. This option not is recommended if you do not have a stable Internet connection. Part 1 Computer Security at UC Berkeley. Follow these steps to get started with the coding portion of Project 2. CS 161 Spring 2022 Calendar Textbook Resources Queue Extensions Staff Policies Unformatted text preview: Paxson Spring 2011 CS 161 Computer Security Project 2 Due Thursday May 5 11 59pm Updated 22Apr11 We linked the two Bro scripts at the end of Section 2 Thus far they were only available in the VM at root bro scripts 1 Background Huge Big Dairy is a farming and poultry conglomerate run out of Madison Wisconsin They pride themselves on their yogurts brie cheeses and Computer Security at UC Berkeley. Grading & Deliverables . Below is an example of a Project 2 score distribution from a previous semester. Part 1: A simple, but secure client You may focus rst on Part 1 and start later parts only after you’ve completed Part 1. 17 or newer. It doesn’t look like our usual project distributions (where most people get full credit). com - powcoder/CS-161-Computer-Security-Project-2 Accept the Project 2 GitHub Classroom Invite Link for Spring 2022. CS 161 Computer Security Project 3 Part 2 Due: May 3, 2020 Most recent update: April 22, 2020 In the second part of this project, you will design and implement a secure version of the vulnerable website from part 1. go. For example, SELECT 1, 'foo', 'evan' will return a single row with 3 columns, with values of 1 , 'foo' and 'evan' . Your client application must implement the eight functions defined in the Client Application API. 2 UUID . Thanks for a great semester! Project 2 design doc due (11:59pm PT) Network Security III: Wed 07/22: Generate a 256-byte RSA key pair for public-key encryption. For each step, think about what data structures are used, and what is being stored and where. Computer Security at UC Berkeley CS 161 Computer Security Project 2 Project Due: October 13th, 2017, 11:59PM Version 1. Low-Level Network Attacks 2. If you’re working with a partner, only one partner should create a team - the other partner should join the team through the list of teams. Wed 10/12: 14. With that said, 161 is probably the best upper div CS class to pair with, as it has an overall lighter workload than any other CS class I know of. First, SSH into any one of the Hive machines. Teams may have no more than 2 members total. The Project 1 Checkpoint (Q1–Q4, no write-up) are due this Friday, June 30 at 11:59 PM PT. Date Lecture Discussion HW Project 2 (due Sunday 11/03) Wed Oct 25: 18. Announcements Show/hide past announcements. It is possible to select constants in SQL rather than selecting column names. User prompted to enter a personal ID i. In this project, you will be designing a system that allows users to securely store and share files in the presence of attackers. Just watch out for project 2 in 161, as that's the one part of that class that takes a lot of effort. Date Lecture Discussion HW For this project, you may either work alone, or in a team of two. For example, Bob and Alice can each run the client application on their own devices at the same time. Before you start writing any code for this project, we’d like you to create a design plan for each feature, and convince yourself that your design meets all requirements outlined in this spec. Please see the links for the requirements of each deliverable. It opened my eyes to a lot of security vulnerabilities and even improved how I approach my own personal security (security keys anyone?). Sharing and Revocation. Table of contents. Story This project has a story component, denoted in blue boxes. But 161 projects are super chill and massively overhyped in difficulty. 3. Mon 03/13: Midterm (7–9pm PT) Cookies and CSRF (solutions) 7. Project 2. Summarize the design of your system. There are no page limits on the assignment, but less than two pages are enough to cover everything you need. 75 points for each flag). The implementation of this method must satisfy the append efficiency requirement. UUID Recall that in the name-value pairs of Datastore, the name should be a UUID. Explain the major design choices you made, written in a manner such that an average 161 student could take it, re-implement your client, and achieve a grade similar to yours. projects woooo. In the root of the repository, run: go test. Grading and Deliverables For this project, you may either work alone, or in a team of two. Imagine something like Dropbox, but secured with cryptography so that the server cannot see your data or tamper with it. Consider that enabling ASLR means you may end up with a nondeterministic solution. CS 161 Computer Security Project 2 An End-to-End Encrypted File Sharing System CS161 Spring 2020 Project 2 Created Date: 20200714195901Z Project 2. The Datastore accepts a UUID (a unique identifier) as the key to its key-value storage. Please feel free to request an extension if you are encountering any difficulties in or out of CS 161. 2 User Sessions The client application MUST allow many different users to use the application at the same time. Announcements: Homework 7 is due Friday, December 3, 11:59 PM PT. The tutorial can take quite a bit of time to complete, so plan accordingly. Gradescope submission Do not forget that your design must satisfy all requirements, including: . Users And User Authentication. How to Sign In as a SPA. Tue 07/12: No lecture (Midterm) Wed 07/13: Slides Recording; 18 CS 161 Home An End-to-End Encrypted File Sharing System In this project, you will apply the cryptographic primitives introduced in class to design and implement the client application for a secure file sharing system. mod and run the tests defined in proj2_test. Section 2: Security Analysis for Potential Threats 1. Instructors: Raluca Ada Popa and Nicholas Weaver Lecture: Monday, Wednesday, Friday, 10:00 AM–11:00 AM PT, 100 Lewis and online. To sign in to a Special Purpose Account (SPA) via a list, add a "+" to your CalNet ID (e. Project 2 Design. Enter a team name. Imagine something like Dropbox, but secured with cryptography so that the server cannot see or tamper your data. ” Be sure to take note of the account login and password. Getting Started; Customizing; Project 1 has been released Considering project 2 requires probably 30-50 hours compared to the ~6 for project 1 and ~4 for project 3, I think there could be a better balance especially when each is weighted equally. [continued from Project 1] Your satellite hacking adventures have convinced you that the Jupiter Orbiter project must be stopped…but how? Luckily for you, EvanBot has called on an expert for advice: CodaBot, an old friend of EvanBot and a CSA architect who previously worked on the Venus impactor. CS 161 Spring 2021 Calendar Staff Policies Resources Queue Extensions Exam Logistics. Getting Started Coding . An End-to-End Encrypted File Sharing System. Computer Security at UC Berkeley Accept the Project 2 GitHub Classroom Invite Link (available on Piazza). CS 161 Computer Security Project 2 An End-to-End Encrypted File Sharing System CS161 Spring 2020 Project 2 Created Date: 3/15/2020 11:07:32 PM 3. Commercial services like Dropbox or Google Drive are popular examples of a le store service (with convenient lesystem interfaces). REGULUS - [REGU]lated [LU]nar [S]torage CS 161 Home 1. Saransh Rakshak CS161 Project 2 Section 1: System Design 1. Jul 17, 2023 · Below is an example of a Project 2 score distribution from a previous semester. Reading it is not necessary for project completion. 1. Wk. At this step, you may receive an email asking you to join the cs161-students organization. To do this, you will use the uuid. Length: maximum 2 pages, plus an optional third page for a diagram. Project 2 Policies. go that you must implement (see Grading and Deliverables). Project 2 is worth a total of 150 points broken down as follows. The next screen will show a drop-down list of all the SPAs you have permission to acc 1. 2 Autograded Code CS 161 (Nicholas Weaver): Rating: 9/10 Workload: ~4-5 hr/week, ~15hr/week when project 2 was being implemented Pros: I found the content very interesting. Jul 5, 2024 · Below is an example of a Project 2 score distribution from a previous semester. pdf from COG SCI C100 at University of California, Berkeley. Follow general Python best practices. You may work with a single partner on Project 2. I never took 188 but from what I hear the project load is about the same or slightly easier than 161. Our extension form is now up. CS 161 Summer 2024 Instructors : Ashley Chiu, Jordan Schwartz, Peyrin Kao / Lecture : 12:30-2PM MTWTh, Hearst Annex A1 [ Zoom , Playlist ] Course Calendar CS 161 Summer 2023 Calendar; Policies; Project 1; Question 6: Antares; Antares (Launched 2001) Step 2: Quick Format String Review Apr 16, 2024 · During fall and spring semesters we have to follow the department’s enrollment policies, which restricts CS 161 enrollment to declared L&S Computer Science or College of Engineering majors only. Design Overview. However, I still think that project 3 should be on the lighter side given that it ends up being close to finals week. Project 2 Page 4 of 17 CS 161 { Sp 18. In this project, you will design and implement a secure file sharing system in Go. Announcements: Final grades are posted. CS 161 Computer Security. Jun 20, 2023 · Homework 2 has been released on Gradescope and is due Friday, June 30th at 11:59 PM PT. Hash Function; 6. If you’d like, you can think of this assignment as a long take-home exam. Your implementation of these 8 functions should satisfy all of the Design Requirements. During your presentation, you can consider the following story and answer the questions. The final design document will be graded on effort and completion. 1 Datastore Adversary The Datastore is an untrusted service hosted on a server and network controlled by an adversary. Using these resources and your knowledge of computer security, you will design a secure client application that satisfies all of the Design Requirements. New() and uuid. Due: Friday, March 19th before 11:59pm PT (extended from March 12th) [10 points] Design Document - Draft. Project 2 is worth a total of 150 points, broken down as follows: This repository contains my work for CS161 Project 2 at UC Berkeley, Spring 2023. Computer Security at UC Berkeley Project 2 is the longest but you get adequate time to do it. Clone the Project 2 - Starter Code repoistory. If you have questions about or find errors in this documentation, please post on Piazza. XSS and UI Attacks. 1 Design Presentation . CS 161 Project 2 . 4 Design Document . The world dreams once again. Advice and Tips. Parameters key ([]byte) - a 16-byte symmetric key for decryption This part of the project enables both stack canaries and ASLR. , "+mycalnetid"), then enter your passphrase. You signed out in another tab or window. You switched accounts on another tab or window. 3. 70 points for finding exploits (8. CS 161 Fall 2023 Calendar; Policies; Resources. Looks up the provided name and deletes the corresponding value, if it exists. Customizing Caltopian intelligence secured a copy of Gobian Union's Satellite Provisioning And Control Environment [SPACE] during the disarray following their fall. Past Course Websites Spring 2023 (Peyrin, Popa) Spring 2022 (Weaver) Summer 2022 (Fuzail, Peyrin) Do not forget that your design must satisfy all requirements, including: . For each of flags 3–8 only, include a brief description (2–3 sentences) of how you acquired the flag, and a suggestion (a line of code or 2–3 sentences) for how to protect against your exploit. Project 1 Customizing Caltopian intelligence secured a copy of Gobian Union's Satellite Provisioning And Control Environment [SPACE] during the disarray following their fall. CS 161: Computer Security Project 2 Walkthrough + Ask Nick Anything: Fri 04/30: CS 161: Computer Security. Create User a. Digital Signatures; 6. We want you to actively get your hands dirty designing and implementing your system. Oct 28, 2022 · 1. Like any techinical writing, your design document needs to be clean and well formatted. Computer Security at UC Berkeley. Hive Machine Setup; Spring 2024 FAQs; Staff; Project 1. Imagine something similar to Dropbox, but secured with cryptography so that the server cannot view or tamper with your data. This Decrypt the ciphertext using the 16-byte key. For this project, you can work in teams of up to 2 people. The only way to gain any information about a file, including the filename itself, is through the user structure, which can only be accessed if one See full list on github. Breaching a Vulnerable Web Server In this project, you will exploit a poorly designed website. One of us particularly likes the Hitchhiker’s Guide to Python, which has a good section on Python Style. Story; Project 2 Policies; Design Overview; Library Functions; CS 161 Spring 2024 Course Calendar Skip to current week. kbndcct rjqono ghryb aocq kglwp vgwula cjload mrhpdm oyai ukzpgku