αⁿ                                                                       α∙

PRESENTS

Check Point FireWall-1 v4.1 SP3 *Incl.Keymaker.and.Patch*

Φεεεεεεεεεεεεεεεεεεú πΣ ΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣ Σ

∙ µεεεεεεεεεεεεεεεεεε╛                                                      ∙

∙   [ Program ......................... Check Point FireWall-1 v4.1 SP3 ]   ∙
∙   [ Type .............. Industry-leading Enterprise Security Solution ]   ∙

∙   [ Protection ...... Screwed up Schnorr signature scheme (142 bit Q) ]   ∙
∙   [ By ...................... Check Point Software Technologies, Inc. ]   ∙
∙   [ Homepage .............................. http://www.checkpoint.com ]   ∙

∙         [ Cracked by ................................ Ivanopulo ]         ∙
∙         [ Release type ................ Incl.Keymaker.and.Patch ]         ∙
∙         [ Release date ........................... Jan 16, 2001 ]         ∙

Φεεεεεεεεεεεεεεεεεεú πΣ ΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣ Σ

∙ µεεεεεεεεεεεεεεεεεε╛                                                      ∙

∙   FireWall-1  enables  enterprises  to  define  and  enforce  a single,   ∙
∙   comprehensive  Security  Policy  that protects all network resources.   ∙
∙   Its  innovative three-tier architecture, patented Stateful Inspection   ∙
∙   Technology  and  the  Open  Platform  for  Security (OPSEC) deliver a   ∙
∙   highly  scalable  solution  that  is  able to integrate and centrally   ∙
∙   manage  all  aspects  of network security. A family of add-on modules   ∙
∙   extends  FireWall-1's  capabilities  to  all  levels  of security and   ∙
∙   management.                                                             ∙

∙   Files included in this release are:                                     ∙

∙   fw-1_41814_1_linux_des.tgz - FireWall-1 v4.1 Linux SP3                  ∙
∙   release_notes_41_sp3.pdf   - FireWall-1 v4.1 SP3 Release Notes          ∙

Φεεεεεεεεεεεεεεεεεεú πΣ ΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣ Σ

∙ µεεεεεεεεεεεεεεεεεε╛                                                      ∙

∙   Please read the information below carefully.                            ∙

∙   First  of  all  you  need  to  patch  the  files.  Please  note  that   ∙
∙   keymaker/patch  is  Win32 application, so create a directory on win32   ∙
∙   machine  and  copy your firewall-1 linux executables there. Start the   ∙
∙   keymaker.   Enter  the  path  to  copied  executables  (w/o  trailing   ∙
∙   backslash).  Hit  'Patch  it'.  The  directory  you specified will be   ∙
∙   scanned   for  files  containing  protection  routines  that  require   ∙
∙   patching.  Wait.  Wait  some more. BTW, backups of all to-be-modified   ∙
∙   files  will be created, so you can always get back to unpatched files   ∙
∙   later.  When  patching is over, you'll see the log. Now you MUST sign   ∙
∙   your cp.macro with the new key. To do it, copy your cp.macro to win32   ∙
∙   machine,  hit  'Sign it' and point to cp.macro location. My advise is   ∙
∙   to  backup  your  cp.macro  before signing it, though (just in case).   ∙
∙   Please  note  that you can add ANY FEATURES you want to cp.macro, but   ∙
∙   you'll  need  to  sign  it again each time after you've done with the   ∙
∙   changes.                                                                ∙

∙   Now the most easy part - license generation. Use default feature list   ∙
∙   provided  by  the  keymaker (I tried to include the best features) or   ∙
∙   use your own one. Enter your host IP and press 'Generate it'. Use the   ∙
∙   generated key to license FireWall-1.                                    ∙

∙   Enjoy =)                                                                ∙

∙   P.S.  For  those  who're  interested in the protection scheme used in   ∙
∙   FireWall-1  (and  for  Check Point staff lurking around), here're the   ∙
∙   details:                                                                ∙

∙   FireWall-1  uses  screwed-up  1024/142  Schnorr signature scheme. Why   ∙
∙   screwed-up?  Because  some people can't keep themselves from thinking   ∙
∙   they're  smarter  than  others.  They changed the algorithm, probably   ∙
∙   trying  to  make  it  harder to break. In fact they just dramatically   ∙
∙   DECREASED  security  of  this strong public key signature scheme with   ∙
∙   their  poor  attempt  (from  DLP  in  142-bit prime order subgroup to   ∙
∙   bruteforcing  just  2^64  variants,  which  is  possible  to do). The   ∙
∙   problem  is  that bruteforcing must be performed for each IP you want   ∙
∙   to  license.  My  goal was a bit different, so some patching code was   ∙
∙   added ;)                                                                ∙

∙   In SP3 smart Check Point guys don't keep public keys (wonder why they   ∙
∙   need  8  when  1  would  be  enough)  in the executables in plaintext   ∙
∙   anymore.  Instead  they  use  *VERY* long function that's supposed to   ∙
∙   "generate"  the  keys (my bet is that it's also supposed to be pretty   ∙
∙   confusing).  Of  course  it  generate  the same 8 keys each time it's   ∙
∙   called.  Not  too  wise  solution,  to  say  the  least, because this   ∙
∙   function  is gone for good =P. Oh, and they now calculate checksum of   ∙
∙   first  public  key  to  check  if  it's not modified. Unfortunatelly,   ∙
∙   public  keys are modified... but correct checksum is modified as well   ∙

Φεεεεεεεεεεεεεεεεεεú πΣ ΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣ Σ

∙ µεεεεεεεεεεεεεεεεεε╛                                                      ∙

∙   Due  to  the  every  day  increasing  amount  of lamers who fake DAMN   ∙
∙   releases  ALL  DAMN releases starting from July 1, 2000 are digitally   ∙
∙   signed.                                                                 ∙

∙   Download  DAMN  Release Signature Verificator from http://www.damn.to   ∙
∙   (about  100K  only)  if  you want to be sure that release you got was   ∙
∙   really made by DAMN.                                                    ∙

∙   Don't  use  any  stuff  claiming  to be made by DAMN if it's released   ∙
∙   after  July  1,  2000  and doesn't pass verification. Using it can be   ∙
∙   dangerous.                                                              ∙

Φεεεεεεεεεεεεεεεεεεú πΣ ΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣ Σ

∙ µεεεεεεεεεεεεεεεεεε╛                                                      ∙

∙   Our  greetings  fly  to all groups and crackers who work hard to keep   ∙
∙   the Scene alive.                                                        ∙

∙   Personal  greetings  to:  Dimedrol,  Duelist,  egis, Quantico, Recca,   ∙
∙   russ97, tE!.                                                            ∙

Φεεεεεεεεεεεεεεεεεεú πΣ ΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣ Σ

∙ µεεεεεεεεεεεεεεεεεε╛                                                      ∙

∙   Visit our www site at       [ http://www.damn.to ]                      ∙
∙   Backup page                 [ http://damn.da.ru  ]                      ∙

∙   Email address for contacts  [ ivanopulo@usa.net  ]                      ∙

ßΣ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ ≈ ΣΣΣΣΣΣ Σ ΣΣΣΣΣΣ ≈ ΣΣΣΣΣΣ Σ ΣΣεεΣΣ Σ ΣΣΣΣΣΣ Σ²
ⁿ (c) 2001 DAMN α

Release ID: 3A602FE52B779B6B

----------------------- DAMN RELEASE SIGNATURE START ------------------------
damn_cpfw41sp3l.exe 1 fRZbP+FBGRx4itjMqIN3dzJZjkw 2RvUKmahDlOvSSiOkZFnjp9Uh1Y
damn.nfo 0 8qYZfGYrSiJi+eSSpz+Lg/6sIuo czq3A2VINl1GwqM14YYC2pWvVBA
------------------------ DAMN RELEASE SIGNATURE END -------------------------