Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next/20220103/v3 #6744

Merged
merged 13 commits into from Jan 4, 2022
Merged

Next/20220103/v3 #6744

merged 13 commits into from Jan 4, 2022

Commits on Dec 21, 2021

  1. dns: create transaction even if z-bit was set

    It appears that DNS servers will still process a DNS request even if the
    z-bit is set, our parser will fail the transaction. So create the
    transaction, but still set the event.
    
    Ticket OISF#4924
    jasonish committed Dec 21, 2021
    Configuration menu
    Copy the full SHA
    fcbdc30 View commit details
    Browse the repository at this point in the history
  2. dns: Logging of Z-bit

    [Edit by Jason Ish: fix flag bit value]
    
    Ticket OISF#4515
    Odin Jenseg authored and jasonish committed Dec 21, 2021
    Configuration menu
    Copy the full SHA
    dfb6f10 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    0861b66 View commit details
    Browse the repository at this point in the history

Commits on Jan 3, 2022

  1. doc/eve-json-format/dns: Describing Z-bit

    Odin Jenseg authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    2a5d79e View commit details
    Browse the repository at this point in the history
  2. detect: fix app-layer-protocol keyword for HTTP

    Ticket: 4920
    
    Completes commit c8dbe24
    which introduced AppProtoEquals to have a generic
    check for http in signature can mean http1 or http2 in
    traffic.
    
    This commit missed this case, as I only looked for
    git grep "alproto ==" and here we deal with
    alproto_tc and alproto_ts, but not alproto by itself.
    catenacyber authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    bf9bbdd View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    7b20488 View commit details
    Browse the repository at this point in the history
  4. userguide: update references to Suricata website

    Many places were still referencing the old Suricata page.
    Used git grep with replace to update them. Checked that new links work.
    Left old references when they were only documentation examples (for
    output or unittests).
    
    Task#4915
    jufajardini authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    de0ce26 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    6ae80b2 View commit details
    Browse the repository at this point in the history
  6. configure.ac: Support libunwind configuration

    This commit adds support for enabling libunwind -- a library that can be
    used to display stack information.
    
    Libunwind is enabled and used by Suricata if present during
    configuration.  A diagnostic message is displayed if libunwind
    cannot be found.
    jlucovsky authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    303dd29 View commit details
    Browse the repository at this point in the history
  7. error: Add error code for sig-related diagnostics

    This commit adds an error code for the diagnostic code used for
    diagnostic messages following unexpected termination due to signals..
    jlucovsky authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    501c870 View commit details
    Browse the repository at this point in the history
  8. logging: Stacktrace on signal term setting

    This commit adds a configuration setting to enable a stack trace message
    if Suricata receives a signal that terminates execution, such as
    SIGSEGV, SIGABRT.
    jlucovsky authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    163f70b View commit details
    Browse the repository at this point in the history
  9. logging/diag: Enable stacktrace diagnostic if config'd

    This commit adds a signal handler for SIGSEGV when configured. The
    signal handler emits a one line stack trace using SCLogError. The intent
    is to provide diagnostic information in deployments where core files are
    not possible.
    
    The diagnostic message is from the offending thread and includes the
    stack trace; each frame includes the symbol + offset.
    jlucovsky authored and victorjulien committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    7f0f463 View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    93842aa View commit details
    Browse the repository at this point in the history