diff --git a/Makefile b/Makefile index 677f32c..ac8715d 100644 --- a/Makefile +++ b/Makefile @@ -190,10 +190,24 @@ lint-zh: --hostname ba-guide \ ba-guide:$(VERSION) \ /bin/sh -c "chktex ${srcdir}/*-zh.tex; exit 0" + +PHONY: lint-nl +lint-nl: + @echo "===========================================" + @echo "= linting Dutch Guide =" + @echo "===========================================" + @docker run \ + --rm \ + -ti \ + -v $(shell pwd):/guide:rw \ + -w /guide \ + --hostname ba-guide \ + ba-guide:$(VERSION) \ + /bin/sh -c "chktex ${srcdir}/*-nl.tex; exit 0" # run the latex linting tool .PHONY: lint -lint: lint-de lint-el lint-en lint-es lint-fr lint-it lint-pt-br lint-ru lint-tr lint-zh +lint: lint-de lint-el lint-en lint-es lint-fr lint-it lint-pt-br lint-ru lint-tr lint-zh lint-nl # generate pdf per language .PHONY: pdf-de @@ -361,6 +375,21 @@ pdf-zh: lualatex \ ${srcdir}/blackarch-guide-zh.tex 1>>./build_log_zh" +.PHONY: pdf-nl +pdf-nl: + @echo "Compiling Dutch guide - output in build_log_nl" + @docker run \ + --rm \ + -ti \ + -v $(shell pwd):/guide:rw \ + -w /guide \ + --hostname ba-guide \ + ba-guide:$(VERSION) \ + /bin/sh -c "lualatex \ + ${srcdir}/blackarch-guide-nl.tex 1>./build_log_nl; \ + lualatex \ + ${srcdir}/blackarch-guide-nl.tex 1>>./build_log_nl" + # generate for all languages .PHONY: pdf -pdf: pdf-de pdf-el pdf-en pdf-es pdf-fr pdf-it pdf-pt-br pdf-ru pdf-tr pdf-zh +pdf: pdf-de pdf-el pdf-en pdf-es pdf-fr pdf-it pdf-pt-br pdf-ru pdf-tr pdf-zh pdf-nl diff --git a/README.md b/README.md index 546beae..5c001d0 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ This is part of BlackArch Linux and provides the latex files for the BlackArch User Guides. -To create a new Guide in in a language create a +To create a new Guide in a language create a blackarch-guide-.tex and an appendex-.tex file in the latex directory and add the target to the ```Makefile```. @@ -32,6 +32,7 @@ This will compile all guides listed as targets in the ```Makefile```. * ru * tr * zh +* nl You can also build a single guide (e.g. German) ```make pdf-de``` diff --git a/latex/appendix-nl.tex b/latex/appendix-nl.tex new file mode 100644 index 0000000..6ef3327 --- /dev/null +++ b/latex/appendix-nl.tex @@ -0,0 +1,312 @@ +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +% % +% BlackArch Linux bijlage sjabloon % +% % +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\appendix + +\chapter{Bijlage} + +\section{Veelgestelde vragen} + +\section{AUTEURS} +De volgende mensen hebben direct bijgedragen aan BlackArch:: +\begin{itemize} +\item Tyler Bennnett (tylerb@trix2voip.com) +\item fnord0 (fnord0@riseup.net) +\item nrz (nrz@nullsecurity.net) +\item Ellis Kenyo (elken.tdos@gmail.com) +\item CaledoniaProject (the.warl0ck.1989@gmail.com) +\item sudokode (sudokode@gmail.com) +\item Valentin Churavy (v.churavy@gmail.com) +\item Boy Sandy Gladies Arriezona (reno.esper@gmail.com) +\item Mathias Nyman +\item Johannes Löthberg (demizide@gmail.com) +\item Thiago da Silva Teixeira (teixeira.zeus@gmail.com) +\end{itemize} +De volgende mensen hebben direct bijgedragen aan ArchPwn en +zijn vervolgens bij BlackArch aangesloten: +\begin{itemize} +\item Francesco Piccinno (stack.box@gmail.com) +\item jensp (jens@jenux.homelinux.org) +\item Valentin Churavy (v.churavy@gmail.com) +\end{itemize} +We hebben code van de volgende mensen gebruikt: +\begin{itemize} +\item 3ED (krzysztof1987@gmail.com) +\item AUR Perl (aurperl@juster.info) +\item Aaron Griffin (aaron@archlinux.org) +\item Abakus (java5@arcor.de) +\item Adam Wolk (netprobe@gmail.com) +\item Aleix Pol (aleixpol@kde.org) +\item Aleshus (aleshusi@gmail.com) +\item Alessandro Pazzaglia (jackdroido@gmail.com) +\item Alessandro Sagratini (ale\_sagra@hotmail.com) +\item Alex Cartwright (alexc223@googlemail.com) +\item Alexander De Sousa (archaur.xandy21@spamgourmet.com) +\item Alexander Rødseth (rodseth@gmail.com) +\item Allan McRae (allan@archlinux.org) +\item AmaN (gabroo.punjab.da@gmail.com) +\item Andre Klitzing (aklitzing@online.de) +\item Andrea Scarpino (andrea@archlinux.org) +\item Andreas Schönfelder (passtschu@freenet.de) +\item Andrej Gelenberg (andrej.gelenberg@udo.edu) +\item Angel Velasquez (angvp@archlinux.org) +\item Antoine Lubineau (antoine@lubignon.info) +\item Anton Bazhenov (anton.bazhenov@gmail.com) +\item Arkham (arkham@archlinux.us) +\item Arthur Danskin (arthurdanskin@gmail.com) +\item Balda (balda@balda.ch) +\item Balló György (ballogyor+arch@gmail.com) +\item Bartek Piotrowski (barthalion@gmail.com) +\item Bartosz Feński (fenio@debian.org) +\item Bartłomiej Piotrowski (nospam@bpiotrowski.pl) +\item Bogdan Szczurek (thebodzio@gmail.com) +\item Brad Fanella (bradfanella@archlinux.us) +\item Brian Bidulock (bidulock@openss7.org) +\item C Anthony Risinger (anthony@xtfx.me) +\item CRT (crt.011@gmail.com) +\item Can Celasun (dcelasun@gmail.com) +\item Chaniyth (chaniyth@yahoo.com) +\item Chris Brannon (cmbrannon79@gmail.com) +\item Chris Giles (Chris.G.27@gmail.com) \& daschu117 +\item Christoph Siegenthaler (csi@gmx.ch) +\item Christoph Zeiler (archNOSPAM@moonblade.org) +\item Clément DEMOULINS (clement@archivel.fr) +\item Corrado Primier (bardo@aur.archlinux.org) +\item Daenyth (Daenyth+Arch@gmail.com) +\item Dale Blount (dale@archlinux.org) +\item Damir Perisa (damir.perisa@bluewin.ch) +\item Dan Fuhry (dan@fuhry.us) +\item Dan Serban (dserban01@yahoo.com) +\item Daniel A. Campoverde Carrión +\item Daniel Golle +\item Daniel Griffiths (ghost1227@archlinux.us) +\item Daniel J Griffiths (ghost1227@archlinux.us) +\item Daniel Micay (danielmicay@gmail.com) +\item Dave Reisner (dreisner@archlinux.org) +\item Dawid Wrobel (cromo@klej.net) +\item Devaev Maxim (mdevaev@gmail.com) +\item Devin Cofer (ranguvar@archlinux.us) +\item DigitalPathogen (aur@InfoSecResearchLabs.co.uk) +\item DigitalPathogen (aur@digitalpathogen.co.uk) +\item Dmitry A. Ilyashevich (dmitry.ilyashevich@gmail.com) +\item Dominik Heidler (dheidler@gmail.com) +\item DrZaius (lou@fakeoutdoorsman.com) +\item Ebubekir KARUL (ebubekirkarul@yandex.com) +\item Eduard "bekks" Warkentin (eduard.warkentin@gmail.com) +\item Elmo Todurov (todurov@gmail.com) +\item Emmanuel Gil Peyrot (linkmauve@linkmauve.fr) +\item Eric Belanger (eric@archlinux.org) +\item Ermak (ermak@email.it) +\item Evangelos Foutras (evangelos@foutrelis.com) +\item Fabian Melters (melters@gmail.com) +\item Fabiano Furtado (fusca14@gmail.com) +\item Federico Quagliata (ntp@quaqo.org) +\item Firmicus (francois.archlinux@org) +\item Florian Pritz (bluewind@jabber.ccc.de) +\item Florian Pritz (flo@xinu.at) +\item Francesco Piccinno (stack.box@gmail.com) +\item François Charette (francois@archlinux.org) +\item Gaetan Bisson (bisson@archlinux.org) +\item Geoffroy Carrier (geoffroy.carrier@koon.fr) +\item Georg Grabler (STiAT) +\item George Hilliard (gh403@msstate.edu) +\item Gerardo Exequiel Pozzi (vmlinuz386@yahoo.com.ar) +\item Gilles CHAUVIN (gcnweb@gmail.com) +\item Giovanni Scafora (giovanni@archlinux.org) +\item Gordin (9ordin@gmail.com) +\item Guillaume ALAUX (guillaume@archlinux.org) +\item Guillermo Ramos (0xwille@gmail.com) +\item Gustavo Alvarez (sl1pkn07@gmail.com) +\item Hugo Doria (hugo@archlinux.org) +\item Hyacinthe Cartiaux (hyacinthe.cartiaux@free.fr) +\item James Fryman (jfryman@gmail.com) +\item Jan "heftig" Steffens (jan.steffens@gmail.com) +\item Jan de Groot (jgc@archlinux.org) +\item Jaroslav Lichtblau (dragonlord@aur.archlinux.org) +\item Jaroslaw Swierczynski (swiergot@aur.archlinux.org) +\item Jason Chu (jason@archlinux.org) +\item Jason R Begley (jayray@digitalgoat.com) +\item Jason Rodriguez +\item Jason St. John (jstjohn@purdue.edu) +\item Jawmare (victor2008@gmail.com) +\item Jeff Mickey (jeff@archlinux.org) +\item Jens Pranaitis (jens@chaox.net) +\item Jens Pranaitis (jens@jenux.homelinux.org) +\item Jinx (jinxware@gmail.com) +\item John D Jones III (jnbek1972@gmail.com) +\item John Proctor (jproctor@prium.net) +\item Jon Bergli Heier (snakebite@jvnv.net) +\item Jonas Heinrich +\item Jonathan Steel (jsteel@aur.archlinux.org) +\item Joris Steyn (jorissteyn@gmail.com) +\item Josh VanderLinden (arch@cloudlery.com) +\item Jozef Riha (jose1711@gmail.com) +\item Judd Vinet (jvinet@zeroflux.org) +\item Juergen Hoetzel (jason@archlinux.org) +\item Juergen Hoetzel (juergen@archlinux.org) +\item Justin Davis (jrcd83@gmail.com) +\item Kaiting Chen (kaitocracy@gmail.com) +\item Kaos +\item Kevin Piche (kevin@archlinux.org) +\item Kory Woods (kory@virlo.net) +\item Kyle Keen (keenerd@gmail.com) +\item Larry Hajali (larryhaja@gmail.com) +\item LeCrayonVert +\item Le\_suisse (lesuisse.dev+aur@gmail.com) +\item Lekensteyn (lekensteyn@gmail.com) +\item Limao Luo (luolimao+AUR@gmail.com) +\item Lucien Immink +\item Lukas Fleischer (archlinux@cryptocrack.de) +\item Manolis Tzanidakis +\item Marcin "avalan" Falkiewicz (avalatron@gmail.com) +\item Mariano Verdu (verdumariano@gmail.com) +\item Marti Raudsepp (marti@juffo.org) +\item MatToufoutu (mattoufootu@gmail.com) +\item Matthew Sharpe (matt.sharpe@gmail.com) +\item Mauro Andreolini (mauro.andreolini@unimore.it) +\item Max Pray a.k.a. Synthead (synthead@gmail.com) +\item Max Roder (maxroder@web.de) +\item Maxwell Pray a.k.a. Synthead (synthead@gmail.com) +\item Maxwell Pray a.k.a. Synthead (synthead1@gmail.com) +\item Mech (tiago.bmp@gmail.com) +\item Michael Düll (mail@akurei.me) +\item Michael P (ptchinster@archlinux.us) +\item Michal Krenek (mikos@sg1.cz) +\item Michal Zalewski (lcamtuf@coredump.cx) +\item Miguel Paolino (mpaolino@gmail.com) +\item Miguel Revilla (yo@miguelrevilla.com) +\item Mike Roberts (noodlesgc@gmail.com) +\item Mike Sampson (mike@sambodata.com) +\item Nassim Kacha (nassim.kacha@gmail.com) +\item Nicolas Pouillard (nicolas.pouillard@gmail.com) +\item Nicolas Pouillard https://nicolaspouillard.fr +\item Niklas Schmuecker +\item Oleander Reis (oleander@oleander.cc) +\item Olivier Le Moal (mail@olivierlemoal.fr) +\item Olivier Médoc "oliv" (o\_medoc@yahoo.fr) +\item Pascal E. (archlinux@hardfalcon.net) +\item Patrick Leslie Polzer (leslie.polzer@gmx.net) +\item Paul Mattal (paul@archlinux.org) +\item Paul Mattal (pjmattal@elys.com) +\item Pengyu CHEN (cpy.prefers.you@gmail.com) +\item Peter Wu (lekensteyn@gmail.com) +\item Philipp 'TamCore' B. (philipp@tamcore.eu) +\item Pierre Schmitz (pierre@archlinux.de) +\item Pranay Kanwar (pranay.kanwar@gmail.com) +\item Pranay Kanwar (warl0ck@metaeye.org) +\item PyroPeter (googlemail@com.abi1789) +\item PyroPeter (googlemail.com@abi1789) +\item Ray Rashif (schiv@archlinux.org) +\item Remi Gacogne +\item Renan Fernandes (renan@kauamanga.com) +\item Richard Murri (admin@richardmurri.com) +\item Roberto Alsina (ralsina@kde.org) +\item Robson Peixoto (robsonpeixoto@gmail.com) +\item Roel Blaauwgeers (roel@ttys0.nl) +\item Rorschach (r0rschach@lavabit.com) +\item Ruben Schuller (shiml@orgizm.net) +\item Rudy Matela (rudy@matela.com) +\item Ryon Sherman (ryon.sherman@gmail.com) +\item Sabart Otto \item Seberm (seberm@gmail.com) +\item SakalisC (chrissakalis@gmail.com) +\item Sam Stuewe (halosghost@archlinux.info) +\item SanskritFritz (SanskritFritz@gmail.com) +\item Sarah Hay (sarahhay@mb.sympatico) +\item Sebastian Benvenuti (sebastianbenvenuti@gmail.com) +\item Sebastian Nowicki (sebnow@gmail.com) +\item Sebastien Duquette (ekse.0x@gmail.com) +\item Sebastien LEDUC (sebastien@sleduc.fr) +\item Sebastien Leduc (sebastien@sleduc.fr) +\item Sergej Pupykin (pupykin.s+arch@gmail.com) +\item Sergio Rubio (rubiojr@biondofu.net) +\item Sheng Yu (magicfish1990@gmail.com) +\item Simon Busch (morphis@gravedo.de) +\item Simon Legner (Simon.Legner@gmail.com) +\item Sirat18 (aur@sirat18.de) +\item SpepS (dreamspepser@yahoo.it) +\item Spider.007 (archPackage@spider007.net) +\item Stefan Seering +\item Stephane Travostino (stephane.travostino@gmail.com) +\item Stéphane Gaudreault (stephane@archlinux.org) +\item Sven Kauber (celeon@gmail.com) +\item Sven Schulz (omee@archlinux.de) +\item Sébastien Duquette (ekse.0x@gmail.com) +\item Sébastien Luttringer (seblu@archlinux.org) +\item TDY (tdy@gmx.com) +\item Teemu Rytilahti (tpr@iki.fi) +\item Testuser\_01 +\item Thanx (thanxm@gmail.com) +\item Thayer Williams (thayer@archlinux.org) +\item Thomas S Hatch (thatch45@gmail.com) +\item Thorsten Töpper +\item Tilmann Becker (tilmann.becker@freenet.de) +\item Timothy Redaelli (timothy.redaelli@gmail.com) +\item Timothée Ravier (tim@siosm.fr) +\item Tino Reichardt +\item Tobias Kieslich (tobias@justdreams.de) +\item Tobias Powalowski (tpowa@archlinux.org) +\item Tom K (tomk@runbox.com) +\item Tom Newsom (Jeepster@gmx.co.uk) +\item Tomas Lindquist Olsen (tomas@famolsen.dk) +\item Travis Willard (travisw@wmpub.ca) +\item Valentin Churavy (v.churavy@gmail.com) +\item ViNS (gladiator@fastwebnet.it) +\item Vlatko Kosturjak (kost@linux.hr) +\item Wes Brown (wesbrown18@gmail.com) +\item William Rea (sillywilly@gmail.com) +\item Xavier Devlamynck (magicrhesus@ouranos.be) +\item Xiao\item Long Chen (chenxiaolong@cxl.epac.to) +\item aeolist (aeolist@hotmail.com) +\item ality@pbrane.org +\item astaroth (astaroth\_@web.de) +\item bender02@archlinux.us +\item billycongo (billycongo@gmail.com) +\item bslackr (brendan@vastactive.com) +\item cbreaker (cbreaker@tlen.pl) +\item chimeracoder (dev@chimeracoder.net) +\item damir (damir@archlinux.org) +\item danitool +\item darkapex (me@jailuthra.in) +\item daronin +\item dkaylor (dpkaylor@gmail.com) +\item dobo (dobo90\_at\_gmail@com) +\item dorphell (dorphell@archlinux.org) +\item evr (evanroman@at.gmail) +\item fnord0 (fnord0@riseup.net) +\item fxbru (frxbru@gmail) +\item hcar +\item icarus (icarus.roaming@gmail.com) +\item iceman (icemanf@gmail.com) +\item kastor (kastor@fobos.org) +\item kfgz (kfgz@interia.pl) +\item linuxSEAT (linuxSEAT@gmail.com) +\item m4xm4n (max@maxfierke.com) +\item mar77i (mysatyre@gmail.com) +\item marc0s (marc0s@fsfe.org) +\item mickael9 (mickael9@gmail.com) +\item nblock (nblock@archlinux.us) +\item nofxx (x@nofxx.com) +\item onny (onny@project +\item pootzko (pootzko@gmail.com) +\item revel (revel@muub.net) +\item rich\_o (rich\_o@lavabit.com) +\item s1gma (s1gma@mindslicer.com) +\item sandman (r.coded@gmail.com) +\item sebikul (sebikul@gmail.com) +\item sh0 (mee@sh0.org) +\item shild (sxp@bk.ru) +\item simo (simo@archlinux.org) +\item snuo +\item sudokode (sudokode@gmail.com) +\item tobias (tobias@archlinux.org) +\item trashstar (trash@ps3zone.org) +\item unexist (unexist@subforge.org) +\item untitled (rnd0x00@gmail.com) +\item virtuemood (virtue@archlinux.us) +\item wido (widomaker2k7@gmail.com) +\item wodim (neikokz@gmail.com) +\item yannsen (ynnsen@gmail.com) +\end{itemize} diff --git a/latex/blackarch-guide-nl.tex b/latex/blackarch-guide-nl.tex new file mode 100644 index 0000000..8d7d406 --- /dev/null +++ b/latex/blackarch-guide-nl.tex @@ -0,0 +1,764 @@ +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +% % +% BlackArch Linux Handboek % +% % +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\documentclass[a4paper, oneside, 11pt]{book} + +%%% INCLUDES %%% +\renewcommand{\familydefault}{\sfdefault} + +\usepackage{array} +\usepackage{color} +\usepackage{enumerate} +\usepackage{fancyhdr} +\usepackage{fancyvrb} +\usepackage{geometry} +\usepackage{graphicx} +\usepackage{html} +\usepackage{hyperref} +\usepackage{ifpdf} +\usepackage{listings} +\usepackage{pstricks} +\usepackage{supertabular} +\usepackage{tocloft} +\usepackage[utf8]{inputenc} +\usepackage[dutch]{babel} + +%%% LAYOUT %%% +\setlength{\parindent}{0em} +\setlength{\parskip}{1.5ex plus0.5ex minus0.5ex} +\geometry{left=2.5cm, textwidth=16cm, top=3cm, textheight=25cm, bottom=3cm} +\widowpenalty=2000 +\clubpenalty=1000 +\frenchspacing +\sloppy +\pagecolor[HTML]{FFFFFF} +\color[HTML]{333333} +\setcounter{tocdepth}{10} +\setcounter{secnumdepth}{10} + +\hypersetup{ + pdftitle={BlackArch Linux, Het BlackArch Linux Handboek}, + pdfsubject={BlackArch Linux, Het BlackArch Linux Handboek}, + pdfauthor={BlackArch Linux, BlackArch Linux}, + pdfkeywords={BlackArch Linux, Penetration Testing, Security, Hacking, Linux}, + pdfcenterwindow=true, + colorlinks=true, + breaklinks=true, + linkcolor=blue, + menucolor=blue, + urlcolor=blue +} + +% syntax highlighting +% all options should be set here document wide +\lstset{ +backgroundcolor=\color[HTML]{EEEEEE}, +frame=single, +basicstyle=\footnotesize\ttfamily, +float, +deletekeywords={return}, +otherkeywords={mkdir, curl, sudo, sha1sum, grep, cut, sort, wget, makepkg, +pacman, blackman, chmod}, +keywordstyle=\color{orange}, +commentstyle=\color{blue}, +stringstyle=\color{red}, +language=bash, +showspaces=false, +showtabs=false, +tabsize=2 +} + +%%% HEADER / FOOTER %%% +\setlength{\headheight}{33pt} +\setlength{\headsep}{33pt} +\lhead{{\includegraphics[width=1cm,height=1cm]{images/logo.png}}} +\rhead{The BlackArch Linux Guide} + +%%% CUSTOM MACROS %%% +% for html links +\ifpdf\else +\def\href#1#2{\htmladdnormallink{#2}{#1}} +\fi + +%------------------% +% TITELPAGINA % +%------------------% +\begin{document} +\pagestyle{empty} +\begin{center} +\begin{figure}[htbp] +\centering +\vspace{0.5cm} +\includegraphics[width=8cm]{images/logo.png} +\label{fig:logo} +\end{figure} +\vspace{0.5cm} +\Huge{\textbf{Het BlackArch Linux Handboek}}\\ +\vspace{1cm} +\Large{\color{blue}https://www.blackarch.org/}\\ +\vspace{0.5cm} +\end{center} +\newpage +\tableofcontents +\newpage +\pagestyle{fancy} + +%------------------% +% Hoofdstuk 1 % +%------------------% + +\chapter{Inleiding} + +\section{Overzicht} +Het BlackArch Linux handboek is opgedeeld in enkele delen: +\begin{itemize} +\item Inleiding - Een globaal overzicht, een inleiding en toegevoegde nuttige projectinformatieion +\item Gebruikershandleiding - Alles wat de gemiddelde gebruiker nodig heeft om effectief te starten met BlackArch +\item Ontwikkelaarshandleiding - Hoe te beginnen met ontwikkelwerk en bijdragen aan BlackArch +\item Gereedschapshandleiding - Diepgaande details over de betreffende gereedschappen en applicaties met daarbij praktische voorbeelden (Werk In Uitvoering) +\end{itemize} + +\section{Wat is BlackArch Linux?} +BlackArch is een complete Linux distributie voor pentesters en security onderzoekers. +Het is een afgeleide van \href{https://www.archlinux.org/}{ArchLinux} en gebruikers kunnen de BlackArch onderdelen stuk voor stuk of in bulk hieraan toevoegen. + +De gereedschapskist is gedeeld als Arch Linux \href{https://wiki.archlinux.org/index.php/Unofficial\_User\_Repositories} +{unofficial user repository} , dus je kunt BlackArch installeren bovenop een reeds bestaande Arch Linux installatie. +Packages kunnen per stuk of per categorie geïnstalleerd worden. + +De constant groeiende repository heeft op dit moment meer dan \href{https://www.blackarch.org/tools.html}{2600} gereedschappen. +Deze zijn allemaal doorgrondig getest voordat ze aan de codebase worden toegevoegd om de kwaliteit van de repository te waarborgen. +%Moet snel de testmethode/codereviewprocedures omschrijven. + +\section{Geschiedenis van BlackArch Linux} +Binnenkort beschikbaar... + +\section{Ondersteunde platforms} +Binnenkort beschikbaar... + +\section{Doe mee} +Je kunt het BlackArch team bereiken via de volgende kanalen: + +Website: \url{https://www.blackarch.org/} + +Mail: \href{mailto:team@blackarch.org}{team@blackarch.org} + +IRC: \url{irc://irc.freenode.net/blackarch} + +Twitter: \url{https://twitter.com/blackarchlinux} + +Github: \url{https://github.com/Blackarch/} + +Discord: \url{https://discord.com/invite/xMHt8dW} + +%------------------% +% Hoofdstuk 2 % +%------------------% + + +\chapter{Gebruikershandleiding} + +\section{Installatie} +De volgende alineas laten je zien hoe je de BlackArch vanaf repository bouwt +en hoe je packages installeert. Blackarch ondersteunt zowel het installeren vanaf +de repository door middel van binary packages als het compilen en installeren vanaf broncode. + +BlackArch is compatibel met een normale Arch installatie. Het fungeert als onofficiele +gebruikersrepository. Als je liever een ISO gebruikt, bekijk dan de sectie:\href{https://www.blackarch.org/downloads.html#iso}{ISOs}. + +\subsection{Installeren bovenop een bestaande ArchLinux installatie} +Start \href{https://blackarch.org/strap.sh}{strap.sh} als de root user en volg de gegeven instructies. Hieronder een voorbeeld: +\begin{lstlisting} + curl -O https://blackarch.org/strap.sh + sha1sum strap.sh # should match: d062038042c5f141755ea39dbd615e6ff9e23121 + sudo chmod +x strap.sh + sudo ./strap.sh +\end{lstlisting} + +Download nu een nieuwe kopie van de master package lijst en synchroniseer de packages met: +\begin{lstlisting} + sudo pacman -Syyu +\end{lstlisting} + + +\subsection{Packages Installeren} +Je kunt de tools van de blackarch repository nu installeren. +\begin{enumerate} +\item Om alle beschikbare tools weer te geven, gebruik: +\begin{lstlisting} + pacman -Sgg | grep blackarch | cut -d' ' -f2 | sort -u +\end{lstlisting} + +\item Om alle tools te installeren, gebruik: +\begin{lstlisting} + pacman -S blackarch +\end{lstlisting} + +\item Om een specifieke categorie van tools te installeren, gebruik: +\begin{lstlisting} + pacman -S blackarch- +\end{lstlisting} + +\item Om de blackarch categorieën te zien, gebruik: +\begin{lstlisting} + pacman -Sg | grep blackarch +\end{lstlisting} + +\end{enumerate} + +\subsection{Packages vanaf broncode installeren} +Een alternatieve manier van installeren is de BlackArch packages vanaf de broncode zelf te bouwen. De PKGBUILDs zijn te vinden op: +\href{https://github.com/BlackArch/blackarch/tree/master/packages}{github}. Om de hele repo te bouwen, gebruik de +\href{https://github.com/BlackArch/blackman}{Blackman} tool. +\begin{itemize} +\item De eerste stap is Blackman te installeren. Als de BlackArch package repository al op je systeem staat kan dit met: +is setup on your machine, you can install Blackman: +\begin{lstlisting} + pacman -S blackman +\end{lstlisting} + +\item Je kunt Blackman ook vanaf de bron opbouwen met: +\begin{lstlisting} + mkdir blackman + cd blackman + wget https://raw.github.com/BlackArch/blackarch/master/packages/blackman/PKGBUILD + # Zeker weten dat er niet (kwaadwillend) met de PKGBUILD geknoeid is. + makepkg -s +\end{lstlisting} + +\item Of je kunt Blackman vanaf de AUR installeren met: +\begin{lstlisting} + -S blackman +\end{lstlisting} + +\end{itemize} + +\subsection{Basisgebruik van Blackman} Blackman is simpel in gebruik, maar de flags zijn anders dan wat je gewend bent van bijvoorbeeld pacman. Basis commandos staan hieronder met voorbeelden. +\begin{itemize} +\item Packages downloaden, bouwen en installeren: +\begin{lstlisting} + sudo blackman -i package +\end{lstlisting} + +\item Een hele categorie downloaden, bouwen en installeren: +\begin{lstlisting} + sudo blackman -g group +\end{lstlisting} + +\item Alle BlackArch tools downloaden, compilen en installeren: +\begin{lstlisting} + sudo blackman -a +\end{lstlisting} + +\item Alle BlackArch categorieën laten zien: +\begin{lstlisting} + blackman -l +\end{lstlisting} + +\item Alle toolcategoriën laten zien: +\begin{lstlisting} + blackman -p category +\end{lstlisting} + +\end{itemize} + +\subsection{Installeren vanaf de full-, netinstal- ISO of ArchLinux} +Je kunt BlackArch Linux installeren vanaf een van onze full- of netinstall- ISO's. \\ Zie \url{https://www.blackarch.org/download.html#iso}. +De volgende steppen zijn noodzakelijk +na opstarten via een ISO. +\begin{itemize} +\item BlackArch-installer package installeren: +\begin{lstlisting} + sudo pacman -S blackarch-installer +\end{lstlisting} + +\item Starten +\begin{lstlisting} + sudo blackarch-install +\end{lstlisting} + +\end{itemize} + +%------------------% +% Hoofdstuk 3 % +%------------------% + +\chapter{Ontwikkelaarsgids} + +\section{Arch' Build System en Repositories} + +PKGBUILD bestanden zijn build scripts. Elk script geeft instructies aan makepkg(1) hoe een packate te maken. PKGBUILD bestanden zijn in Bash geschreven. + +Voor meer informatie, lees (of scan) de volgende, engelstalige, wikipagina's: +\begin{itemize} +\item \href{https://wiki.archlinux.org/index.php/Creating_Packages}{Arch Wiki: Creating Packages} +\item \href{https://wiki.archlinux.org/index.php/Makepkg}{Arch Wiki: makepkg} +\item \href{https://wiki.archlinux.org/index.php/PKGBUILD}{Arch Wiki: PKGBUILD} +\item \href{https://wiki.archlinux.org/index.php/Arch_Packaging_Standards}{Arch Wiki: Arch Packaging Standards} +\end{itemize} + +\section{Blackarch PKGBUILD standaarden} +Om het simpel te houden zijn onze PKGBUILD's vergelijkbaar met die van AUR. Wel zijn er enkele kleine verschillen, deze zijn hieronder verder uitgelegd. +Elke package moet minimaal van blackarch zijn, maar er zal ook veel overlap zijn met packages die van meerdere groepen zijn. + +\subsection{Groepen} +Om het gebruikers makkelijk te maken een specifieke reeks van packages te installeren, zijn deze onderverdeeld in groepen. Groepen maken het mogelijk voor gebruikers om simpelweg het commando: "pacman -S " te gebruiken om een hele groep packages te pullen. + +\subsubsection{blackarch} +De blackarch groep is de basisgroep waar alle packages in moeten zitten. Dit maakt het mogelijk voor de gebruiker om alle packages gemakkelijk te installeren. + +Wat hierin zou moeten zitten: alles. + +\subsubsection{blackarch-anti-forensic} +Packages die gebruikt worden om forensische activiteiten tegen te gaan, +dit is inclusief encryption, stenografie en alles dat bestanden of bestand attributen aanpast. +Dit bevat alle tools die enodig zijn om, in basis, wijzigingen te maken aan een systeem met het doel om informatie te verstoppen. + +Voorbeelden: luks, TrueCrypt, Timestomp, dd, ropeadope, secure-delete + +\subsubsection{blackarch-automation} +Packages die gebruikt worden voor tool of workflow automation. + +Voorbeelden: blueranger, tiger, wiffy + +\subsubsection{blackarch-backdoor} +Packages die backdoors misbruiken of openen op reeds kwetsbare systemen. + +Voorbeelden: backdoor-factory, rrs, weevely + +\subsubsection{blackarch-binary} +Packages die hun uitvoering hebben op binary files. + +Voorbeelden: binwally, packerid + +\subsubsection{blackarch-bluetooth} +Packages that exploit anything concerning the Bluetooth standard (802.15.1). + +Voorbeelden: ubertooth, tbear, redfang + +\subsubsection{blackarch-code-audit} +Packages that audit existing source code for vulnerability analysis. + +Voorbeelden: flawfinder, pscan + +\subsubsection{blackarch-cracker} +Packages used for cracking cryptographic functions, ie hashes. + +Voorbeelden: hashcat, john, crunch + +\subsubsection{blackarch-crypto} +Packages that work with cryptography, with the exception of cracking. + +Voorbeelden: ciphertest, xortool, sbd + +\subsubsection{blackarch-database} +Packages that involve database exploitations on any level. + +Voorbeelden: metacoretex, blindsql + +\subsubsection{blackarch-debugger} +Packages that allow the user to view what a particular program is "doing" in realtime. + +Voorbeelden: radare2, shellnoob + +\subsubsection{blackarch-decompiler} +Packages that attempt to reverse a compiled program into source code. + +Voorbeelden: flasm, jd-gui + +\subsubsection{blackarch-defensive} +Packages that are used to protect a user from malware \& attacks from other users. + +Voorbeelden: arpon, chkrootkit, sniffjoke + +\subsubsection{blackarch-disassembler} +This is similar to blackarch-decompiler, and there will probably be a lot +of programs that fall into both, however these packages produce assembly output +rather than the raw source code. + +Voorbeelden: inguma, radare2 + +\subsubsection{blackarch-dos} +Packages that use DoS (Denial of Service) attacks. + +Voorbeelden: 42zip, nkiller2 + +\subsubsection{blackarch-drone} +Packages that are used for managing physically engineered +drones. + +Voorbeelden: meshdeck, skyjack + +\subsubsection{blackarch-exploitation} +Packages that takes advantages of exploits in other programs or services. + +Voorbeelden: armitage, metasploit, zarp + +\subsubsection{blackarch-fingerprint} +Packages that exploit fingerprint biometric equipment. + +Voorbeelden: dns-map, p0f, httprint + +\subsubsection{blackarch-firmware} +Packages that exploit vulnerabilities in firmware + +Voorbeelden: None yet, amend asap. + +\subsubsection{blackarch-forensic} +Packages that are used to find data on physical disks or embedded memory. + +Voorbeelden: aesfix, nfex, wyd + +\subsubsection{blackarch-fuzzer} +Packages that use the fuzz testing principle, ie +"throwing" random inputs at the subject to see what happens. + +Voorbeelden: msf, mdk3, wfuzz + +\subsubsection{blackarch-hardware} +Packages that exploit or manage anything to do with +physical hardware. + +Voorbeelden: arduino, smali + +\subsubsection{blackarch-honeypot} +Packages that act as "honeypots", ie programs that appear to +be vulnerable services used to attract hackers into a trap. + +Voorbeelden: artillery, bluepot, wifi-honey + +\subsubsection{blackarch-keylogger} +Packages that record and retain keystrokes on another system. + +Voorbeelden: None yet, amend asap. + +\subsubsection{blackarch-malware} +Packages that count as any type of malicious software or +malware detection. + +Voorbeelden: malwaredetect, peepdf, yara + +\subsubsection{blackarch-misc} +Packages that don't particularly fit into any categories. + +Voorbeelden: oh-my-zsh-git, winexe, stompy + +\subsubsection{blackarch-mobile} +Packages that manipulate mobile platforms. + +Voorbeelden: android-sdk-platform-tools, android-udev-rules + +\subsubsection{blackarch-networking} +Package that involve IP networking. + +Voorbeelden: arptools, dnsdiag, impacket + +\subsubsection{blackarch-nfc} +Packages that use nfc (near-field communications). + +Voorbeelden: nfcutils + +\subsubsection{blackarch-packer} +Packages that operate on or involve packers. + +\textit{packers are programs that embed malware within other executables.} + +Voorbeelden: packerid + +\subsubsection{blackarch-proxy} +Packages that acts as a proxy, ie redirecting traffic +through another node on the internet. + +Voorbeelden: burpsuite, ratproxy, sslnuke + +\subsubsection{blackarch-recon} +Packages that actively seeks vulnerable exploits in the +wild. More of an umbrella group for similar packages. + +Voorbeelden: canri, dnsrecon, netmask + +\subsubsection{blackarch-reversing} +This is an umbrella group for any decompiler, +disassembler or any similar program. + +Voorbeelden: capstone, radare2, zerowine + +\subsubsection{blackarch-scanner} +Packages that scan selected systems for vulnerabilities. + +Voorbeelden: scanssh, tiger, zmap + +\subsubsection{blackarch-sniffer} +Packages that involve analyzing network traffic. + +Voorbeelden: hexinject, pytactle, xspy + +\subsubsection{blackarch-social} +Packages that primarily attack social networking sites. + +Voorbeelden: jigsaw, websploit + +\subsubsection{blackarch-spoof} +Packages that attempt to spoof the attacker such, in that +the attacker doesn't show up as an attacker to the victim. + +Voorbeelden: arpoison, lans, netcommander + +\subsubsection{blackarch-threat-model} +Packages that would be used for reporting/recording the +threat model outlined in a particular scenario. + +Voorbeelden: magictree + +\subsubsection{blackarch-tunnel} +Packages that are used to tunnel network traffic on a given +network. + +Voorbeelden: ctunnel, iodine, ptunnel + +\subsubsection{blackarch-unpacker} +Packages that are used to extract pre-packed malware from an +executable. + +Voorbeelden: js-beautify + +\subsubsection{blackarch-voip} +Packages that operate on voip programs and protocols. + +Voorbeelden: iaxflood, rtp-flood, teardown + +\subsubsection{blackarch-webapp} +Packages that operate on internet-facing applications. + +Voorbeelden: metoscan, whatweb, zaproxy + +\subsubsection{blackarch-windows} +This group is for any native Windows package that runs via wine. + +Voorbeelden: 3proxy-win32, pwdump, winexe + +\subsubsection{blackarch-wireless} +Packages that operates on wireless networks on any level. + +Voorbeelden: airpwn, mdk3, wiffy + +\section{Repository structure} +You can find the main BlackArch git repo here: +\href{https://github.com/BlackArch/blackarch}{https://github.com/BlackArch/blackarch}. +There are also several secondary repos here: +\href{https://github.com/BlackArch}{https://github.com/BlackArch}. + +Within the main git repo, there are three important directories: + +\begin{itemize} +\item docs - Documentation. +\item packages - PKGBUILD files. +\item scripts - Useful little scripts. +\end{itemize} + +\subsection{Scripts} +Here is a reference for scripts in the \verb|scripts/| directory: + +\begin{itemize} +\item baaur - Soon, this will upload packages to the AUR. +\item babuild - Build a package. +\item bachroot - Manage a chroot for testing. +\item baclean - Clean old .pkg.tar.xz files from the package repo. +\item baconflict - Soon this will replace \verb|scripts/conflicts|. +\item bad-files - Find bad files in built packages. +\item balock - Obtain or release the package repo lock. +\item banotify - Notify IRC about package pushes. +\item barelease - Release packages to the package repo. +\item baright - Print the BlackArch copyright info. +\item basign - Sign packages. +\item basign-key - Sign a key. +\item blackman - This behaves sort of like pacman but builds from git (not to be + confused with nrz's Blackman). +\item check-groups - Check groups. +\item checkpkgs - Check packages for errors. +\item conflicts - Check for file conflicts. +\item dbmod - Modify a package database. +\item depth-list - Create a list sorted by dependency depth. +\item deptree - Create a dependency tree, listing only blackarch-provided packages. +\item get-blackarch-deps - Get a list of blackarch dependencies for a package. +\item get-official - Get official packages for release. +\item list-loose-packages - List packages that are not in groups and are not + dependencies for other packages. +\item list-needed - List missing dependencies. +\item list-removed - List packages that are in the package repo but not in git. +\item list-tools - List tools. +\item outdated - Look for packages that are out-dated in the package repo + relative to the git repo. +\item pkgmod - Modify a build package. +\item pkgrel - Increment pkgrel in a package. +\item prep - Clean up a PKGBUILD file's style and find errors. +\item sitesync - Sync between a local copy of the package repo and a remote copy. +\item size-hunt - Hunt for large packages. +\item source-backup - Backup package source files. +\end{itemize} + +\section{Contributing to repository} +This section shows you how to contribute to the BlackArch Linux project. We +accept pull requests of all sizes, from tiny typo fixes to new packages.\\For +help, suggestions, or questions feel free to contact us. +\\\\ +Everyone is welcome to contribute. All contributions are appreciated. + +\subsection{Required tutorials} +Please read the following tutorials before contributing: +\begin{itemize} +\item +\href{https://wiki.archlinux.org/index.php/Arch\_Packaging\_Standards)}{Arch +Packaging Standards} +\item \href{https://wiki.archlinux.org/index.php/Creating\_Packages}{Creating +Packages} +\item \href{https://wiki.archlinux.org/index.php/PKGBUILD}{PKGBUILD} +\item \href{https://wiki.archlinux.org/index.php/Makepkg}{Makepkg} +\end{itemize} + +\subsection{Steps for contributing} +In order to submit your changes to the BlackArchLinux project, follow these +steps: +\begin{enumerate} +\item Fork the repository from +\url{https://github.com/BlackArch/blackarch} +\item Hack the necessary files, (e.g. PKGBUILD, .patch files, etc). +\item Commit your changes. +\item Push your changes. +\item Ask us to merge in your changes, preferably through a pull request. +\end{enumerate} + +\subsection{Example} +The following example demonstrates submitting a new package to the BlackArch +project. We use \href{https://github.com/Jguer/yay}{yay} +(you can use pacaur as well) to fetch a pre-existing PKGBUILD file for +\textbf{nfsshell} from the \href{https://aur.archlinux.org/}{AUR} and adjust it +according to our needs. + +\subsubsection{Fetch PKGBUILD} +Fetch the \textit{PKGBUILD} file using yay or pacaur: +\begin{lstlisting} + user@blackarchlinux $ yay -G nfsshell + ==> Download nfsshell sources + x LICENSE + x PKGBUILD + x gcc.patch + user@blackarchlinux $ cd nfsshell/ +\end{lstlisting} + +\subsubsection{Clean up PKGBUILD} +Clean up the \textit{PKGBUILD} file and save some time: +\begin{lstlisting} + user@blackarchlinux nfsshell $ ./blackarch/scripts/prep PKGBUILD + cleaning 'PKGBUILD'... + expanding tabs... + removing vim modeline... + removing id comment... + removing contributor and maintainer comments... + squeezing extra blank lines... + removing '|| return'... + removing leading blank line... + removing $pkgname... + removing trailing whitespace... +\end{lstlisting} + +\subsubsection{Adjust PKGBUILD} +Adjust the \textit{PKGBUILD} file: +\begin{lstlisting} + user@blackarchlinux nfsshell $ vi PKGBUILD +\end{lstlisting} + +\subsubsection{Build the package} +Build the package: +\begin{lstlisting}user@blackarchlinux nfsshell $ makepkg -sf +==> Making package: nfsshell 19980519-1 (Mon Dec 2 17:23:51 CET 2013) +==> Checking runtime dependencies... +==> Checking buildtime dependencies... +==> Retrieving sources... +-> Downloading nfsshell.tar.gz... +% Total % Received % Xferd Average Speed Time Time Time +CurrentDload Upload Total Spent Left Speed100 29213 100 29213 0 +0 48150 0 --:--:-- --:--:-- --:--:-- 48206 +-> Found gcc.patch +-> Found LICENSE +... + +... +==> Leaving fakeroot environment. +==> Finished making: nfsshell 19980519-1 (Mon Dec 2 17:23:53 CET 2013) +\end{lstlisting} + +\subsubsection{Install and test the package} +Install and test the package: +\begin{lstlisting} + user@blackarchlinux nfsshell $ pacman -U nfsshell-19980519-1-x86_64.pkg.tar.xz + user@blackarchlinux nfsshell $ nfsshell # test it +\end{lstlisting} + +\subsubsection{Add, commit and push package} +Add, commit and push the package +\begin{lstlisting}user@blackarchlinux nfsshell $ cd /blackarchlinux/packages +user@blackarchlinux ~/blackarchlinux/packages $ mv ~/nfsshell . +user@blackarchlinux ~/blackarchlinux/packages $ git commit -am nfsshell && git push +\end{lstlisting} + +\subsubsection{Create a pull request} +Create a pull request on \href{https://github.com/}{github.com} +\begin{lstlisting} + firefox https://github.com//blackarchlinux +\end{lstlisting} + +\subsubsection{Adding a remote for upstream} +A smart thing to do if you're working upstream and on a fork is to pull your own fork and add the main ba repo as a remote +\begin{lstlisting} + user@blackarchlinux ~/blackarchlinux $ git remote -v + origin (fetch) + origin (push) + user@blackarchlinux ~/blackarchlinux $ git remote add upstream https://github.com/blackarch/blackarch + user@blackarchlinux ~/blackarchlinux $ git remote -v + origin (fetch) + origin (push) + upstream https://github.com/blackarch/blackarch (fetch) + upstream https://github.com/blackarch/blackarch (push) +\end{lstlisting} + +By default, git should push straight to origin, but make sure your git config is +configured correctly. This won't be an issue unless you have commit rights as +you won't be able to push upstream without them. + +If you do have the ability to commit, you might have more success using +\textit{git@github.com:blackarch/blackarch.git} but it's up to you. + +\subsection{Requests} +\begin{enumerate} +\item Don't add \textbf{Maintainer} or \textbf{Contributor} comments to +\textit{PKGBUILD} files. Add maintainer and contributor names to the +AUTHORS section of BlackArch guide. +\item For the sake of consistency, please follow the general style of the other +\textit{PKGBUILD} files in the repo and use two-space indentation. +\end{enumerate} + +\subsection{General tips} +\href{http://wiki.archlinux.org/index.php/Namcap}{namcap} can check packages for +errors. + +%------------------% +% Chapter 4 % +%------------------% + +\chapter{Tools Guide} +Coming soon... + +\section{Coming Soon} +Coming soon... + +%%% APPENDIX %%% +\appendix +\include{latex/appendix-en} + +\end{document} + +%%% EOF %%%