public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api/pmg-gui v5] add additional attributes to ContentTypeFilter and MatchField
Date: Fri, 21 Feb 2025 17:48:14 +0100	[thread overview]
Message-ID: <20250221164821.207845-1-s.ivanov@proxmox.com> (raw)

v4->v5:
* squashed pmg-api patches 2/5 and 3/5 together
* re-added the $magic to the if
both based on Dominik's feedback on- and off-list - thanks!

tested with Friedrichs swaks sample again.

I added the Tested-by/Reviewed-by trailers for those patches I did not
touch in the v5.


cover-letter for v4:
v3->v4:
* rework patch 3/5 for pmg-api according to feedback from Dominik and Friedrich
  after understanding that file-paths (and in result content-types are not
  set for mail-parts that are multipart (mime-entities either have parts
  or a body in general)

cover-letter for v3:

This series replaces two previous patch-series.

v2->v3:
for the content-type matching based on magic infromation only two patches
were added that remove the fallback on the content-type header in case no
filetype could be found through magic.
The one place were I decided to fall back on header information was when
determining if a mime-part is an archive.

places where the content-type information was used are based on grepping
for PMX_ in the pmg-api sources.

Tested with Friedrich's swaks reproducer - the random blob was not
detected as pdf anymore.

no changes to the series for matching headers only on the top-part
(resending so that the comment that it's based on v2 of the content-type
series does not cause confusion)

original cover-letters:

for https://lore.proxmox.com/pmg-devel/20250218135416.54504-1-s.ivanov@proxmox.com/T/#t

v1->v2:
Based on Domink's feedback reworked the series - it now offers only one
optional new attribute for the content-type filter ('only-content') to
indicate that it should only compare the content-type obtained via
magic/file-conents. The other 2 match options can already be expressed
with the Filenamefilter ('application/pdf' -> '.*\.pdf') and the Match
Field filter (to match the 'Content-type' header)

original cover-letter for v1[0]:
The following patch series was started shortly after the release of PMG 8.1,
but I did not find the time to get it in shape for sending.
They follow the patches for adding 'top' and 'add_separator' to the
Disclaimer action.

The current content-type filter can sometimes surprise users (e.g.
https://bugzilla.proxmox.com/show_bug.cgi?id=5618#c2 and
https://bugzilla.proxmox.com/show_bug.cgi?id=2691#c0 ,but also a few
cases in our technical support-channels come up here and there):

It matches if any of:
* content-type header
* file-magic
* filename (extension)
match the content type, the what-object matches.
by adding an attribute for each of the sources users can restrict which
of the sources should be taken into consideration

the first patches for both repositories are independent (I just ran into
them while looking into this).

minimally tested locally, by sending a plain-text file called
testtext.pdf, and a pdf-file renamed to have a `.docx` suffix.

[0]
https://lore.proxmox.com/pmg-devel/20250212151241.91077-1-s.ivanov@proxmox.com/ 


for https://lore.proxmox.com/pmg-devel/20250218194829.80095-1-s.ivanov@proxmox.com/T/#t
based on top of:
https://lore.proxmox.com/pmg-devel/20250218135416.54504-1-s.ivanov@proxmox.com/T/#t

as I think testing both should go well together, and to avoid a trivial
merge-conflict (can of course resend on top of current master) in the
pmg-api patch

Tested minimally in my setup - more testing  would be appreciated
pmg-api:
Stoiko Ivanov (4):
  ruledb: disclaimer: simplify update-case
  utils: content-type: don't fallback to header information for magic
  ruledb: content-type: add flag for matching only based on
    magic/content
  fix #2709: ruledb: match-field: optionally restrict to top mime-part

 src/PMG/RuleDB/ArchiveFilter.pm     |  2 +-
 src/PMG/RuleDB/ContentTypeFilter.pm | 79 +++++++++++++++++++++++++----
 src/PMG/RuleDB/Disclaimer.pm        |  8 ++-
 src/PMG/RuleDB/MatchField.pm        | 47 +++++++++++++++--
 src/PMG/Utils.pm                    | 12 ++---
 src/bin/pmg-smtp-filter             |  8 ++-
 6 files changed, 129 insertions(+), 27 deletions(-)

pmg-gui:
Stoiko Ivanov (3):
  rules/object: remove icon from remove button
  rules/content-typefilter: add checkbox for file content only matching
  fix #2709: rules: match-field: add top-level-only checkbox

 js/ObjectGroup.js |  3 +--
 js/Utils.js       | 17 +++++++++++++++++
 2 files changed, 18 insertions(+), 2 deletions(-)

-- 
2.39.5



_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel


             reply	other threads:[~2025-02-21 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 16:48 Stoiko Ivanov [this message]
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-api v5 1/4] ruledb: disclaimer: simplify update-case Stoiko Ivanov
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-api v5 2/4] utils: content-type: don't fallback to header information for magic Stoiko Ivanov
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-api v5 3/4] ruledb: content-type: add flag for matching only based on magic/content Stoiko Ivanov
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-api v5 4/4] fix #2709: ruledb: match-field: optionally restrict to top mime-part Stoiko Ivanov
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-gui v5 1/3] rules/object: remove icon from remove button Stoiko Ivanov
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-gui v5 2/3] rules/content-typefilter: add checkbox for file content only matching Stoiko Ivanov
2025-02-21 16:48 ` [pmg-devel] [PATCH pmg-gui v5 3/3] fix #2709: rules: match-field: add top-level-only checkbox Stoiko Ivanov
2025-02-21 17:26 ` [pmg-devel] applied: [PATCH pmg-api/pmg-gui v5] add additional attributes to ContentTypeFilter and MatchField Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250221164821.207845-1-s.ivanov@proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal