Changes between Version 4 and Version 5 of Ticket #5837


Ignore:
Timestamp:
May 12, 2012, 7:28:15 PM (7 years ago)
Author:
mikeperry
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5837 – Description

    v4 v5  
    2929If you want to be extra-helpful, you can write up a detailed howto (and/or just paste the ones you find that already exist) on the process itself to make it even easier for others to learn and participate.
    3030
    31 We'll need to do this often.. Perhaps not for every release, but at least randomly on some builds every once and a while. Also, BinDiffing archived signed TBB copies from https://archive.torproject.org/tor-package-archive/torbrowser/ will be useful, too, so no need to wait for future releases. You can start today.
     31We'll need to do this often.. Perhaps not for every release, but at least randomly on some builds every once and a while. Also, BinDiffing archived signed TBB copies from https://archive.torproject.org/tor-package-archive/torbrowser/ will be useful, too, so no need to wait for future releases. You can start today. The source tarballs are in that directory as well, with -src.tar.gz instead of a language and arch. However, to get the actual git sources for an old release:
    3232
    33 Note that the above is a fantastic exercise in learning basic reverse engineering skills. Diffing vendor patches and malware updates is a common practice in the field. It's a useful skill to learn, if you have the time.
     33{{{
     34git clone git://git.torproject.org/torbrowser.git
     35cd torbrowser
     36git tag -l
     37git checkout torbrowser-2.2.35-9.1
     38}}}
     39
     40Git will tell you that you can't commit anything that way, but that shouldn't matter to you.
     41
     42Note that this whole process is a fantastic exercise in learning basic reverse engineering skills. Diffing vendor patches and malware updates is a common practice in the field. It's a useful skill to learn, if you have the time.
    3443
    3544Good luck!