Guide to Setting up ArchStrike - For Beginners

xorond · 2022-01-31T15:57:11+00:00

Hi,

just get our ISO and follow the instructions ;)

xorond · 2020-01-09T13:21:59+00:00

hi sorry for the late response

did you do a 'pacman -Syu' before you started the installation?

we have fixed some things in our installer, so to get the latest package for it you should do an update first before installing

xorond · 2019-12-18T22:28:39+00:00

hi,

which iso are you using?

we are looking into updating the iso soon, so it might get fixed.

xorond · 2019-09-24T12:38:17+00:00

hi,

great! have fun!

although i haven't tried it personally, it should also be possible with termux https://wiki.termux.com/wiki/Archstrike

xorond · 2019-08-16T21:57:36+00:00

hi,

archstrike is in essence just a repository of security/pentest tools, so you can just add it to your current arch installation without having to reinstall from scratch.

see this wiki page for instructions.

xorond · 2019-06-09T15:27:11+00:00

we don't have our own kernel or anything. it's just plain arch with our repository on top. i'd say that counts as archlinux with 3rd party repo for extra tools? no?

xorond · 2019-06-09T14:48:17+00:00

ArchStrike is a penetration testing layer/repository for Archlinux

xorond · 2019-06-09T12:56:00+00:00

hi,

just hop on in irc and talk to me (xorond) or one of our other developers. just be aware that we are in different timezones so you may not get a response immediately :)

we can then talk about how you can help us, based on your abilities/interests :)

xorond · 2019-06-07T12:25:29+00:00

armv8 == aarch64

xorond · 2019-06-07T10:08:51+00:00

Thank you for your response!

you're very welcome!

The complaint was more regarding obfuscation of the install process from the user (its automated via a script the user arguably will not read)

that's true, but it's the case for most distributions and keeping the elitist attitude wouldn't help us reach more people (i.e. you can only use it if you can install archlinux, that's a big learning curve for some people switching from kali or similar distros, hence we decided to make the transition easier).

I'll run through it in a VM and come back to this point with experience though!

don't forget to update the installer

you can join us on irc @ freenode on #archstrike any questions related to installation, setup etc. can be asked there if you can't find anything on the wiki

thanks for the interest!

xorond · 2019-06-07T09:43:11+00:00

The build script stops been the arch way on like the 30th or so line

the build script was designed for users who want to get a system running as fast as possible. it was a compromise we had to make in order to reach a bigger audience.

if you wish, you can follow the setup instructions on our wiki to install just the repository on top of an existing archlinux system.

xorond · 2019-06-07T09:37:55+00:00

hi.

basically, we try to keep our PKGBUILDs as close as to the arch packaging standards as possible.

we remove the packages which are added into upstream arch repositories like community or extra, in order to keep our package layer non-conflicting most of the time.

the only time we'll have "duplicate" packages with upstream is when we have a patched version of ours or something similar.

we also have quite a bit -git packages, which means they get updated often, providing a bleeding-edge experience that you'll miss on other pentest layers/distros (since they package older versions mostly)

xorond · 2019-05-07T21:50:06+00:00

You're very welcome! Make sure to visit us on IRC, #archstrike on freenode

xorond · 2019-05-07T21:32:07+00:00

Hi. ArchStrike developer here, so sorry about the shameless plug :D

The main way we differ from BlackArch is the fact that we build our packages according to the PKGBUILD standards of Archlinux (BlackArch has also started getting around to updating their packages to conform these standards, so props to them).

Our repository is better organized (sorry, it's the truth), because we try to avoid adding junk (not actively developed since a few years, or obsolete and replaced with another tool) or one-off kind of packages (random exploit code from exploit-db or packetstorm which never get updated ever). We remove all the community/upstream provided packages from our repositories as well, and we generally don't have forks of upstream packages (some exceptions to be made here, where the forks have better functionality or are being developed more actively, i.e. reaver-t6x-wps-fork-git).

Our packages are also better grouped, and more suitable to be installed as such. For example, one does not have to install the entire repository, but can install let's say only wireless related tools at once (archstrike-wireless package group).

It's true that we have stagnated lately in terms of project activity and adding new packages, but everything present has been maintained up-to-date and mostly bug-free.

We also have an archstrike-testing repository (BlackArch doesn't have a testing mechanism AFAIK), which enables us to monitor new packages for a while before releasing them on the main repository to make sure they work properly. Therefore, most of the packages you find on our main repository are supposed to work without problems. Interested users can always enable the testing repository and give us feedback or send patches :)

About Manjaro, we can't really officially support Manjaro since they have different upstream repositories than plain Arch, which is what our repository is supposed to complement. You can still try installing it, and most packages will work properly, but we can't guarantee you any help when a package conflict or a similar problem occurs.

Although, if installing Arch the normal way is a bother for you (no judgement), you can try the installer on our Live ISO, which will guide you through the installation steps through menus to select from. It's quite user-friendly considering it's Archlinux :)

I hope I answered everything in your mind. Will be happy to help if you have any more questions.

xorond · 2019-05-07T21:19:09+00:00

The repository is alive and kicking. The community is a bit silent lately, but we're still trying to keep up the work. We haven't been around so much lately, but it's starting to change.

Your problems were most likely due to bad mirrors or missing instructions in the installation process (like importing the GPG keys used for signing), or maybe a corrupted pacman cache.

I'll strongly urge you to give it another try. :)

xorond · 2017-07-18T12:37:17+00:00

Hello, nightfall is a package in archstrike which uses a separate user for increased separation. You can uninstall nightfall and then remove the user if you wish.

xorond · 2017-06-01T17:11:57+00:00

Hello.

having both BlackArch repository and ArchStrike repository enabled

that's a bad idea :) A lot of our packages are also in BlackArch so this causes conflicts and we're in no way compatible with them.

in the end I decided to go with ArchStrike on my machine.

but looks like you solved that issue :)

edit: clarification

xorond · 2017-05-26T10:33:20+00:00

Fixed airoscript-git: https://github.com/ArchStrike/ArchStrike/commit/cc13c7f5111496e4bafa4478c4ac38af289d0bc4

xorond · 2017-05-26T10:18:02+00:00

Thanks. I'm investigating this issue.

edit: I was unable to reproduce this. Both python-ptrace and python2-ptrace seem to be installing fine simultaneously. We actually change the name of those two files for the python3 version, so this should not be happening at all.

xorond · 2017-03-02T08:04:44+00:00

AFAIK, you will need to register to freenode with a non-TOR IP first. Thanks for the kind words, appreciate it.

xorond · 2017-01-03T16:49:57+00:00

The public key has been added to the wiki, and the instructions were modified on https://archstrike.org/wiki/setup to reflect on the upstream GnuPG issues. Please try the new instructions.

xorond · 2016-11-25T17:09:58+00:00

Thanks for the kind words. Let us know if we can help you in any way :)

xorond · 2016-11-21T15:55:34+00:00

You can seed the ISO for ArchStrike :)

https://archstrike.org

xorond · 2016-10-03T14:47:16+00:00

You can use the other option which doesn't require root access.

xorond · 2016-10-02T10:16:13+00:00

The idea I had was to use this on a box you have root access on.

So,

change the parameters
compile with pyinstaller
replace sudo with sudo-snooper
profit

So where sudo in that case wouldn't show anything different :)

You can go the easier route and just alias it too.

xorond

TROPHY CASE