-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
galaxy issues #1731
Labels
T: potential bug
Type: potential bug. This issue may be a bug
Comments
Will have a look at the permissions once i am on solid ground, sounds odd.
Editing galaxies is not supported in the current release.
For the ID, it's kind of intended for now, galaxies are dropped and
reloaded fully until the second iteration.
Will look at the other issues asap.
…On Dec 8, 2016 9:57 AM, "Christophe Vandeplas" ***@***.***> wrote:
MISP version / git hash | 2.4.56
User permissions;
- Permission level Manage and Publish Organisation Events
- Delegate Yes
- Sync No
- Auth Yes
- Audit No
- Admin No
- Site Admin No
- Regexp Access No
- Tagger Yes
- Template No
- Sharing Group No
- Tag Editor Yes
Here are some issues encountered:
-
user permissions:
- /galaxies/index : the list of the 2 galaxies is visible
- galaxies/view/2 : shows the description, but not the content (the
list of entries)
- /galaxy_clusters/view/60: results in permission error
-
update galaxies link: This causes to have the galaxy IDs change. (old
IDs are lost, and replaced by new IDs)
-
pivot from Event to other events in the same galaxy : when you are on
the event page, you cannot pivot to the page with the galaxy details or
other events in the same galaxy.
-
the misp-galaxy taxonomy is still listed in the tags list; but is
empty.
-
(feature request) Ideally adding something to a galaxy should also be
possible with the normal tagging principle. The reason for this is keeping
the same workflow for the analyst.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1731>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADf6wH1s4Azuq156PJkHxNq208XgFGZ8ks5rF8ZlgaJpZM4LHk7->
.
|
iglocska
added a commit
that referenced
this issue
Dec 8, 2016
…selected cluster as a filter, affects #1731
@cvandeplas Related to the taxonomies, do you want me to update the taxonomy tool for generating the tags? The new galaxy system can work with both but we did some minor changes into the format. Cheers. |
The taxonomy is no longer needed
…On Dec 8, 2016 11:39 AM, "Alexandre Dulaunoy" ***@***.***> wrote:
@cvandeplas <https://github.com/cvandeplas> Related to the taxonomies, do
you want me to update the taxonomy tool for generating the tags? The new
galaxy system can work with both but we did some minor changes into the
format. Cheers.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1731 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADf6wF1NWOiyb9GMZLgl31o7DRjMzd5Tks5rF953gaJpZM4LHk7->
.
|
Also permission issues result in an user being able to add a Cluster to an event that's not his. It should behave the same as a tag. |
Hmm interesting. Internally it should, so we may have the same issues with
tags via the API (the same functionality is reused)
…On Dec 8, 2016 2:22 PM, "Christophe Vandeplas" ***@***.***> wrote:
Also permission issues result in an user being able to add a Cluster to an
event that's not his. It should behave the same as a tag.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1731 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADf6wCgal_gHGHljnI2MLAYZ8BW7MgC9ks5rGASRgaJpZM4LHk7->
.
|
@iglocska So we get rid of the galaxy taxonomy as is? @cvandeplas |
Yup
On Dec 8, 2016 4:08 PM, "Alexandre Dulaunoy" <notifications@github.com> wrote:
@iglocska <https://github.com/iglocska> So we get rid of the galaxy
taxonomy as is? @cvandeplas <https://github.com/cvandeplas>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1731 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADf6wD0U3BXipHKgx7k0BExUDrHTHmnBks5rGB18gaJpZM4LHk7->
.
|
adulau
added a commit
to MISP/misp-taxonomies
that referenced
this issue
Dec 8, 2016
Fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MISP version / git hash | 2.4.56
User permissions;
Here are some issues encountered:
user permissions:
update galaxies link: This causes to have the galaxy IDs change. (old IDs are lost, and replaced by new IDs)
pivot from Event to other events in the same galaxy : when you are on the event page, you cannot pivot to the page with the galaxy details or other events in the same galaxy.
the misp-galaxy taxonomy is still listed in the tags list; but is empty.
(feature request) Ideally adding something to a galaxy should also be possible with the normal tagging principle. The reason for this is keeping the same workflow for the analyst.
The text was updated successfully, but these errors were encountered: