Post Description
Zeroday.Scene.Rules.v2010.1-RULES
Dit zijn de nieuwste 0day scene rules die vanaf nu in de scene van toepassing zijn. Dit is bedoeld voor de geinteresseerde mensen, je kunt er verder niks mee in principe. ;)
Informatie uit het .nfo bestand:
This is intended as an addendum to the existing 0day rules. All the old rules
are still valid, unless they have been altered or updated by this addendum.
The 0day scene has gone through major changes in this decade. As technologies
have changed, so have we, but our adaptations have left many grey areas in the
current rules. The last rules update was years ago when programs were much
smaller and transfer speeds much lower. The existing 0day rules did not address
problems of software encountered today, simply because at that date it did not
exist. These changes have led to a series of loopholes which groups have been
taking advantage of. The new rules we constructed aim to close these loopholes,
as well as increase the general quality level of releases in the scene.
This document covers a new ruleset for 0day. These rules and guidelines are
intended for release-groups in the first place, and sites secondary. We hope
that in time many sites will take over the majority of these rules. The
following groups have signed and committed to following these rules:
ACME AiR AGAiN ALiAS ARN BACKLASH BEAN BLiZZARD BRD CORE CRD
CROSSFiRE DIGERATI DVT EMBRACE FALLEN FAS iNViSiBLE LND
MESMERiZE NGEN NULL ORiON OUTLAWS RiTUEL ROGUE rG
RAiN SHOCK SSG TBE TE UNLEASHED VACE ZWT
This particular 2010.1 revision was created to address a number of unclear bits
in the original release. Although we do appreciate constructive criticism, we
would like to point out that these rules were not created by an individual, and
as such they are not trivial to construct. With this new revision we hope to
clarify the rules to match our intentions when we released them. If you did not
get the rules you want, please remember that this was a combined effort from a
large number of groups, where the opinion of the collective supersedes that of
any single group.
These rules will go into effect starting January 31st, 2010.
When a rule is described as *should*, we interpret this as follows: you are
expected to follow the rule, if you do not, groups are free to proper your
release. If it is not propered however, you will not get nuked.
When a rule is described as *must*, there is no compromise, you either follow
the rule or you get nuked.
Comments # 0