+-----------------------------------------------------------------------------------------------------+
Ś OFFiCiAL.NULLED.SCRiPT.RULES.2010-DRAFT2 Ś
Ś Ś
+-----------------------------------------------------------------------------------------------------+
+-----------------------------------------------------------------------------------------------------+
Ś Requirements: Notepad with terminal font or any other ascii viewer. Ś
+-----------------------------------------------------------------------------------------------------Ś
Ś Date: 04.05.2010 - 20:00 GMT+1 Ś
+-----------------------------------------------------------------------------------------------------+
Ś To all 0Day groups that are interested: This ruleset is only a draft
Ś if someone wants to fix something, or add a rule then you can
Ś reach us under our email adress (on the bottom of this NFO)
Ś
Ś If no one reacts to this Ruleset until 10.05.2010 (DD.MM.YYYY) we will pre it 1:1 as final.
Ś
Ś PS: Help at translating in other languages (ES/FR i.e.) is always wanted.
+-----------------------------------------------------------------------------------------------------+
Ś
Ś-ENGLiSH-
Ś
ŚiNDEX:
Ś 0: General Rules
Ś 1: Packaging / NFO
Ś 1.1: Examples
Ś 1.2: NFO
Ś 2: Naming
Ś 2.1: Themes/Addons
Ś 2.2: Updates
Ś 3: NULLiNG Rules
Ś 3.1: KEYGEN Rules
Ś 4: NUKE RULES / REASONS
Ś
Ś Prolog:
Ś Since the last PHP Nulling group faded away long time ago there were no rules for PHP scripts...
Ś So we decided to write new ones so that we, and other groups, can start releasing scripts
Ś with a basic ruleset that provides help at cracking and releasing.
Ś
Ś In general the actual 0Day Rules apply for all not discussed themes.
Ś
+-----------------------------------------------------------------------------------------------------+
Ś
Ś 0. General Rules
Ś -NULLED dupes KEYGEN -NOT- (and vice versa), both has good sides.
Ś because of this there are 2 releases per script allowed (excluding PROPER/REPACK etc.)
Ś -BETA/ALPHAs need no INTERNAL tagging
Ś -CRACK.ONLY / KEYGEN.ONLY / KEYFiLEMAKER.ONLY is only allowed if the software
Ś (i.e. as Full, Unlockable Demo version)
Ś is downloadable for free and without registration at the manufacturers website
Ś Usualy it is better to include the files for Archive reasons, and because it does not
Ś dupe NULLED anyway.
Ś -On-the-Fly Patches are allowed if the script needs a system variable (ID i.e.)
Ś to work, but Pre-Patched (to all IDs for example) is preffered over that.
Ś
Ś This has to be tagged in the following format:
Ś
Ś
+-----------------------------------------------------------------------------------------------------+
Ś
Ś 1. Packaging
Ś -Standard 0Day Packing, Filenames max. 8.3 Characters (Name.typ - 12345678.123)
Ś Releases are needed to be RARed - Compression is allowed but not mandatory.
Ś Each ZIP should be 5000000 Bytes (5Mb).
Ś Therefore the size per RAR is around the same.
Ś Bigger filesizes are allowed, look at actual 0Day Rules.
Ś
Ś
Ś 1.1: Example
Ś 12 Files - 26Mb
Ś -5x 5Mb RAR + 1x 1Mb RAR -> grprls.rXX
Ś (The RARs can also be only named .rXX)
Ś --Each RAR in a ZIP
Ś --5x 5Mb ZIP + 1x 1Mb ZIP -> grprls.zip
Ś (The actual naming is the groups decision (a|b or 001|002, 01|02, 1|2) )
Ś
Ś Each ZIP needs to include:
Ś xxxx.rXX - file_id.diz - .nfo
Ś
Ś Wrong naming of RARs/ZIPs is no Nuke reason, unless some other reason applys to:
Ś (dupe.filenames, special.chars u.a.)
Ś
Ś
Ś 1.2: NFO
Ś The NFO needs to contain:
Ś -Release Date
Ś -Size (or Diskcount)
Ś -Developer Website
Ś -Version
Ś -Short description (Copy & paste)
Ś -Languages (if MULTi)
Ś -Short usage description
Ś
Ś In the NFO wanted is:
Ś -Price (Currency does not matter - Copy from website)
Ś
+-----------------------------------------------------------------------------------------------------+
Ś
Ś 2: Naming
Ś Naming under following scheme:
Ś <> = needed | [] = additional
Ś Language tag is only needed on non-english only Releases.
Ś For the rare case that only 2 languages are available
Ś it has to be tagged BiLiNGUAL.
Ś
Ś .[Edition].v.[Language|MULTi|BiLiNGUAL].
Ś .
Ś [Beta|Alpha|RETAIL|REAL].[iNTERNAL|iNT|DiRFiX|NFOFiX|PROPER|REPACK|READ.NFO].
Ś -GRP
Ś
Ś Examples (fictional):
Ś
Ś Vbulletin.v5.1.NULLED.PHP-GRP = Vbulletin 5.1 English, Nulled
Ś Vbulletin.v5.1.KEYGEN.ONLY.PHP-GRP = Vbulletin 5.1 English, Keygen Only
Ś Vbulletin.v5.1b3.NULLED.BETA.iNTERNAL.PHP-GRP = Vbulletin 5.1 Beta, English, iNTERNAL, Nulled
Ś Vbulletin.PRO.v5.1.NULLED.PHP-GRP = Vbulletin 5.1, Pro Edition, English, Nulled
Ś Vbulletin.v5.1.MULTi.incl.KEYGEN.PHP-GRP = Vbulletin 5.1, Multilanguage (Notes in NFO!), Keygen
Ś Gallerypro.v2.1.GERMAN.NULLED.ASP-GRP = Gallerypro 2.1, German, Nulled, ASP
Ś
Ś
Ś If the script is sold with no protections at all (no Callbacks or similar)
Ś then instead of NULLED/KEYGEN there shall be no tag used:
Ś Somesoftware.v1.5.PHP-GRP
Ś
Ś In this case even only decoding of protected files (Ioncube for example)
Ś is counted as NULLED.
Ś (Better for dupe searches and historical background)
Ś Releases with Key in NFO and nulled backend (no Callbacks/Security Checks)
Ś should be labeled as .NULLED.
Ś
Ś
Ś 2.1: Themes/Addons
Ś Themes/Addons for Wordpress/Joomla/Vbulletin etc.
Ś
Ś ..for...[Language|MULTi].
Ś .[Beta|Alpha|RETAIL].
Ś [iNTERNAL|DiRFiX|NFOFiX|PROPER|READ.NFO].-GRP
Ś
Ś Examples (fictional):
Ś Dark.Theme.v3.for.vBulletin.5.X.GERMAN.NULLED.PHP-GRP
Ś = Dark Theme Version 3, for Vbulletin Version 5.X, German, Nulled
Ś Sidebar.Rotation.2.for.Wordpress.2.1.incl.KEYGEN.PHP-GRP
Ś = Sidebar rotation 2 Addon for Wordpress 2.1, with Keygen
Ś
Ś 2.2.: Updates
Ś Updates are allowed 4 weeks after the last Pre
Ś (same MU rules as in 0Day Rules)
Ś
+-----------------------------------------------------------------------------------------------------+
Ś
Ś
Ś 3: NULLiNG Rules
Ś -All Callbacks need to be removed or patched
(i.e. Serial Check over Developer Server)
Ś -No Group Watermarks (also not in script comments).
Ś -If files of the release are encoded all files need to be decoded.
Ś (i.e. Ioncube, Sourceguardian, eval() etc.)
Ś
Ś 3.1: KEYGEN Rules
Ś -Keygens need to be in the same format as the Release
Ś (Release is PHP - Keygen needs to be in PHP too)
Ś -The Language of the keygen needs to be selectable on MULTi (i.e. DE,EN,PL)
Ś or the keygen needs to be completely in english.
Ś At specific releases (i.e. GERMAN) the keygen can be english or
Ś in the language of the release (in this case German)
Ś -Group comments in Keygen Sourcecodes are allowed if the group
Ś wants to explain the code, but this is in not mandatory.
Ś -Encoded Keygen code is allowed, as long is it does not use an external
Ś loader (Example: Ioncube is forbidden, eval() is allowed)
Ś -ASCii Art / Pictures are allowed but should be used thrifty.
Ś -Pictures in keygens shall not affect the code
Ś (i.e. Picture missing = Keygen not loading = Nuke/Proper reason)
Ś -Pictures need to be included and can not be mapped from websites
Ś (Security risk)
Ś
+-----------------------------------------------------------------------------------------------------+
Ś
Ś 4: NUKE and PROPER RULES / REASONS
Ś NUKEs are possible for:
Ś -bad.pack (i.e. RARs instead of ZIP) - stolen.from.[web|p2p|etc] - missing.files
Ś -bad.crack (= bad nulled) - keygen.not.working
Ś -Common Sense Nukes (dupe.filename, mislabeled.<|>, etc.)
Ś -This is NOT a complete list.
Ś
Ś PROPER/DiRFiX/REPACK follows the normal scene rules.
Ś
Ś
+-----------------------------------------------------------------------------------------------------+
Ś SiGNED: Ś
Ś YET TO BE SIGNED Ś
Ś CONTACT: contactye@hush.com
+-----------------------------------------------------------------------------------------------------+
9.5.10
OFFiCiAL.NULLED.SCRiPT.RULES.2010
Subscribe to:
Post Comments (Atom)
0 komentarze:
Post a Comment