Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@musharafmaqbool
Copy link

What does it do?

Adds a warning message to the database export functionality to inform users that malware samples are not included in database exports since they are stored on the filesystem rather than in the database.

Changes:

  • Added warning message to inform users about malware sample exclusion
  • Warning appears when users access the export function
  • Helps set proper expectations about export contents

Fixes: #3101

Testing

  • Warning message appears when accessing DB export
  • Message clearly explains malware samples are not included
  • Export functionality still works normally

Questions

  • Does it require a DB change? No
  • Are you using it in production? This is a user-facing warning improvement
  • Does it require a change in the API (PyMISP for example)? No

- Remove duplicate emailDstRule call for generic 'email' case
- Prevents duplicate entries in NIDS export output
- Generic email attributes now default to source rules only
- Users can still use 'email-dst' for destination-specific rules
- Fixes issue MISP#6565
…6565

Fix duplicate email rules in NIDS export
…SP#3101)

Added warning message to inform users that malware samples are not included 
in database exports since they are stored on the filesystem rather than 
in the database. This addresses issue MISP#3101.
This PR adds a warning message to the database export functionality to inform users that malware samples are not included in database exports since they are stored on the filesystem rather than in the database.

The warning message appears when users access the export function and helps set proper expectations about what will be included in the export.

Fixes MISP#3101
Reverted NIDS email duplicate fix changes to keep this branch focused only on the database export malware warning feature. The NIDS fix will be implemented in a separate PR.
@musharafmaqbool
Copy link
Author

musharafmaqbool commented Sep 5, 2025

Hi @adulau,

Thank you for the feedback. You're absolutely right - I understand now that each fix should be in its own separate branch with its own PR.

I've just created separate branches for each fix:

  1. DB Export Malware Warning - This branch only contains the warning message for database exports
  2. NIDS Email Duplicate Fix - I'm creating this as a separate branch that only addresses the duplicate email rules issue

I apologize for initially combining both changes in one PR. I'll make sure to follow the one-fix-per-PR approach going forward. Each branch now focuses on solving one specific issue with its own commit history.

Thank you for your patience and guidance on the proper contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant