| safarisucks | |
| SafariSucks | |
| safarisucks | |
| SafariSucks | |
| safarisucks | |
| safari sucks |
| # -*- mode: python; -*- | |
| # Copyright 2009 Google Inc. | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 | |
| # | |
| # Unless required by applicable law or agreed to in writing, software |
| acedy/decay | |
| adustion/sudation | |
| aedility/ideality | |
| agentive/negative | |
| agral/argal | |
| agrestic/ergastic | |
| alerce/relace | |
| allegate/ellagate | |
| ammine/immane | |
| annite/innate |
| # From http://oinksoft.com/static/closure-tools/Makefile.example | |
| # This is an example Makefile for a project that uses all of the Closure | |
| # Tools: Compiler, Library, Templates, Stylesheets, and Linter. | |
| # | |
| # `make deps`: Download and build all dependencies (compiler, etc.). | |
| # | |
| # `make`: Compile the project for development (does not use Closure | |
| # Stylesheet map $(CSS_MAP), uses compilation flags that should be | |
| # good for development). | |
| # |
| takeoff | |
| go forward 10 feet | |
| faster | |
| move back | |
| stop | |
| spin left | |
| faster | |
| faster | |
| slower | |
| spin right |
| what is the best way to 113 | |
| what do i need to know 88 | |
| should i stay or should i 82 | |
| i stay or should i go 80 | |
| how do i get rid of 79 | |
| what is the name of this 69 | |
| i do not want to be 63 | |
| is there such a thing as 48 | |
| what should i do with my 45 | |
| i do not know how to 34 |
| 88 0110000101101100011000010110111000100000011101000111010101110010011010010110111001100111 | |
| 66 eventhoughmostofthedinosaursinitareactuallyfromthecretaceousperiod | |
| 62 noonereallyneedstotypeasinglewordthatsoverthirtycharactersorso | |
| 58 llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch | |
| 57 bustergophechiduckneaealcockidgeoverwingailusharkolanbler | |
| 55 diddiewadiddiewahdittywahdiddydowahdiddydiddydumdiddydo | |
| 55 cheezborgercheezborgercheezborgercheezborgercheezborger | |
| 54 trustustrustustrustustrustustrustustrustustrustustrust | |
| 53 aciiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiid | |
| 52 gbggbbggbbbggbbbbggbbbbbggbbbbbbggbhbbhbggbbhbbbhbgg |
Red Team versus the Agents
At a nuclear weapons lab, a team of elite hackers matches wits with undefeated autonomous defenders
ALBUQUERQUE, N.M.--By the time my escort steers me past the armed guards, key-coded doors, and bags of shredded paper into the heart of Sandia National Laboratories, the rematch has already begun. Inside the Advanced Information Systems Lab, six men sit around a large table loaded with laptops and network cables, which snake over to a rack of high-powered machines labeled BORG SERVER CLUSTER. These men are the defense--the Blue Team in this high-tech version of capture the flag--and they lean back in their chairs confidently. This past March, they claim, their "agents"--computer programs that autonomously cooperate to protect a networked system--became the first defenders ever to thwart Sandia's esteemed Red Team of professional hackers. But that was in a two-day skirmish. Now Steven Y. Goldsmith, the research group's lead scientist, has invited the Red Team to spend this entire we