Re: [Prelude Hybrid IDS] #217: new row for relation "prelude_checksum" violates check constraint "prelude_checksum_algorithm_check"
"Prelude Hybrid IDS" <[email protected]>
| Newsgroups | gmane.comp.security.ids.prelude.devel |
|---|---|
| Message-ID | <[email protected]> |
#217: new row for relation "prelude_checksum" violates check constraint
"prelude_checksum_algorithm_check"
--------------------------+-------------------------------------------------
Reporter: bjou | Owner: yoann
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: libpreludedb | Version: 0.9
Severity: normal | Resolution:
Keywords: |
--------------------------+-------------------------------------------------
Changes (by yoann):
* status: new => assigned
Comment:
Replying to [comment:2 [email protected]]:
> nepenthes writes the checksums name uppercase
>
> add_idmef_object(idmef, "alert.target(0).file(0).checksum(0).algorithm"
,"MD5");
>
> not sure what is correct
Yes, this is correct.
The problem is within the libpreludedb database schema that use lowercase
in place of uppercase. Application can use either since it's normalized to
upper case (as specified by IDMEF) within libprelude.
The upcoming libpreludedb release will fix this issue.
--
Ticket URL: <https://trac.prelude-ids.org/ticket/217#comment:3>
Prelude Hybrid IDS <http://www.prelude-ids.org>
The Prelude Hybrid Intrusion Detection System suite
_______________________________________________
Prelude-devel site list
[email protected]
http://www.prelude-ids.org/mailman/listinfo/prelude-devel