Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 5da4a08

Browse files
committed
add screenshot
1 parent 57caf52 commit 5da4a08

File tree

3 files changed

+7
-1
lines changed

3 files changed

+7
-1
lines changed

‎README.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,12 @@
66

77
Welcome to Assignment 1 for [CS 253: Web Security](https://cs253.stanford.edu). ✨
88

9+
We're doing client-side attacks! This assignment is all about Cross Site Scripting (XSS) vulnerabilities. Your goal is to come up with "attack inputs" that when entered into websites vulnerable to cross-site scripting (XSS) attacks you are able to execute any code you want in the victim's browser.
10+
11+
The assignment takes the form of an interactive workshop that you'll run in your browser. This is what it looks like:
12+
13+
![](img/screenshot.png)
14+
915
## Prepare
1016

1117
### Get the starter code

‎exercises/00/problem.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Keep in mind when you design your attacks that you are attacking a server runnin
1818

1919
## Another note for the extra, extra devious among you
2020

21-
We haven't attempted to secure this workshop from *you*. You have all the source code and it's running on your machine, so you are able to freely examine the source code if you're curious how this workshop is designed. This means that it is possible for you to fake calls to `success()` or to modify the local state file to instantly "finish" all the challenges. I ask you to avoid trying this since it'll just make the assignments less fun for you if you read ahead. Since you have to submit your solutions in a separate text file anyway, this doesn't really help you anyway.
21+
We haven't attempted to secure this workshop from *you*. You have all the source code and it's running on your machine, so you are technically able to examine the source code. We ask you to avoid doing this since it'll just make the assignments less fun for you. It is also possible for you to fake calls to `success()` or to modify the local state file to instantly "finish" all the challenges. Again, this wouldn't be much fun for you, so please don't do it. Since you have to submit your solutions in a separate text file anyway, this doesn't really help you anyway.
2222

2323
## Let's get going!
2424

‎img/screenshot.png‎

311 KB
Loading[フレーム]

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /