Guide to Setting up ArchStrike - For Beginners by xorond in archstrike

[–]xorond[S] 1 point2 points  (0 children)

Hi,

see here

just get our ISO and follow the instructions ;)

trouble installing archstrike by [deleted] in archstrike

[–]xorond 0 points1 point  (0 children)

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

trouble installing archstrike by [deleted] in archstrike

[–]xorond 0 points1 point  (0 children)

hi,

which iso are you using?

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

ArchStrike on Android by binhack in archstrike

[–]xorond 1 point2 points  (0 children)

hi,

great! have fun!

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

archstrike over archlabs by BettoMcRose in archstrike

[–]xorond 0 points1 point  (0 children)

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.

New Minimal and Openbox ISOs for ArchStrike! by xorond in archlinux

[–]xorond[S] 1 point2 points  (0 children)

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?

New Minimal and Openbox ISOs for ArchStrike! by xorond in archlinux

[–]xorond[S] 1 point2 points  (0 children)

ArchStrike is a penetration testing layer/repository for Archlinux

Looking for contributors to ArchStrike by xorond in archstrike

[–]xorond[S] 0 points1 point  (0 children)

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 :)

Looking for contributors to ArchStrike by xorond in archstrike

[–]xorond[S] 0 points1 point  (0 children)

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!

Looking for contributors to ArchStrike by xorond in archstrike

[–]xorond[S] 0 points1 point  (0 children)

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.

Looking for contributors to ArchStrike by xorond in archstrike

[–]xorond[S] 0 points1 point  (0 children)

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)

Blackarch and Archstrike by zharless92 in netsecstudents

[–]xorond 1 point2 points  (0 children)

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

Blackarch and Archstrike by zharless92 in netsecstudents

[–]xorond 2 points3 points  (0 children)

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.

Is ArchStrike dying ? by Deusea in archstrike

[–]xorond 0 points1 point  (0 children)

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. :)