{"id":1296,"date":"2017-03-21T16:46:37","date_gmt":"2017-03-21T20:46:37","guid":{"rendered":"https:\/\/easy-admin.ca\/?p=1296"},"modified":"2024-03-28T13:40:50","modified_gmt":"2024-03-28T17:40:50","slug":"install-bro-on-centos-7-x6-x","status":"publish","type":"post","link":"https:\/\/easy-admin.ca\/index.php\/2017\/03\/21\/install-bro-on-centos-7-x6-x\/","title":{"rendered":"Install Bro on CentOS 7.X\/6.X"},"content":{"rendered":"<div class=\"entry-content\">\n<h2><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-1663\" src=\"https:\/\/easy-admin.ca\/wp-content\/uploads\/2017\/03\/bro-jpeg.jpg\" alt=\"\" width=\"500\" height=\"378\" srcset=\"https:\/\/easy-admin.ca\/wp-content\/uploads\/2017\/03\/bro-jpeg.jpg 500w, https:\/\/easy-admin.ca\/wp-content\/uploads\/2017\/03\/bro-jpeg-300x227.jpg 300w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/h2>\n<h2>Required Dependencies<\/h2>\n<p>Bro requires following dependancies to work properly<\/p>\n<ul class=\"simple\">\n<li>Libpcap \u00a0 (Package name=libpcap-devel)<\/li>\n<li>OpenSSL libraries (openssl-devel)<\/li>\n<li>BIND8 library (already installed in centos)<\/li>\n<li>Libz (already install in centos)<\/li>\n<li>Bash (for BroControl)<\/li>\n<li>Python (for BroControl) (python-devel)<\/li>\n<\/ul>\n<p>To build Bro from source following addition dependancies are required<\/p>\n<ul class=\"simple\">\n<li>CMake 2.6.3 or greater (<a class=\"reference external\" href=\"http:\/\/www.cmake.org\/\">http:\/\/www.cmake.org<\/a>)(cmake)<\/li>\n<li>Make(make)<\/li>\n<li>C\/C++ compiler(gcc-c++, gcc)<\/li>\n<li>SWIG (<a class=\"reference external\" href=\"http:\/\/www.swig.org\/\">http:\/\/www.swig.org<\/a>)(swig)<\/li>\n<li>Bison (GNU Parser Generator)(bison)<\/li>\n<li>Flex (Fast Lexical Analyzer)(flex)<\/li>\n<li>Libpcap headers (<a class=\"reference external\" href=\"http:\/\/www.tcpdump.org\/\">http:\/\/www.tcpdump.org<\/a>)(libpcap-devel)<\/li>\n<li>OpenSSL headers (<a class=\"reference external\" href=\"http:\/\/www.openssl.org\/\">http:\/\/www.openssl.org<\/a>)(openssl-devel)<\/li>\n<li>zlib headers(zlib-devel)<\/li>\n<li>Perl (perl)<\/li>\n<\/ul>\n<p>Let us install all of above dependancies first<\/p>\n<pre>sudo yum install cmake make gcc gcc-c++ flex bison libpcap-devel openssl-devel python-devel swig zlib-devel perl<\/pre>\n<h2>Optional Dependencies<\/h2>\n<p>Following are the optional dependancies, bro can make use of them if they are availble at build time<\/p>\n<ul class=\"simple\">\n<li>LibGeoIP (for geolocating IP addresses)<\/li>\n<li>sendmail (enables Bro and BroControl to send mail)<\/li>\n<li>gawk (enables all features of bro-cut)<\/li>\n<li>curl (used by a Bro script that implements active HTTP)<\/li>\n<li>gperftools (tcmalloc is used to improve memory and CPU usage)<\/li>\n<li>ipsumdump (for trace-summary; <a class=\"reference external\" href=\"http:\/\/www.cs.ucla.edu\/%7Ekohler\/ipsumdump\">http:\/\/www.cs.ucla.edu\/~kohler\/ipsumdump<\/a>)<\/li>\n<li>Ruby executable, library, and headers (for Broccoli Ruby bindings)<\/li>\n<\/ul>\n<h3>LibgeoIP<\/h3>\n<p>During the process of creating policy scripts the need may arise to find the geographic location for an IP address. Bro has support for the <a class=\"reference external\" href=\"http:\/\/www.maxmind.com\/app\/c\">GeoIP library<\/a> at the policy script level beginning with release 1.3 to account for this need. To use this functionality, you need to first install the libGeoIP software, and then install the GeoLite city database before building Bro.<\/p>\n<p>Libgeoip allows bro to<\/p>\n<pre>sudo yum install GeoIP-devel<\/pre>\n<p>A country database for GeoIPLite is included when you do the C API install, but for Bro, we are using the city database which includes cities and regions in addition to countries.<\/p>\n<p><a class=\"reference external\" href=\"http:\/\/www.maxmind.com\/app\/geolitecity\">Download<\/a> the GeoLite city binary database.<\/p>\n<pre>wget http:\/\/geolite.maxmind.com\/download\/geoip\/database\/GeoLiteCity.dat.gz\n#unzip the database\ngunzip GeoLiteCity.dat.gz<\/pre>\n<p>move data base to required diretory<\/p>\n<pre> sudo mv GeoLiteCity.dat \/usr\/share\/GeoIP\/GeoIPCity.dat<\/pre>\n<h3>Install gawk<\/h3>\n<p>GNU implementation of famous\u00a0<a href=\"https:\/\/www.gnu.org\/software\/gawk\/\">awk<\/a> utility<\/p>\n<pre>sudo yum install gawk<\/pre>\n<h3>Install gperftools(google performance tools)<\/h3>\n<p><a href=\"https:\/\/code.google.com\/p\/gperftools\/wiki\/GooglePerformanceTools\">Gperftools<\/a> is a collection of a high-performance multi-threaded malloc() implementation, plus some pretty nifty performance analysis tools<\/p>\n<pre>sudo yum install gperftools<\/pre>\n<h3>Ipsumdump<\/h3>\n<p>The <a href=\"http:\/\/www.read.seas.harvard.edu\/%7Ekohler\/ipsumdump\/\">ipsumdump<\/a> program reads IP packets from one or more data sources, then summarizes those packets into a line-based ASCII file. The resulting summary dump is easy to process with text-based tools<\/p>\n<pre>#Download the latest version from <a href=\"http:\/\/www.read.seas.harvard.edu\/%7Ekohler\/ipsumdump\/\">here <\/a>\nwget http:\/\/www.read.seas.harvard.edu\/~kohler\/ipsumdump\/ipsumdump-1.85.tar.gz\ntar -xvf ipsumdump-1.85.tar.gz\ncd ipsumdump-1.85\n.\/configure --prefix=\/usr\/\nmake \nsudo make install<\/pre>\n<h2>Install Bro<\/h2>\n<p>Download the latest version from <a href=\"https:\/\/www.bro.org\/download\/index.html\">here<\/a><\/p>\n<pre>wget https:\/\/www.bro.org\/downloads\/release\/bro-2.5.tar.gz\ntar -xvf bro-2.5.tar.gz\n\nNow change to this directory \n\/bro\/bro-2.5   assuming you created a \/bro\/ and install in this directory!\n.\/configure\nmake\nsudo make install<\/pre>\n<p><em><strong>The installation will take a while!<\/strong><\/em><\/p>\n<p>by default bro will be install to <b><i>\/usr\/local\/bro\/bin<\/i><\/b><\/p>\n<p>Modifiy you PATH environment variable to include bro binaries<\/p>\n<pre>export PATH=\/usr\/local\/bro\/bin:$PATH<\/pre>\n<p>To make changes permanent add above line to <strong><em>~\/.bashrc<\/em><\/strong> file<\/p>\n<div id=\"a-minimal-starting-configuration\" class=\"section\">\n<h3>A Minimal Starting Configuration<\/h3>\n<p>These are the basic configuration changes to make for a minimal BroControl installation that will manage a single Bro instance on the <code class=\"docutils literal\"><span class=\"pre\">localhost<\/span><\/code>:<\/p>\n<ol class=\"arabic simple\">\n<li>In <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/etc\/node.cfg<\/span><\/code>, set the right interface to monitor.<\/li>\n<li>In <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/etc\/networks.cfg<\/span><\/code>, comment out the default settings and add the networks that Bro will consider local to the monitored environment.<\/li>\n<li>In <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/etc\/broctl.cfg<\/span><\/code>, change the <code class=\"docutils literal\"><span class=\"pre\">MailTo<\/span><\/code> email address to a desired recipient and the <code class=\"docutils literal\"><span class=\"pre\">LogRotationInterval<\/span><\/code> to a desired log archival frequency.<\/li>\n<\/ol>\n<p>Now start the BroControl shell like:<\/p>\n<div class=\"pygments\">\n<pre>broctl\n<\/pre>\n<\/div>\n<p>Since this is the first-time use of the shell, perform an initial installation of the BroControl configuration:<\/p>\n<div class=\"pygments\">\n<pre><span class=\"o\">[<\/span>BroControl<span class=\"o\">]<\/span> &gt; install\n<\/pre>\n<\/div>\n<p>Then start up a Bro instance:<\/p>\n<div class=\"pygments\">\n<pre><span class=\"o\">[<\/span>BroControl<span class=\"o\">]<\/span> &gt; start\n<\/pre>\n<\/div>\n<p>If there are errors while trying to start the Bro instance, you can can view the details with the <code class=\"docutils literal\"><span class=\"pre\">diag<\/span><\/code> command. If started successfully, the Bro instance will begin analyzing traffic according to a default policy and output the results in <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/logs<\/span><\/code>.<\/p>\n<div class=\"admonition note\">\n<p class=\"first admonition-title\">Note<\/p>\n<p class=\"last\">The user starting BroControl needs permission to capture network traffic. If you are not root, you may need to grant further privileges to the account you\u2019re using; see the <a class=\"reference external\" href=\"https:\/\/www.bro.org\/documentation\/faq.html\">FAQ<\/a>. Also, if it looks like Bro is not seeing any traffic, check out the FAQ entry on checksum offloading.<\/p>\n<\/div>\n<p>You can leave it running for now, but to stop this Bro instance you would do:<\/p>\n<div class=\"pygments\">\n<pre><span class=\"o\">[<\/span>BroControl<span class=\"o\">]<\/span> &gt; stop\n<\/pre>\n<\/div>\n<\/div>\n<div id=\"browsing-log-files\" class=\"section\">\n<h3>Browsing Log Files<\/h3>\n<p>By default, logs are written out in human-readable (ASCII) format and data is organized into columns (tab-delimited). Logs that are part of the current rotation interval are accumulated in <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/logs\/current\/<\/span><\/code> (if Bro is not running, the directory will be empty). For example, the <code class=\"docutils literal\"><span class=\"pre\">http.log<\/span><\/code> contains the results of Bro HTTP protocol analysis. Here are the first few columns of <code class=\"docutils literal\"><span class=\"pre\">http.log<\/span><\/code>:<\/p>\n<div class=\"highlight-default\">\n<div class=\"highlight\">\n<pre><span class=\"c1\"># ts          uid          orig_h        orig_p  resp_h         resp_p<\/span>\n<span class=\"mf\">1311627961.8<\/span>  <span class=\"n\">HSH4uV8KVJg<\/span>  <span class=\"mf\">192.168<\/span><span class=\"o\">.<\/span><span class=\"mf\">1.100<\/span> <span class=\"mi\">52303<\/span>   <span class=\"mf\">192.150<\/span><span class=\"o\">.<\/span><span class=\"mf\">187.43<\/span> <span class=\"mi\">80<\/span><\/pre>\n<\/div>\n<\/div>\n<p>Logs that deal with analysis of a network protocol will often start like this: a timestamp, a unique connection identifier (UID), and a connection 4-tuple (originator host\/port and responder host\/port). The UID can be used to identify all logged activity (possibly across multiple log files) associated with a given connection 4-tuple over its lifetime.<\/p>\n<p>The remaining columns of protocol-specific logs then detail the protocol-dependent activity that\u2019s occurring. E.g. <code class=\"docutils literal\"><span class=\"pre\">http.log<\/span><\/code>\u2018s next few columns (shortened for brevity) show a request to the root of Bro website:<\/p>\n<div class=\"highlight-default\">\n<div class=\"highlight\">\n<pre><span class=\"c1\"># method   host         uri  referrer  user_agent<\/span>\n<span class=\"n\">GET<\/span>        <span class=\"n\">bro<\/span><span class=\"o\">.<\/span><span class=\"n\">org<\/span>  <span class=\"o\">\/<\/span>    <span class=\"o\">-<\/span>         <span class=\"o\">&lt;...&gt;<\/span><span class=\"n\">Chrome<\/span><span class=\"o\">\/<\/span><span class=\"mf\">12.0<\/span><span class=\"o\">.<\/span><span class=\"mf\">742.122<\/span><span class=\"o\">&lt;...&gt;<\/span><\/pre>\n<\/div>\n<\/div>\n<p>Some logs are worth explicit mention:<\/p>\n<blockquote>\n<div>\n<dl class=\"docutils\">\n<dt><code class=\"docutils literal\"><span class=\"pre\">conn.log<\/span><\/code><\/dt>\n<dd>Contains an entry for every connection seen on the wire, with basic properties such as time and duration, originator and responder IP addresses, services and ports, payload size, and much more. This log provides a comprehensive record of the network\u2019s activity.<\/dd>\n<dt><code class=\"docutils literal\"><span class=\"pre\">notice.log<\/span><\/code><\/dt>\n<dd>Identifies specific activity that Bro recognizes as potentially interesting, odd, or bad. In Bro-speak, such activity is called a \u201cnotice\u201d.<\/dd>\n<\/dl>\n<\/div>\n<\/blockquote>\n<p>By default, <code class=\"docutils literal\"><span class=\"pre\">BroControl<\/span><\/code> regularly takes all the logs from <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/logs\/current<\/span><\/code> and archives\/compresses them to a directory named by date, e.g. <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/logs\/2011-10-06<\/span><\/code>. The frequency at which this is done can be configured via the <code class=\"docutils literal\"><span class=\"pre\">LogRotationInterval<\/span><\/code> option in <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/etc\/broctl.cfg<\/span><\/code><\/p>\n<div class=\"grid_9\">\n<div class=\"body\">\n<div id=\"quick-start-guide\" class=\"section\">\n<div id=\"bro-as-a-command-line-utility\" class=\"section\">\n<h2><a class=\"toc-backref\" href=\"https:\/\/www.bro.org\/sphinx-git\/quickstart\/index.html#id9\">Bro as a Command-Line Utility<\/a><\/h2>\n<p>If you prefer not to use BroControl (e.g. don\u2019t need its automation and management features), here\u2019s how to directly control Bro for your analysis activities from the command line for both live traffic and offline working from traces.<\/p>\n<div id=\"monitoring-live-traffic\" class=\"section\">\n<h3><a class=\"toc-backref\" href=\"https:\/\/www.bro.org\/sphinx-git\/quickstart\/index.html#id10\">Monitoring Live Traffic<\/a><\/h3>\n<p>Analyzing live traffic from an interface is simple:<\/p>\n<div class=\"pygments\">\n<pre>bro -i en0 &lt;list of scripts to load&gt;\n<\/pre>\n<\/div>\n<p><code class=\"docutils literal\"><span class=\"pre\">en0<\/span><\/code> can be replaced by the interface of your choice and for the list of scripts, you can just use \u201call\u201d for now to perform all the default analysis that\u2019s available.<\/p>\n<p>Bro will output log files into the working directory.<\/p>\n<div class=\"admonition note\">\n<p class=\"first admonition-title\">Note<\/p>\n<p class=\"last\">The <a class=\"reference external\" href=\"https:\/\/www.bro.org\/documentation\/faq.html\">FAQ<\/a> entries about capturing as an unprivileged user and checksum offloading are particularly relevant at this point.<\/p>\n<\/div>\n<p>To use the site-specific <code class=\"docutils literal\"><span class=\"pre\">local.bro<\/span><\/code> script, just add it to the command-line:<\/p>\n<div class=\"pygments\">\n<pre>bro -i en0 local\n<\/pre>\n<\/div>\n<p>This will cause Bro to print a warning about lacking the <code class=\"docutils literal\"><span class=\"pre\">Site::local_nets<\/span><\/code> variable being configured. You can supply this information at the command line like this (supply your \u201clocal\u201d subnets in place of the example subnets):<\/p>\n<div class=\"pygments\">\n<pre>bro -r mypackets.trace local <span class=\"s2\">\"Site::local_nets += { 1.2.3.0\/24, 5.6.7.0\/24 }\"<\/span><\/pre>\n<\/div>\n<\/div>\n<div id=\"reading-packet-capture-pcap-files\" class=\"section\">\n<h3><a class=\"toc-backref\" href=\"https:\/\/www.bro.org\/sphinx-git\/quickstart\/index.html#id11\">Reading Packet Capture (pcap) Files<\/a><\/h3>\n<p>Capturing packets from an interface and writing them to a file can be done like this:<\/p>\n<div class=\"pygments\">\n<pre>sudo tcpdump -i en0 -s <span class=\"m\">0<\/span> -w mypackets.trace\n<\/pre>\n<\/div>\n<p>Where <code class=\"docutils literal\"><span class=\"pre\">en0<\/span><\/code> can be replaced by the correct interface for your system as shown by e.g. <code class=\"docutils literal\"><span class=\"pre\">ifconfig<\/span><\/code>. (The <code class=\"docutils literal\"><span class=\"pre\">-s<\/span> <span class=\"pre\">0<\/span><\/code> argument tells it to capture whole packets; in cases where it\u2019s not supported use <code class=\"docutils literal\"><span class=\"pre\">-s<\/span> <span class=\"pre\">65535<\/span><\/code> instead).<\/p>\n<p>After a while of capturing traffic, kill the <code class=\"docutils literal\"><span class=\"pre\">tcpdump<\/span><\/code> (with ctrl-c), and tell Bro to perform all the default analysis on the capture which primarily includes :<\/p>\n<div class=\"pygments\">\n<pre>bro -r mypackets.trace\n<\/pre>\n<\/div>\n<p>Bro will output log files into the working directory.<\/p>\n<p>If you are interested in more detection, you can again load the <code class=\"docutils literal\"><span class=\"pre\">local<\/span><\/code> script that we include as a suggested configuration:<\/p>\n<div class=\"pygments\">\n<pre>bro -r mypackets.trace local\n<\/pre>\n<\/div>\n<\/div>\n<div id=\"telling-bro-which-scripts-to-load\" class=\"section\">\n<h3><a class=\"toc-backref\" href=\"https:\/\/www.bro.org\/sphinx-git\/quickstart\/index.html#id12\">Telling Bro Which Scripts to Load<\/a><\/h3>\n<p>A command-line invocation of Bro typically looks like:<\/p>\n<div class=\"pygments\">\n<pre>bro &lt;options&gt; &lt;policies...&gt;\n<\/pre>\n<\/div>\n<p>Where the last arguments are the specific policy scripts that this Bro instance will load. These arguments don\u2019t have to include the <code class=\"docutils literal\"><span class=\"pre\">.bro<\/span><\/code> file extension, and if the corresponding script resides under the default installation path, <code class=\"docutils literal\"><span class=\"pre\">$PREFIX\/share\/bro<\/span><\/code>, then it requires no path qualification. Further, a directory of scripts can be specified as an argument to be loaded as a \u201cpackage\u201d if it contains a <code class=\"docutils literal\"><span class=\"pre\">__load__.bro<\/span><\/code> script that defines the scripts that are part of the package.<\/p>\n<p>This example does all of the base analysis (primarily protocol logging) and adds SSL certificate validation.<\/p>\n<div class=\"pygments\">\n<pre>bro -r mypackets.trace protocols\/ssl\/validate-certs\n<\/pre>\n<\/div>\n<p>You might notice that a script you load from the command line uses the <code class=\"docutils literal\"><span class=\"pre\">@load<\/span><\/code> directive in the Bro language to declare dependence on other scripts. This directive is similar to the <code class=\"docutils literal\"><span class=\"pre\">#include<\/span><\/code> of C\/C++, except the semantics are, \u201cload this script if it hasn\u2019t already been loaded.\u201d<\/p>\n<div class=\"admonition note\">\n<p class=\"first admonition-title\">Note<\/p>\n<p class=\"last\">If one wants Bro to be able to load scripts that live outside the default directories in Bro\u2019s installation root, the <code class=\"docutils literal\"><span class=\"pre\">BROPATH<\/span><\/code> environment variable will need to be extended to include all the directories that need to be searched for scripts. See the default search path by doing <code class=\"docutils literal\"><span class=\"pre\">bro<\/span> <span class=\"pre\">--help<\/span><\/code>.<\/p>\n<\/div>\n<\/div>\n<div id=\"running-bro-without-installing\" class=\"section\">\n<h3><a class=\"toc-backref\" href=\"https:\/\/www.bro.org\/sphinx-git\/quickstart\/index.html#id13\">Running Bro Without Installing<\/a><\/h3>\n<p>For developers that wish to run Bro directly from the <code class=\"docutils literal\"><span class=\"pre\">build\/<\/span><\/code> directory (i.e., without performing <code class=\"docutils literal\"><span class=\"pre\">make<\/span> <span class=\"pre\">install<\/span><\/code>), they will have to first adjust <code class=\"docutils literal\"><span class=\"pre\">BROPATH<\/span><\/code> to look for scripts and additional files inside the build directory. Sourcing either <code class=\"docutils literal\"><span class=\"pre\">build\/bro-path-dev.sh<\/span><\/code> or <code class=\"docutils literal\"><span class=\"pre\">build\/bro-path-dev.csh<\/span><\/code> as appropriate for the current shell accomplishes this and also augments your <code class=\"docutils literal\"><span class=\"pre\">PATH<\/span><\/code> so you can use the Bro binary directly:<\/p>\n<div class=\"highlight-default\">\n<div class=\"highlight\">\n<pre><span class=\"o\">.\/<\/span><span class=\"n\">configure<\/span>\n<span class=\"n\">make<\/span>\n<span class=\"n\">source<\/span> <span class=\"n\">build<\/span><span class=\"o\">\/<\/span><span class=\"n\">bro<\/span><span class=\"o\">-<\/span><span class=\"n\">path<\/span><span class=\"o\">-<\/span><span class=\"n\">dev<\/span><span class=\"o\">.<\/span><span class=\"n\">sh<\/span>\n<span class=\"n\">bro<\/span> <span class=\"o\">&lt;<\/span><span class=\"n\">options<\/span><span class=\"o\">&gt;<\/span><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"grid_3 omega\"><strong>Video Tutorial<\/strong><\/div>\n<div class=\"grid_3 omega\"><\/div>\n<\/div>\n<p><iframe loading=\"lazy\" src=\"https:\/\/www.youtube.com\/embed\/RjDItxZprk8\" width=\"600\" height=\"415\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<\/div>\n<div class=\"grid_3 omega\"><em><strong>Have fun!<\/strong><\/em><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Required Dependencies Bro requires following dependancies to work properly Libpcap \u00a0 (Package name=libpcap-devel) OpenSSL libraries (openssl-devel) BIND8 library (already installed in centos) Libz (already install in centos) Bash (for BroControl) Python (for BroControl) (python-devel) To build Bro from source following addition dependancies are required CMake 2.6.3 or greater (http:\/\/www.cmake.org)(cmake) Make(make) C\/C++ compiler(gcc-c++, gcc) SWIG (http:\/\/www.swig.org)(swig) &hellip; <a href=\"https:\/\/easy-admin.ca\/index.php\/2017\/03\/21\/install-bro-on-centos-7-x6-x\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Install Bro on CentOS 7.X\/6.X<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"slim_seo":{"title":"Install Bro on CentOS 7.X\/6.X - HP Server","description":"Required Dependencies Bro requires following dependancies to work properly Libpcap \u00a0 (Package name=libpcap-devel) OpenSSL libraries (openssl-devel) BIND8 librar"},"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1296","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/posts\/1296","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/comments?post=1296"}],"version-history":[{"count":0,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/posts\/1296\/revisions"}],"wp:attachment":[{"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/media?parent=1296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/categories?post=1296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/easy-admin.ca\/index.php\/wp-json\/wp\/v2\/tags?post=1296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}