Package: suricata
Version: 1:8.0.7-1~bpo13+1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

On Debian 13 (Trixie, amd64), upgrading Suricata from 8.0.7 to 8.0.8 from 
official trixie-backports causes APT to propose removing Rspamd, an essential 
component of my production mail infrastructure.

**This is a significant security and package integration problem. I would 
particularly appreciate coordination between the Debian maintainers and Rspamd 
upstream to find a mutually compatible solution, regardless of which package 
ultimately needs to change.**

### 1. Affected packages

- Debian 13 (Trixie), amd64
- Suricata installed: `1:8.0.7-1~bpo13+1`
- Suricata upgrade: `1:8.0.8-1~bpo13+1` from official Debian trixie-backports
- Rspamd: `4.3.0-1~~25c9ecc~~trixie` from the official Rspamd repository
- `libhyperscan5`: `5.4.2-3`
- `libvectorscan5`: `5.4.11-2+b1`

The conflict was originally observed with Rspamd 4.2.3 and remains present with 
Rspamd 4.3.0.

Importantly, Debian's own Rspamd 3.12.1-1 package also depends on 
`libhyperscan5 (>= 5.4.2)` on amd64. Therefore, this is not merely an 
incompatibility caused by using an external Rspamd repository.

### 2. Technical cause

Suricata 8.0.8 was rebuilt against Vectorscan on amd64.

Suricata now depends on:

`libvectorscan5 (>= 5.4.11)`

Rspamd depends on:

`libhyperscan5 (>= 5.4.2)`

However, Debian's `libvectorscan5` declares:

- `Provides: libhyperscan5`
- `Conflicts: libhyperscan5`
- `Replaces: libhyperscan5`

The unversioned `Provides` does not satisfy Rspamd's versioned dependency. The 
two libraries also cannot coexist as currently packaged.

Consequently, APT proposes removing Rspamd when upgrading Suricata. Requesting 
both packages results in an unsatisfiable dependency conflict.

### 3. Reproduction

On Debian 13 amd64 with Rspamd installed:

```sh
apt-cache policy suricata rspamd
apt-get -s -t trixie-backports install suricata
apt-get -s -t trixie-backports install suricata rspamd
dpkg-query -W -f='${Depends}\n' rspamd
apt-cache show libvectorscan5 | grep -E 
'^(Version|Provides|Conflicts|Breaks|Replaces):'
```

The first APT simulation proposes removing Rspamd and libhyperscan5. The second 
fails because the requirements cannot be satisfied simultaneously.

### 4. Security impact

Suricata is an important component of my server's network security 
infrastructure.

Suricata 8.0.8 is explicitly a security release. According to the Open 
Information Security Foundation, it fixes **32 vulnerabilities, including six 
classified as high severity**.

Being unable to install these security fixes without removing the production 
mail filtering service is a significant problem.

Rspamd is also essential to my server. Removing it or permanently moving it to 
a different deployment model solely to work around this dependency conflict 
would introduce additional operational complexity.

I have therefore kept Suricata at 8.0.7, but this is not a satisfactory 
long-term solution.

### 5. Rspamd upstream's position

I reported the problem to Rspamd upstream:

[https://github.com/rspamd/rspamd/issues/6370](https://github.com/rspamd/rspamd/issues/6370)

The issue was closed as "not planned".

In a subsequent comment, Rspamd's lead developer, Vsevolod Stakhov, stated that 
Hyperscan and Vectorscan are not binary-compatible and expressed concerns about 
Vectorscan's development quality. He therefore does not want to replace 
Hyperscan with Vectorscan by default.

His response is available here:

[https://github.com/rspamd/rspamd/issues/6370#issuecomment-6878439420](https://github.com/rspamd/rspamd/issues/6370#issuecomment-6878439420)

This position should be considered before attempting to resolve the issue 
simply by changing dependency metadata.

Notably, Debian's Vectorscan package describes the library as an intended 
API/ABI-compatible replacement for Hyperscan. The apparent disagreement about 
compatibility merits technical clarification between the relevant maintainers.

### 6. Request for coordinated resolution

**I would appreciate it if the Debian Suricata, Rspamd, and, where appropriate, 
Vectorscan maintainers could coordinate with Rspamd upstream to identify a 
technically sound solution.**

I do not have a preference about which project should implement the necessary 
changes.

Potential approaches worth investigating include:

- Building Suricata against Hyperscan on amd64 again, while retaining 
Vectorscan where needed on other architectures.
- Supporting a Vectorscan-based Rspamd build, provided compatibility and 
upstream support can be established.
- Finding another packaging or dependency solution that allows both 
applications to coexist safely.
- Agreeing with Rspamd upstream on a longer-term approach that avoids recurring 
conflicts.

These are possibilities for investigation, not requests for any particular 
implementation.

In particular, I am **not** suggesting that Vectorscan should simply be 
declared a versioned replacement for Hyperscan without verifying binary and 
runtime compatibility.

The desired outcome is straightforward:

**Both Suricata and Rspamd should remain installable and independently 
updatable through APT on Debian 13 amd64, without removing either service.**

Because this currently blocks a Suricata security update, I would appreciate 
coordination between the relevant Debian maintainers and Rspamd upstream rather 
than treating the issue as an isolated problem belonging exclusively to one 
project.

### References

Suricata 8.0.8 security release:

[https://suricata.io/2026/10/29/suricata-8-0-8-released/](https://suricata.io/2026/10/29/suricata-8-0-8-released/)

Debian Suricata 8.0.8 backport:

[https://tracker.debian.org/news/1818626/accepted-suricata-1808-1bpo131-source-into-stable-backports/](https://tracker.debian.org/news/1818626/accepted-suricata-1808-1bpo131-source-into-stable-backports/)

Debian's Rspamd dependencies:

[https://packages.debian.org/trixie/amd64/rspamd](https://packages.debian.org/trixie/amd64/rspamd)

Debian's Vectorscan packaging:

[https://sources.debian.org/src/vectorscan/5.4.11-2/debian/control](https://sources.debian.org/src/vectorscan/5.4.11-2/debian/control)

Rspamd upstream discussion:

[https://github.com/rspamd/rspamd/issues/6370](https://github.com/rspamd/rspamd/issues/6370)

Thank you for looking into this issue.


-- System Information:
Debian Release: 13.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.116+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages suricata depends on:
ii  libbpf1                     1:1.5.0-3
ii  libbsd0                     0.12.2-2
ii  libc6                       2.41-12+deb13u4
ii  libcap-ng0                  0.8.5-4+b1
ii  libevent-2.1-7t64           2.1.13-stable-1~deb13u1
ii  libevent-pthreads-2.1-7t64  2.1.13-stable-1~deb13u1
ii  libgcc-s1                   14.2.0-19
ii  libhiredis1.1.0             1.2.0-6+b3
ii  libhwloc15                  2.12.0-4
ii  libhyperscan5               5.4.2-3
ii  libjansson4                 2.14-2+b3
ii  liblz4-1                    1.10.0-4
ii  libmagic1t64                1:5.46-5
ii  libmaxminddb0               1.12.2-1
ii  libnet1                     1.3+dfsg-2
ii  libnetfilter-log1           1.0.2-4+b1
ii  libnetfilter-queue1         1.0.5-4+b1
ii  libnfnetlink0               1.0.2-3
ii  libnuma1                    2.0.19-1
ii  libpcap0.8t64               1.10.5-2
ii  libpcre2-8-0                10.46-1~deb13u3
ii  librte-eal25                24.11.8-0+deb13u1
ii  librte-ethdev25             24.11.8-0+deb13u1
ii  librte-kvargs25             24.11.8-0+deb13u1
ii  librte-log25                24.11.8-0+deb13u1
ii  librte-mbuf25               24.11.8-0+deb13u1
ii  librte-mempool25            24.11.8-0+deb13u1
ii  librte-net-bond25           24.11.8-0+deb13u1
ii  libunwind8                  1.8.1-0.1
ii  libxdp1                     1.5.4-1
ii  libyaml-0-2                 0.2.5-2
ii  procps                      2:4.0.4-9
ii  python3                     3.13.5-1
ii  zlib1g                      1:1.3.dfsg+really1.3.1-1+deb13u1

Versions of packages suricata recommends:
ii  python3          3.13.5-1
ii  suricata-update  1.3.4-1+deb13u1

Versions of packages suricata suggests:
pn  libtcmalloc-minimal4  <none>

-- Configuration Files:
/etc/logrotate.d/suricata changed:
/var/log/suricata/*.log
/var/log/suricata/*.json
{
        weekly
        rotate 12
        missingok
    delaycompress
        compress
        copytruncate
        sharedscripts
        postrotate
                /usr/bin/kill -HUP `cat /var/run/suricata/suricata.pid 
2>/dev/null`2>/dev/null || true
        endscript
}

/etc/suricata/rules/app-layer-events.rules [file not found]
/etc/suricata/rules/dhcp-events.rules [file not found]
/etc/suricata/rules/files.rules [file not found]
/etc/suricata/rules/ipsec-events.rules [file not found]
/etc/suricata/rules/kerberos-events.rules [file not found]
/etc/suricata/rules/modbus-events.rules [file not found]
/etc/suricata/rules/nfs-events.rules [file not found]
/etc/suricata/rules/ntp-events.rules [file not found]
/etc/suricata/rules/quic-events.rules [file not found]
/etc/suricata/rules/rfb-events.rules [file not found]
/etc/suricata/rules/smb-events.rules [file not found]
/etc/suricata/rules/ssh-events.rules [file not found]
/etc/suricata/suricata.yaml changed:
%YAML 1.1
---
runmode: workers
vars:
  address-groups:
    HOME_NET:       
"[192.168.42.98/32,217.64.151.45/32,93.104.28.218/32,2001:a61:2ac1:4e01:6600:6aff:fe8b:ec8/128,fd22:780c:60ab:0:6600:6aff:fe8b:ec8/128]"
    EXTERNAL_NET:   "!$HOME_NET"
    DNS_SERVERS:    "$HOME_NET"
    HTTP_SERVERS:   "$HOME_NET"
    SMTP_SERVERS:   "$HOME_NET"
    SQL_SERVERS:    "[127.0.0.1/32]"
  port-groups:
    DNS_PORTS:       "53,853"
    HTTP_PORTS:      "80,443"
    SMTP_PORTS:      "25,465,587"
    IMAP_PORTS:      "143,993"
    SHELLCODE_PORTS: "!$HTTP_PORTS"
rule-files:
  - /var/lib/suricata/rules/suricata.rules
  - /etc/suricata/rules/local.rules
classification-file: /var/lib/suricata/rules/classification.config
threshold-file: /etc/suricata/threshold.config
logging:
  default-log-level: info
outputs:
  - fast:
      enabled: yes
      filename: /var/log/suricata/fast.log
      append: yes
      filetype: regular
  - eve-log:
      enabled: yes
      filetype: regular
      filename: /var/log/suricata/eve.json
      pcap-file: false
      community-id: true
      community-id-seed: 0
      types:
        - alert
        - stats
stats:
  enabled: yes
  interval: 60
unix-command:
  enabled: yes
  filename: /var/run/suricata-command.socket
nfqueue:
  - id: 0-3
    threads: 4
    fail-open: yes
    bypass: yes
    max-pending-packets: 32768
    batchcount: 64
    recv-err-queue: yes
    checksum-checks: auto
host-mode: auto
stream:
  memcap: 512mb
  checksum-validation: yes
  midstream: false
flow:
  memcap: 512mb
  hash-mode: 1
reassembly:
  memcap: 512mb
  depth: 2mb
detect:
  profile: medium
  sgh-mpm-context: auto
  prefilter: yes
app-layer:
  protocols:
    dns:    { enabled: yes }
    http:   { enabled: yes }
    smtp:   { enabled: yes }
    imap:   { enabled: yes }
    tls:
      enabled: yes
      ja3-fingerprints: yes
      ja4-fingerprints: auto
    http2:  { enabled: yes }
    dhcp:   { enabled: yes }
    # Disabled protocols (keine Relevanz + weniger Ressourcen)
    ssh:      { enabled: no }
    ftp:      { enabled: no }
    ftp-data: { enabled: no }
    rfb:      { enabled: no }
    mqtt:     { enabled: no }
    rdp:      { enabled: no }
    ntp:      { enabled: no }
    tftp:     { enabled: no }
    ikev2:    { enabled: no }
    krb5:     { enabled: no }
    snmp:     { enabled: no }
    sip:      { enabled: no }
    smb:      { enabled: no }
    dcerpc:   { enabled: no }
    modbus:   { enabled: no }
    enip:     { enabled: no }
    dnp3:     { enabled: no }
    nfs:      { enabled: no }
defrag:
  memcap: 64mb
  hash-size: 65536
threading:
  set-cpu-affinity: yes
  cpu-affinity:
    - management-cpu-set:
        cpu: [0]
        mode: balanced
    - receive-cpu-set:
        cpu: [1,2,3]
        mode: balanced
        prio: high


-- no debconf information

Reply via email to