Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 4
» Latest member: Aston
» Forum threads: 19
» Forum posts: 28

Full Statistics

Online Users
There is currently 1 user online
» 0 Member(s) | 1 Guest(s)

Latest Threads
SF iso ?
Forum: Help & Support:
Last Post: r1sen
09-16-2018, 11:31 AM
» Replies: 6
» Views: 17
Forum: Introductions:
Last Post: r1sen
09-13-2018, 09:48 PM
» Replies: 3
» Views: 19
Placing your wireless dev...
Forum: General:
Last Post: r1sen
08-13-2018, 06:03 PM
» Replies: 0
» Views: 13
Seamonkey 2.49.4
Forum: Packages & Drivers:
Last Post: r1sen
08-09-2018, 02:42 AM
» Replies: 0
» Views: 19
Ettercap 0.8.2 & deps
Forum: Packages & Drivers:
Last Post: r1sen
07-28-2018, 12:02 AM
» Replies: 0
» Views: 31
Release cycle
Forum: Release Notes:
Last Post: r1sen
07-23-2018, 04:13 AM
» Replies: 0
» Views: 71
v1.2Z.1 - released!
Forum: News:
Last Post: r1sen
07-22-2018, 02:57 AM
» Replies: 0
» Views: 94
Aircrack new libs extensi...
Forum: Bugs:
Last Post: r1sen
07-20-2018, 10:19 PM
» Replies: 0
» Views: 163
RouterSploit 3.3.0 & pyPa...
Forum: Packages & Drivers:
Last Post: r1sen
07-19-2018, 09:04 PM
» Replies: 0
» Views: 43
Updating TinyPaw-Linux an...
Forum: General:
Last Post: r1sen
07-15-2018, 11:44 PM
» Replies: 0
» Views: 53

  SF iso ?
Posted by: Aston - 09-14-2018, 08:41 AM - Forum: Help & Support: - Replies (6)

I download tpaw iso in 7zip from sourceForge and i get 0-bytes?
Is this download broken or something else?
Also i see that iso is 648MB in size ?
why is so large i expect something smaller ?
like beini , xiaopan ..i think that are 64MB or similar?

Print this item

Posted by: Aston - 09-09-2018, 07:31 PM - Forum: Introductions: - Replies (3)

First Hi! Smile
i don't know that this forum exist because i do bot often visit
Xiapan forum and i recently see some changes there.
I must say that i am not expert in linux in fact most of
time i use win7 ( i am a hobby programmer ,most preffer win32api- hmm i know not sound good for linux)
BUT...big BUT i always liked to see small distros
and support all effort authors made in creating.
I have installed wifi-slax on my old comuter and this ditro let say
worked-ok ? i run every program on that distro.
I think that is to large for my taste.
I tested Xiapan to and work with all my wifi cards
i have on computers - they are Canyon RaLink
probably are not the best cards but with all types of antennas i build they worked fine.
Yes i like to test my antennas with wifi distros Smile
What i would like to see is more modern look if is possible in still small package.
I hope that i don't talk to much or to talk about wrong things.

Print this item

  Placing your wireless device(s) into monitor mode
Posted by: r1sen - 08-13-2018, 06:03 PM - Forum: General: - No Replies

First things first, do you have to do this?... no, but should you do this?... yes, in my opinion.

Now that we have that out of the way, this will only be helpful to those using a wireless device and / or chipset that is compatible with the TinyPaw-Linux build release that you are currently using. If you are not sure if your device is supported then please consult the project Wiki section for exactly that:


Once you've established whether one or all of your devices are supported then we can continue. You may be asking "but r1sen, don't many of these tools and scripts place your device into monitor mode for you?" - yes, no and sort of. Though many of these scripts do or can place your device into monitor mode, doing things this way though not necessarily wrong... can lead to or occasionally lead to multiple instances being created for the same interface which can cause functionality and / or compatibility issues. Also, some of the eaves dropping, capture, sniffing tools - upon startup list only active interfaces, meaning that unless your device(s) are already placed in monitor mode or currently active in a connection they may not be listed as available interfaces - meaning that you may only see "ETHx" or "USBx" on your list for available interfaces to choose from. So in a nutshell, in my opinion this is why one of the very first things you ought to do upon booting into TinyPaw-Linux is placing the wireless device(s) you wish to use into monitor mode.

How is this done you ask? Simple:

1.) You will need to initiate Airmon-ng from one of two ways, either the "Airmon" launcher icon located in your WBAR at the bottom of your screen or from the terminal.

2.) Regardless of how you decide to go about initiating Airmon-ng you will be prompted to enter the proper command string to begin.

- First: sudo airmon-ng check kill

*This will terminate any process interacting or trying to interact with any wireless interface*

- Second: sudo airmon-ng

*This should display any and all available interfaces "wlan0, wlan1, wlan2, etc" - if none are listed, check to ensure your device is supported and / or you have USB redirection enabled in your VM*

- Third: sudo airmon-ng start wlan0 "or wlan1 or wlan2 or etc"

*This will now place each and any device you choose into monitor mode - of course if the device you choose supports monitor mode*

*The interface you've selected will now be listed as mon - ie: "wlan0mon , wlan1mon , wlan2mon , etc"

- Forth: sudo airmon-ng stop wlan0mon "or wlan1mon , or wlan2mon , or etc"

*This will place the interface you've selected back into managed mode from monitor*

Print this item

  Seamonkey 2.49.4
Posted by: r1sen - 08-09-2018, 02:42 AM - Forum: Packages & Drivers: - No Replies

Seamonkey extension upgraded from previous 2.49.3 build to 2.49.4 and wrapped in a squashfs *.tcz package. Current TinyPaw-Linux build (1.2Z.1) has version 2.49.3 by default, version 2.49.4 will not be included as a default package until the next TinyPaw build release. Installing and updating you seamonkey browser extension can be done in your current release build with the following instructions:

*Only for TinyPaw-Linux installed on a storage medium - LIVE runs will need to wait for following build release*

Available from either TinyPaw-Linux repository:






1.) Download both *.tcz and *.dep files from one of the above repositories.

2.) Copy both files into your (*/tce/optional/) directory.

3.) Open your onboot.lst file located within your (*/tce/) directory.

4.) Make the following changes to your onboot.lst file:
-Locate any line item containing: "seamonkey-2.49.3.tcz" and change to: "seamonkey-2.49.4.tcz"
*There may be more then one line item listing*

5.) Save the changes you've made to your onboot.lst file by either "file + save" or "cntl+s" and close your editor.

6.) Close all open windows and reboot your system.

7.) Upon reboot seamonkey 2.49.4 will be your active browser - if you are certain you will not wish to revert back to version 2.49.3 - then remove both: "seamonkey-2.49.3.tcz & seamonkey-2.49.3.tcz.dep" from your (*/tce/optional/) directory.

Print this item

  Ettercap 0.8.2 & deps
Posted by: r1sen - 07-28-2018, 12:02 AM - Forum: Packages & Drivers: - No Replies

Last/latest build release of ettercap (version 0.8.2) compiled within TinyPaw as well as the necessary libs. At this time a complete package with wbar launcher is not provided and will not be until the next release build of TinyPaw-Linux. Currently once the ettercap package and all required dependencies have been installed properly it can be launched from within your terminal or from the "Run" wbar launcher.

Full post available and originally posted on the Xiaopan OS forum:


*Please review the above post for detailed installation instructions as well as a full listing of required files and download links*

Print this item

Information Release cycle
Posted by: r1sen - 07-23-2018, 04:13 AM - Forum: Release Notes: - No Replies

Initially I planned for something around a 3 - 6 month cycle release period, however this being primarily a LIVE distro when major bugs have been discovered in a release build a new build is needed to be rolled out. Why? you may ask, simple - if the distribution is being ran in LIVE mode then applying a system update or patch would be meaningless if the distro reverted back to .iso default upon shutdown/reboot. So due to this I try to always post patching or updating instructions along with any files and/or extensions for those who wish to make necessary changes to their installed build - otherwise a new build is released ahead of schedule if the bug found significantly impacts core functionality. This is a constantly developed project and I do thank the communities that have given feedback and support and I certainly plan to continue this project. Thanks

Print this item

Star v1.2Z.1 - released!
Posted by: r1sen - 07-22-2018, 02:57 AM - Forum: News: - No Replies

Ugh - hate when that happens, yes v1.2Z was literally just released and unfortunately after the release a substantial bug was found in the aircrack extension I included in that build compiled against new libs. This bug affected at the least and maybe more components of aireplay / deauth / etc causing attacks to stall out. For anyone who has installed v1.2Z I have posted instructions on how to resolve this issue: 


However this caused pretty much any tool / script / etc relying on aircrack-ng to be severely unstable and running in LIVE mode would make patching not possible. So that is how we are on v1.2Z.1 now, I have corrected the aircrack-ng extension and released this new stable build for out-of-the-box functionality for running in LIVE.

Download available at:







Print this item

Exclamation Aircrack new libs extension - v1.2Z
Posted by: r1sen - 07-20-2018, 10:19 PM - Forum: Bugs: - No Replies

Unfortunately a bug was caught with the aircrack-ng 1.2 build compiled with new libs - certain functionality with aireplay / deauth / etc stalls out. The current aircrack build is being redacted back to the previous aircrack-ng-1.2-exp build default in regular v1.2 build. Again apologies - i am one person and I hate catching bugs only too late :/

I am rolling out a patched 1.2Z.1 build to correct this issue, however for those who have installed v1.2Z instructions on correcting this issue are as follows:

1.) Download the previous aircrack-ng extension from one of the following TinyPaw repositories:

SourceForge: aircrack-ng-1.2-exp.tcz

BitBucket: aircrack-ng-1.2-exp.tcz

2.) Copy the above extension to your optional directory located at (*/tce/optional/)

3.) Locate your onboot.lst file located in your (*/tce/) directory and make the following change:

- Adjust line item #8: from "aircrack-ng-1.2-exp-libs.tcz" and change it to: "aircrack-ng-1.2-exp.tcz"

4.) Save the changes to your onboot.lst file and close your editor

5.) Reboot your system, and aircrack-ng will be fully functional again with the above listed features.

Apologies! and thanks for your support!

Print this item

  RouterSploit 3.3.0 & pyPack_3.6_rev1
Posted by: r1sen - 07-19-2018, 09:04 PM - Forum: Packages & Drivers: - No Replies

As of now I have adopted a new practice for scripts and python tools where they will be embedded into the core "/home/tc/" directory instead of a squashfs extension to compensate for r+rw issues. That being said the new RouterSploit will not be included as a default tool until the following TinyPaw-Linux build release. However "pyPack_3.6_rev1.tcz" is the first revision release of all the necessary python3.6 modules needed to the newest RouterSploit (3.3.0) to function properly. Until the next build release RouterSploit can be downloaded from the project github: https://github.com/threat9/routersploit , unzipped and along with the pyPack_3.6_rev1 package can be initiated from the command line.

The pyPack_3.6_rev1 extension can be found at either TinyPaw repository:

SourceForge: pyPack_3.6_rev1.tcz

BitBucket: pyPack_3.6_rev1.tcz


1.) Download the pyPack_3.6_rev1.tcz extension from one of the above repositories.

2.) Copy the pyPack_3.6_rev1.tcz extension to your (*/tce/optional/) directory.

3.) Open your onboot.lst file located in your (*/tce/) directory and make the following adjustment:

-Add line item: pyPack_3.6_rev1.tcz *adding one additional empty line at the end of your onboot.lst*

4.) Download the RSF source at: https://github.com/threat9/routersploit

5.) Navigate to your (/home/tc/Downloads/) directory and open your terminal and enter the following:

-unzip routersploit-master.zip

6.) At this step close all windows and reboot your system.

7.) Now once your system has rebooted and now your pyPack_3.6_rev1.tcz is active navigate back to your (/home/tc/Downloads/routersploit-master/) directory and once again open your terminal and this time enter the following:

-sudo python3.6 rsf.py

8.) Enjoy~

Originally posted in the Xiaopan OS forum:


Print this item

Information Updating TinyPaw-Linux and/or packages
Posted by: r1sen - 07-15-2018, 11:44 PM - Forum: General: - No Replies

First things first, yes you can apply updates, and new packages to TinyPaw-Linux. However if you are running LIVE then you will not need to worry about that due to your system reverting to .iso default upon shutdown. Currently TinyPaw-Linux does not have repositories accessible via the "appsbrowser / package manager" , the Tiny Core Linux repositories are listed and accessible within TinyPaw as of the date of this posting. Though very important to understand, these listed Tiny Core Linux repositories SHOULD NEVER BE USED TO APPLY SYSTEM OR PACKAGE UPDATES! Yes, TinyPaw-Linux is derived from Tiny Core Linux, is it the same? No, no it is not. Many of the core system files, packages and libraries have either been updated, recompiled, modified, etc. from the parent Tiny Core Linux build and applying updates or installing system files intended for Tiny Core Linux from their repositories can certainly render your TinyPaw installation either unstable or unusable DO SO AT YOUR OWN RISK! Any updates or packages/extensions should only be obtained from the official TinyPaw-Linux repositories at: SourceForge or BitBucket and you should be have an understanding of the relationships between packages, libraries or core system files before applying updates over previous installed files. That all being said, I generally try to roll out vital core updates/patches with the .iso release cycle, any updates posted in between will certainly include instructions on installation as well as the listed dependencies needed as well, typically those posts can be found on this forum or from Xiaopan OS forums as well.

Now, why did I leave the Tiny Core Linux repositories listed in the package manager? Simple, as I said TinyPaw is still a Tiny Core derivative and thus the repositories were included to offer multimedia, imaging, office, etc. options for any user who desired to add more to TinyPaw. This is entirely a pen-test oriented system and thus has no additional applications, games, or multimedia options, that is why the Tiny Core Linux repositories were not removed from the package manager.

Similar information was posted in the TinyPaw-Linux wiki:


A YouTube video is available for an overview of installing packages and altering your onboot.lst file:


Print this item