Tiny Core Base > CorePlus
Installation of aircrack-ng,hashcat,hcxdumptool,hcxpcaptools,reaver
Rich:
Hi Sashank999
--- Quote from: Sashank999 on June 04, 2020, 12:54:58 AM --- ... The script looks amazing. ...
--- End quote ---
Thank you.
--- Quote --- ... It automates all things without human interactions. ...
--- End quote ---
Almost. The one thing you cannot automate is the Change-log: field of the .info file. That needs to be done manually. So if an
updated version of gpicview gets released, you would need to copy the last entry listed under Change-log: in the .info file:
--- Code: --- ~----- SNIP -----~
Source: https://downloads.sourceforge.net/lxde/gpicview-0.2.5.tar.xz
Change-log: 2020/03/28 Original release Version: 0.2.5
Current: 2020/03/28 Original release Version: 0.2.5
--- End code ---
Update this section of the script from this:
--- Code: ---Original-site: http://lxde.sourceforge.net/gpicview/
Change-log: $DATE Original release Version: $VERSION
Current: $DATE Original release Version: $VERSION
--- End code ---
To this:
--- Code: ---Original-site: http://lxde.sourceforge.net/gpicview/
Change-log: 2020/03/28 Original release Version: 0.2.5
Current: $DATE Original release Version: $VERSION
--- End code ---
And the next time it gets updated, it might look like this:
--- Code: ---Original-site: http://lxde.sourceforge.net/gpicview/
Change-log: 2020/03/28 Original release Version: 0.2.5
2020/06/03 Original release Version: 0.2.7
Current: $DATE Original release Version: $VERSION
--- End code ---
This way there is always a list of when updates occurred.
--- Quote --- ... Any tips about what to do with the licenses for hcxtools, hcxdumptool, aircrack-ng ?
--- End quote ---
See the section of the script that says Copy the copyright file. It places the licensing file here:
--- Code: ---/usr/local/share/doc/gpicview/COPYING
--- End code ---
--- Quote from: Sashank999 on June 04, 2020, 01:45:29 AM --- ... And also, should I follow the flags mentioned in your script for my x86 TCL ?
In your script, x86 flags are in case i686 and I am assuming they are the flags for all x86 TCL PCs.
CFLAGS=" -flto -march=i486 -mtune=i686 $OPTIMIZE -pipe -fno-plt"
# CXXFLAGS="g++ -flto -march=i486 -mtune=i686 $OPTIMIZE -pipe -fno-plt -fno-exceptions -fno-rtti"
LDFLAGS="-Wl,-T/usr/local/lib/ldscripts/elf_i386.xbn"
--- End quote ---
Yes, those are the flags to use for all x86 processors. I commented out the CXXFLAGS= line because gpicview didn't use any
C++ code. Truth of the matter is, that really wasn't necessary. Leaving CXXFLAGS defined doesn't hurt anything.
Sashank999:
--- Quote from: Rich on June 04, 2020, 09:45:32 AM ---See the section of the script that says Copy the copyright file. It places the licensing file here:
--- Code: ---/usr/local/share/doc/gpicview/COPYING
--- End code ---
--- End quote ---
Which script ?
--- Quote from: Rich on June 04, 2020, 09:45:32 AM ---Yes, those are the flags to use for all x86 processors. I commented out the CXXFLAGS= line because gpicview didn't use any
C++ code. Truth of the matter is, that really wasn't necessary. Leaving CXXFLAGS defined doesn't hurt anything.
--- End quote ---
Gpicview doesn't use C++. But what if others do. I am thinking that just uncommenting it is enough.
GPLv2 says to include the source. Should I copy src folder from the original aircrack-ng folder as it is into the tcz ?
Should I include source for MIT licensed hashcat,hcxdump and hcxtools ?
Juanito:
It is OK to set CXXFLAGS even if it is not used.
By "including the source", we mean include it with the submission not in the extension itself. All submissions need to have the source included.
Sashank999:
It is written in GPLv2 to include source in modified package.
Juanito:
The source will be uploaded to the tinycore site.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version