Replies: 1 comment 8 replies
-
Please test latest 3.18.x snapshot: https://github.com/sepinf-inc/IPED/actions/runs/1982951751 and check if it works.
They are not attachments, past behavior was wrong.
Now there are new properties ufed:ForwardedMessageData and ufed:ReplyMessageData you can use to filter by those messages types e.g.: ufed:ForwardedMessageData:* this will list forwarded instant messages in table tab.
We already have an open issue to render them properly in Preview tab: #998. This is not scheduled for a future 3.18.x release. Of course, contributions are always welcome. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone!
I was researching about forwardedMessages and ReplyMessages (whatsapp).
I found bug #997 which more or less describes the issue that we are experiencing.
Version 18.13: Decoding via external parser, ufdr forwardedMessages and ReplyMessages are flagged with an attachment. Decoding via ufdr internal parser, duplicates it and does not flag.
I build a iped version from source today, but only the duplication problem resolved, there is still no indication that it is a forwarded or reply message. And the external parser stopped to flagged it with attachment (wich I dont think is a good way).
Is this the scenario for now?
Would it be worth opening an issue to request that these types of messages, when decoded via external at least, to be flagged in a specific way?
Beta Was this translation helpful? Give feedback.
All reactions