mirror of
https://github.com/zeek/zeek.git
synced 2025-10-10 10:38:20 +00:00
Remove "contents" Sphinx directive usages
Seems redundant: same info is always available in RTD theme's floating sidebar.
This commit is contained in:
Jon Siwek
parent
a46967bad8
commit
5ebe47ec23
23 changed files with 0 additions and 53 deletions
|
|
@ -5,8 +5,6 @@
|
|||
Cluster Configuration
|
||||
=====================
|
||||
|
||||
.. contents::
|
||||
|
||||
A *Bro Cluster* is a set of systems jointly analyzing the traffic of
|
||||
a network link in a coordinated fashion. You can operate such a setup from
|
||||
a central manager system easily using BroControl because BroControl
|
||||
|
|
|
|||
|
|
@ -29,8 +29,6 @@ Broker-Enabled Communication/Cluster Framework
|
|||
also gives examples of Broker and the new cluster framework that
|
||||
show off all the new features and capabilities.
|
||||
|
||||
.. contents::
|
||||
|
||||
Porting Guide
|
||||
=============
|
||||
|
||||
|
|
|
|||
|
|
@ -14,10 +14,6 @@ ability to specify input files to enable changing the value of options at
|
|||
runtime, a couple of functions, and a log file "config.log"
|
||||
which contains information about every change to option values.
|
||||
|
||||
|
||||
.. contents::
|
||||
|
||||
|
||||
Introduction
|
||||
------------
|
||||
|
||||
|
|
|
|||
|
|
@ -21,8 +21,6 @@ File Analysis
|
|||
provide analysis specifically for files that is analogous to the
|
||||
analysis Bro provides for network connections.
|
||||
|
||||
.. contents::
|
||||
|
||||
File Lifecycle Events
|
||||
=====================
|
||||
|
||||
|
|
|
|||
|
|
@ -17,8 +17,6 @@ GeoLocation
|
|||
software, and then install the GeoLite2 city database before building
|
||||
Bro.
|
||||
|
||||
.. contents::
|
||||
|
||||
Install libmaxminddb
|
||||
--------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -15,8 +15,6 @@ Input Framework
|
|||
worthwhile to take a look at the unit tests in
|
||||
``testing/btest/scripts/base/frameworks/input/``.
|
||||
|
||||
.. contents::
|
||||
|
||||
Reading Data into Tables
|
||||
========================
|
||||
|
||||
|
|
|
|||
|
|
@ -14,8 +14,6 @@ Logging To and Reading From SQLite Databases
|
|||
they can, for example, be used to make data that changes regularly available
|
||||
to Bro on a continuing basis.
|
||||
|
||||
.. contents::
|
||||
|
||||
Warning
|
||||
=======
|
||||
|
||||
|
|
|
|||
|
|
@ -12,8 +12,6 @@ Logging Framework
|
|||
logged. This document describes how logging can be customized and
|
||||
extended.
|
||||
|
||||
.. contents::
|
||||
|
||||
Terminology
|
||||
===========
|
||||
|
||||
|
|
|
|||
|
|
@ -17,8 +17,6 @@ NetControl Framework
|
|||
it can be used in practice, it might be worthwhile to take a look at
|
||||
the unit tests.
|
||||
|
||||
.. contents::
|
||||
|
||||
NetControl Architecture
|
||||
=======================
|
||||
|
||||
|
|
|
|||
|
|
@ -14,8 +14,6 @@ Notice Framework
|
|||
alarm emails. This page gives an introduction into writing such a notice
|
||||
policy.
|
||||
|
||||
.. contents::
|
||||
|
||||
Overview
|
||||
--------
|
||||
|
||||
|
|
|
|||
|
|
@ -14,9 +14,6 @@ Signature Framework
|
|||
other NIDS. This page gives a brief overview on Bro's signatures
|
||||
and covers some of their technical subtleties.
|
||||
|
||||
.. contents::
|
||||
:depth: 2
|
||||
|
||||
Basics
|
||||
======
|
||||
|
||||
|
|
|
|||
|
|
@ -17,8 +17,6 @@ Summary Statistics
|
|||
data sets and making them measurable in practice on large clustered and
|
||||
non-clustered Bro deployments.
|
||||
|
||||
.. contents::
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@
|
|||
Detailed Version History
|
||||
========================
|
||||
|
||||
.. contents::
|
||||
|
||||
---
|
||||
Bro
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@
|
|||
Cross Compiling Bro
|
||||
===================
|
||||
|
||||
.. contents::
|
||||
|
||||
Prerequisites
|
||||
=============
|
||||
|
||||
|
|
|
|||
|
|
@ -12,8 +12,6 @@
|
|||
Installing Bro
|
||||
==============
|
||||
|
||||
.. contents::
|
||||
|
||||
Prerequisites
|
||||
=============
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@
|
|||
Release Notes
|
||||
=============
|
||||
|
||||
.. contents::
|
||||
|
||||
.. include:: NEWS.rst
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@
|
|||
Introduction
|
||||
============
|
||||
|
||||
.. contents::
|
||||
|
||||
Overview
|
||||
--------
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@
|
|||
Bro Logging
|
||||
===========
|
||||
|
||||
.. contents::
|
||||
|
||||
Once Bro has been deployed in an environment and monitoring live
|
||||
traffic, it will, in its default configuration, begin to produce
|
||||
human-readable ASCII logs. Each log file, produced by Bro's
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@
|
|||
Quick Start Guide
|
||||
=================
|
||||
|
||||
.. contents::
|
||||
|
||||
Bro works on most modern, Unix-based systems and requires no custom
|
||||
hardware. It can be downloaded in either pre-built binary package or
|
||||
source code forms. See :ref:`installing-bro` for instructions on how to
|
||||
|
|
|
|||
|
|
@ -1,9 +1,6 @@
|
|||
File Analyzers
|
||||
==============
|
||||
|
||||
.. contents::
|
||||
:depth: 2
|
||||
|
||||
.. bro:type:: Files::Tag
|
||||
|
||||
:Type: :bro:type:`enum`
|
||||
|
|
|
|||
|
|
@ -1,9 +1,6 @@
|
|||
Protocol Analyzers
|
||||
==================
|
||||
|
||||
.. contents::
|
||||
:depth: 2
|
||||
|
||||
.. bro:type:: Analyzer::Tag
|
||||
|
||||
:Type: :bro:type:`enum`
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@
|
|||
Writing Bro Scripts
|
||||
===================
|
||||
|
||||
.. contents::
|
||||
|
||||
Understanding Bro Scripts
|
||||
=========================
|
||||
|
||||
|
|
|
|||
|
|
@ -260,8 +260,6 @@ void ProtoAnalyzerTarget::DoCreateAnalyzerDoc(FILE* f) const
|
|||
{
|
||||
fprintf(f, "Protocol Analyzers\n");
|
||||
fprintf(f, "==================\n\n");
|
||||
fprintf(f, ".. contents::\n");
|
||||
fprintf(f, " :depth: 2\n\n");
|
||||
|
||||
WriteAnalyzerTagDefn(f, "Analyzer");
|
||||
|
||||
|
|
@ -288,8 +286,6 @@ void FileAnalyzerTarget::DoCreateAnalyzerDoc(FILE* f) const
|
|||
{
|
||||
fprintf(f, "File Analyzers\n");
|
||||
fprintf(f, "==============\n\n");
|
||||
fprintf(f, ".. contents::\n");
|
||||
fprintf(f, " :depth: 2\n\n");
|
||||
|
||||
WriteAnalyzerTagDefn(f, "Files");
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue