-
Notifications
You must be signed in to change notification settings - Fork 164
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update link to LICENSE to point to repo, not Trac
- Loading branch information
1 parent
e47afe3
commit d3ecf8d
Showing
1 changed file
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
# Acceptable Use Policy | ||
# Acceptable Use Policy | ||
|
||
For the most part, the things that you shouldn't do aren't supported by the API. You're welcome to use our code for commercial projects, etc. Please see [our license (MIT)](https://seattle.poly.edu/browser/seattle/trunk/LICENSE.txt) for details. | ||
For the most part, the things that you shouldn't do aren't supported by the API. You're welcome to use our code for commercial projects, etc. Please see [our license (MIT)](../LICENSE) for details. | ||
|
||
Our use policy is roughly modeled on the [PlanetLab Acceptable Use Policy](http://www.planet-lab.org/aup). The main things to know are: (1) no illegal activity, (2) don't try to hack into Seattle user machines (if you want to test a vulnerability, let us know, we have machines set aside for this), and (3) even if the system doesn't have outgoing or incoming IP / port restrictions, don't abuse this. Basically, it boils down to treating the system as though you're a network admin and it's on your network. | ||
Our use policy is roughly modeled on the [PlanetLab Acceptable Use Policy](http://www.planet-lab.org/aup). The main things to know are: (1) no illegal activity, (2) don't try to hack into Seattle user machines (if you want to test a vulnerability, let us know, we have machines set aside for this), and (3) even if the system doesn't have outgoing or incoming IP / port restrictions, don't abuse this. Basically, it boils down to treating the system as though you're a network admin and it's on your network. |