Hello and thanks for taking the time to report this bug. In order to
drive this forward we some more things from your side:
0. Can you please double check your yara_2.yar is valid? The error your
report is:
undefined identifier "uint32be"
but the documentation you linked says "The following keywords are
reserved and cannot be used as an identifier:" and follows listing
"uint32be" as one of these keywords. This makes me suspect your yara
file has syntax issues.
1. Is this a regression, or is this the first time you try to setup
ClamAV with yara rules? In other words: did you upgrade an existing,
working Ubuntu system to 20.04 and hit the issue, or did you hit it
while setting up a system up from scratch?
2. Can you share your yara_2.yar file and outline how you setup ClamAV
for using it? Ideally we need the minimal set of steps to setup a system
which will hit the problem you described.
I'm marking this report as Incomplete for the moment. Please change its
status back to New after commenting back and we'll look at it again.
Thanks!
** Changed in: clamav (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883857
Title:
Not supported "uint32be" condition in yara rules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1883857/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
