Just to make hack tool development a little easier, here are the standards that the staff has agreed on for packaging up hacktools for iOS.
-Hack tools should reside in /var/mobile/pentest, with start up scripts living in /usr/bin
-Metasploit and will live in /var/mobile/pentest/framwork
-Package id's
-If you ported an app it should be just the common name of the app (i.e. xterm or libnet)
-If you wrote a tool it should be in the form of com.<username>.<package> (i.e. com.trcx.iaht or com.boococky.ipwn)
-Section name is Hacktools (upper case 'h' and no space/punctuation of any kind)
-Control file for the debs should be in this format:
[Beginning control file]
Package:
(com.yourname.yourpackage if you wrote it, or the name of the program if you ported it, but NO SPACES)Name:
(friendly name)Version:
(version)Architecture: iphoneos-arm
Depends:
(package ids, separated by commas)Conflicts:
(package ids, separated by commas)Replaces:
(package ids, separated by commas)Description:
(really short description, this is what cydia shows under each package when you are just browsing)
(Full-length description (new lines must begin with a space!)Depiction:
https://ininjas.com/forum/index.php?topic=###;theme=14
Maintainer:
[username] <email>Author:
[username] <email>Sponsor: iNinjas <
repo@ininjas.com>
Section: Hacktools
Tag: role::
[pick one: enduser OR hacker OR developer](optional, if not included it will use the section icon)
Icon: file:///var/mobile/Documents/iNinjas/icons/
<package id>[end of control file]
Be sure to include a (yes, only one) new line (\n) charater at the end of the control file!!!!In the Tag: Role:: section pick one of the tags
The parts in red are what you should edit, just leave everything else the same.
When there is an email anywhere in the control file, include the < and > around it. That enables a user to click it and make an email!If anyone has any objections or question post about them. Feel free to edit to add/update this as needed.
