Skip to content

Issues: MISP/misp-rfc

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

9 Open 6 Closed
9 Open 6 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Add a description in the core format about hashes.csv for the manifest part enhancement
#38 opened Nov 17, 2020 by adulau
update misp-core-format info and raw.md.txt to available draft 08
#33 opened Dec 19, 2019 by bernhardreiter
Add a section about current implementation (following BP from RFC 7942) enhancement
#26 opened Jun 23, 2019 by adulau
type codes appear to be duplicated for Attribute and ShadowAttribute; should probably refer to a single appendix table enhancement
#25 opened May 16, 2019 by acruise
1
Several of the attribute attributes refer to their context as "event", maybe C&P error?
#24 opened May 16, 2019 by acruise
3
warning-list format Internet-Draft
#7 opened Dec 7, 2017 by adulau
Sample UUID and example orgs should be added
#5 opened Apr 7, 2017 by adulau
1
Timestamps should all be in the same format valid
#4 opened Feb 13, 2017 by rhaist
2
Fields containing only numbers should be JSON integers
#3 opened Feb 13, 2017 by rhaist
2
ProTip! Add no:assignee to see everything that’s not assigned.