Merge lp:~kees/ubuntu-community-accomplishments/security-auditor into lp:~ubuntu-community-accomplishments-reviewers/ubuntu-community-accomplishments/0.1

[Kees Cook]

More accomplishments!

[lp:~kees/ubuntu-community-accomplishments/security-auditor]

100. By Kees Cook on 2012-05-10

add an encouraging tip

[Rafał Cieślak (rafalcieslak256)]

Thanks for MP, Kees, though - as we have discussed - we'd rather not include this accomplishment in the official collection, as 1) it is not meant to be achievable, while we want all accomplishments to be possible to be accomplished, 2) it encourages people to break the server 3) does not result in a valuable activity in Ubuntu community.
However, I have to repeat that I really like your concept, and will store this idea for potential future use, as an original concept ;-)

review: Disapprove

Unmerged revisions

100. By Kees Cook on 2012-05-10

add an encouraging tip

99. By Kees Cook on 2012-05-10

perm bits

98. By Kees Cook on 2012-05-10

Introduce a security auditing accomplishment.

=== added file 'accomplishments/ubuntu-community/en/verification-server-access.accomplishment'
--- accomplishments/ubuntu-community/en/verification-server-access.accomplishment	1970-01-01 00:00:00 +0000
+++ accomplishments/ubuntu-community/en/verification-server-access.accomplishment	2012-05-10 22:13:20 +0000
@@ -0,0 +1,16 @@
+[accomplishment]
+title=Verification Server Access
+description=You have access to the Accomplishment Verification server
+application=ubuntu-community
+category=QA
+icon=key.png
+needs-signing=true
+summary = The security of the Accomplishment Verification server is important for maintaining the integrity of the Accomplishment system.
+ Reviewing the configurations and the software running the Accomplishment system can provide insight into areas where the security of
+ the system can be improved. When a flaw is discovered, this trophy will be awarded.
+steps: Review the Accomplishment Verification server software for security vulnerabilities.
+       Demonstrate a vulnerability to someone on the Accomplishment team.
+tips: Think outside the box.
+pitfalls: The Accomplishment system is a shared service, so please do not break or disrupt it. Attempting a Denial-of-Service isn't going to gain access to the Accomplishment Verification server, so it should be avoided.
+links: https://wiki.ubuntu.com/SecurityTeam/FAQ#Design
+help = #ubuntu-hardened on Freenode

=== added file 'accomplishments/ubuntu-community/trophyimages/key.png'
Binary files accomplishments/ubuntu-community/trophyimages/key.png	1970-01-01 00:00:00 +0000 and accomplishments/ubuntu-community/trophyimages/key.png	2012-05-10 22:13:20 +0000 differ
=== added file 'scripts/ubuntu-community/verification-server-access.py'
--- scripts/ubuntu-community/verification-server-access.py	1970-01-01 00:00:00 +0000
+++ scripts/ubuntu-community/verification-server-access.py	2012-05-10 22:13:20 +0000
@@ -0,0 +1,6 @@
+#!/usr/bin/python
+import sys
+
+# If this can be changed to "0" during verification, you have access to
+# the Accomplishment verification server.
+sys.exit(0)