ARTEMIS: Real-Time Detection and Automatic Mitigation for BGP Prefix Hijacking. This is the main ARTEMIS repository that composes artemis-frontend, artemis-backend, artemis-monitor and other needed containers.
License: BSD 3-Clause "New" or "Revised" License
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
Describe the bug
Something causes a query to fail when updating a hijack. Exception suggests that the values are empty but I think this should never happen.
Affected Component(s)
To Reproduce
Unknown behavior. Observed when monitorint /0 prefix.
Expected behavior
No exception and normal handling of the update/hijack.
Screenshots
System (please complete the following information):
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Right now hijacks are sorted based on their detection timestamp (time_detected).
Describe the solution you'd like
Hijacks should be sorted based on their time_last field. The time selection (24h, etc.) should also be based on this field from now on. The appropriate index should also be added to the db (migration required).
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
In Hijack view, the lists of the peers seen hijack updates and withdrawals are not beautified, and the tooltip is missing.
Describe the solution you'd like
When someone presses on the button(s) to show the list(s), show the list as follows:
Follow the same principle for distinct value lists in BGP updates and hijacks.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
We need a function that translates a hijack event (accompanied by its relevant update entries) into an ARTEMIS rule (plus prefixes and ASNs), assuming that the event is marked as ignored, and should thus be learned in the configuration. Note that to have the info on (origin, neighbors) for this event, the event needs to be ongoing.
Describe the solution you'd like
The function should receive a hijack event information (together with its BGP updates) as an input (in the configuration module, consuming from rabbitmq) and generate a dict as follows (the dict will be translated to yaml primitives in issue #23):
[E|S]|0|*|* hijack
-->
{
prefix: <hijacked_prefix>,
origin_asns: [
<hijacker_asn>
]
neighbors: [
<neighbor_seen_in_update_1>,
...,
<neighbor_seen_in_update_N>
]
}
[E|S]|1|*|* hijack
-->
{
prefix: <hijacked_prefix>,
origin_asns: [
<origin_seen_in_update_1>,
...,
<origin_seen_in_update_N>
],
neighbors: [
<hijacker_asn>
]
}
[E|S]|-|*|* hijack
-->
{
prefix: <hijacked_prefix>,
origin_asns: [
<origin_seen_in_update_1>,
...,
<origin_seen_in_update_N>
],
neighbors: [
<neighbor_seen_in_update_1>,
...,
<neighbor_seen_in_update_N>
]
}
Q|0|*|* hijack
-->
{
prefix: <hijacked_prefix>,
origin_asns: [
<origin_seen_in_update_1>,
...,
<origin_seen_in_update_N>
],
neighbors: [
<neighbor_seen_in_update_1>,
...,
<neighbor_seen_in_update_N>
]
}
Describe alternatives you've considered
N/A
Additional context
N/A
Describe the bug
Documentation - https://github.com/FORTH-ICS-INSPIRE/artemis/wiki#starting-artemis - mentions:
...
or if you want additional services:
docker-compose -f docker.compose.yaml -f docker_compose.<extra_service>.yaml up -d
...
It should be:
or if you want additional services:
docker-compose -f docker-compose.yaml -f docker-compose.<extra_service>.yaml up -d
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
docker-compose -f docker.compose.yaml -f docker_compose.grafana.yaml up -dERROR: .FileNotFoundError: [Errno 2] No such file or directory: './docker.compose.yaml'docker-compose -f docker-compose.yaml -f docker_compose.grafana.yaml up -dERROR: .FileNotFoundError: [Errno 2] No such file or directory: './docker_compose.grafana.yaml'docker-compose -f docker-compose.yaml -f docker-compose.grafana.yaml up -dExpected behavior
No error when running command for additional services
Screenshots
N/A
System (please complete the following information):
Additional context
N/A
Is your feature request related to a problem? Please describe.
When we run many instances of the same module the status overview gets really difficult to read.
Describe the solution you'd like
We need to group the same instances and expand/collapse them when we want to check their status.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Workflow to access and use ARTEMIS APIs is not documented.
Describe the solution you'd like
Document use of workflow to access and use ARTEMIS APIs in the wiki (dedicated page)
You can use: https://github.com/FORTH-ICS-INSPIRE/artemis/wiki/Graphql-API
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Currently we conflate hijacks in different dimensions with one single character
Describe the solution you'd like
Use three dimensions: 1) Exact (E) or Sub (S) prefix, 2) Path manipulation (Q|0|1|-),
3) Data plane (-). So the format will consist of 3 characters: ||
So, current types: 0 --> E|0|-, 1 --> E|1|-, S --> S|-|-, Q - -> E|Q|-
Also update detection code to correctly mark these hijacks (especially sub-prefix ones).
And make sure that the frontend deals with the new types (and explain properly in tooltip)
Describe alternatives you've considered
N/A
Additional context
https://arxiv.org/pdf/1801.01085.pdf
Section 2, Table 1
Describe the bug
Tooltip for ASes does not work in BGP updates and hijacks
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Showing tooltip information.
Screenshots
N/A
System (please complete the following information):
Additional context
N/A
Describe the bug
If you update the rabbitmq default username/password in the .env file with a custom username/password the backend process will be unable to connect to rabbitmq.
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Change username or password in the .env file and try to docker-compose -up. You will end up with a 502 if you try to load the site as it cannot properly connect to rabbitmq.
Expected behavior
Updating the default password in the .env file should pass the credentials to the docker containers so we can use custom passwords.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
Additional context
@slowr : yes we need to change the URLs in the modules because they don't use these credentials
Is your feature request related to a problem? Please describe.
Currently we do not have a formal workflow to test ARTEMIS functionality in the frontend
Describe the solution you'd like
Use automated browser tools (such as Selenium https://www.seleniumhq.org/ ) to test the interaction between a -simulated- user and the frontend. Check how this can be combined with backend testing (#36)
Describe alternatives you've considered
N/A
Additional context
https://www.pluralsight.com/guides/testing-user-interfaces-with-browser-automation
Is your feature request related to a problem? Please describe.
We can use pre-commit hooks to avoid having style or other similar related issues when pushing new code.
Describe the solution you'd like
We can follow the guides in: https://pre-commit.com/
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
When we (developers) change sth in default ARTEMIS config.yaml (backend), this change
should not cause any hurdle when deployers download the latest master and have their system versions updated
Describe the solution you'd like
No hurdles, or at least a documented workflow when upgrading and downloading the latest master branch (emphasis in config.yaml and compose.yaml)
Describe alternatives you've considered
N/A
Additional context
N/A
Describe the bug
I get the following error when running docker-compose up.
Pulling backend (inspiregroup/artemis-backend:release-1.0.0)...
release-1.0.0: Pulling from inspiregroup/artemis-backend
54f7e8ac135a: Pull complete
d6341e30912f: Pull complete
087a57faf949: Pull complete
5d71636fb824: Pull complete
0c1db9598990: Pull complete
2eeb5ce9b924: Pull complete
a8c530378055: Pull complete
687ed2fb2a0d: Pull complete
620aea26e853: Pull complete
d1f69edf51b4: Pull complete
d521975a68ff: Pull complete
d6bfccd2c905: Pull complete
4ae245b6935d: Pull complete
58a72a140d62: Pull complete
7490874e1599: Pull complete
60c0048962c3: Extracting [==================================================>] 767.5kB/767.5kB
64bea18216f5: Download complete
2c8b54a5a101: Download complete
de349e122938: Download complete
04968a44e8f8: Download complete
c7f9972b77fa: Download complete
78c5c5662f4a: Download complete
c62301620d19: Download complete
b57b1a7f21cd: Download complete
9ea41fa60b16: Download complete
5ab8a96196e4: Download complete
960687b25614: Download complete
edf4a9369020: Download complete
ERROR: failed to register layer: ApplyLayer exit status 1 stdout: stderr: lchown /root/src/wandio-1.0.4: invalid argument
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect the images to build.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
docker-compose version 1.20.0, build ca8d3c6
Docker version 18.09.0, build 4d60db4
Additional context
Add any other context about the problem here.
Is your feature request related to a problem? Please describe.
We need to be able to translate the dictionary generated by #22 into proper YAML.
Describe the solution you'd like
The function should receive the translated dictionary from #22 as a input, and an existing YAML ARTEMIS config file, and add the following to the file:
The following are just examples. Think about the translation!
E|0|-|- hijack
-->
prefixes:
...: &...
...
ignored_<dict['prefix']>: &ignored_<dict['prefix']>
<dict['prefix']>
...
asns:
...: &...
...
ignored_<dict['origin_asns'][0]>: &ignored_<dict['origin_asns'][0]>
<dict['origin_asns'][0]>
ignored_<dict['neighbors'][0]>: &ignored_<dict['neighbors'][0]>
<dict['neighbors'][0]>
...
...
rules:
...
- prefixes:
- * ignored_<dict['prefix']>
origin_asns:
- *ignored_<dict['origin_asns'][0]>
neighbors:
- *ignored_<dict['neighbors'][0]>
- ...
E|1|-|- hijack
-->
prefixes:
...: &...
...
ignored_<dict['prefix']>: &ignored_<dict['prefix']>
<dict['prefix']>
...
asns:
...: &...
...
ignored_<dict['origin_asns'][0]>: &ignored_<dict['origin_asns'][0]>
<dict['origin_asns'][0]>
...
ignored_<dict['neighbors'][0]>: &ignored_<dict['neighbors'][0]>
<dict['neighbors'][0]>
...
rules:
...
- prefixes:
- * ignored_<dict['prefix']>
origin_asns:
- *ignored_<dict['origin_asns'][0]>
- ...
neighbors:
- *ignored_<dict['neighbors'][0]>
S|*|-|- hijack
-->
prefixes:
...: &...
...
ignored_<dict['prefix']>: &ignored_<dict['prefix']>
<dict['prefix']>
...
asns:
...: &...
...
ignored_<dict['origin_asns'][0]>: &ignored_<dict['origin_asns'][0]>
<dict['origin_asns'][0]>
...
ignored_<dict['neighbors'][0]>: &ignored_<dict['neighbors'][0]>
<dict['neighbors'][0]>
...
...
rules:
...
- prefixes:
- * ignored_<dict['prefix']>
origin_asns:
- *ignored_<dict['origin_asns'][0]>
- ...
neighbors:
- *ignored_<dict['neighbors'][0]>
- ...
Q|0|-|- hijack
-->
prefixes:
...: &...
...
ignored_<dict['prefix']>: &ignored_<dict['prefix']>
<dict['prefix']>
...
asns:
...: &...
...
ignored_<dict['origin_asns'][0]>: &ignored_<dict['origin_asns'][0]>
<dict['origin_asns'][0]>
...
ignored_<dict['neighbors'][0]>: &ignored_<dict['neighbors'][0]>
<dict['neighbors'][0]>
...
...
rules:
...
- prefixes:
- * ignored_<dict['prefix']>
origin_asns:
- *ignored_<dict['origin_asns'][0]>
- ...
neighbors:
- *ignored_<dict['neighbors'][0]>
- ...
||-|L hijack:
same as previous, remove the no-export policy (talk with @vkotronis if you reach this stage).
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Currently .env is version-controlled, but it contains secrets; accidentally overwriting it by a fresh install vs. accidently pushing to git are risks. Therefore, we need to check how to handle this properly, e.g., pushing this too in local_configs.
Describe the solution you'd like
Check a possible solution to the location problem and the writing of secrets on disk.
Describe alternatives you've considered
N/A
Additional context
docker/compose#6170
Is your feature request related to a problem? Please describe.
We have a lot of very large subnets, /10s and such, so having to list them as /24s is rough and makes for a huge config file.
Describe the solution you'd like
It would be nice to allow the config format to use some operators like what we use with our IRRs (RADB) route-sets. They follow rfc2622 which has a few operators, although I'm personally only interested in ^n.
^n where n is an integer, stands for all the length n specifics of
the address prefix. For example, 30.0.0.0/8^16 contains all the
more specifics of 30.0.0.0/8 which are of length 16 such as
30.9.0.0/16.
Describe alternatives you've considered
none, except leaving as is.
Additional context
Example:
10.0.0.0/8^24 would match all the /24s in the /8, but only require a tiny config, instead of hundreds of /24s.
Is your feature request related to a problem? Please describe.
Currently, if a configured prefix (or group of prefixes) is associated with no origins/neighbors in a rule,
any announcement is considered as a squatting attack. We need to enable the user to "wildcard" origins.
Describe the solution you'd like
origin_asns: '*' (star as a wildcard --> needs to be translated to an integer if we have a conf check probably).
Neighbors can be omitted (this works already now, with valid origins --> no alert).
Please also check if automated tests could be added for this case.
Describe alternatives you've considered
NA
Additional context
NA
Is your feature request related to a problem? Please describe.
The user currently cannot delete hijacks using the UI
Describe the solution you'd like
This should be done after #34 is solved (will require hasura for "IN"-like searching in key lists).
UI button and backend db functionality to delete multiple hijacks and their related BGP updates.
Make sure that there is an "Are you sure?" banner before confirming final deletion.
This issue needs frontend support (UI) via graphql (delete hijacks and updates from db).
Delete only updates that belong to a single hijack, remove the key from the ones that belong to multiple (like withdrawals). Make sure that the UI is usable during the transition (e.g., you can delete first the hijack events and then the updates for safety).
We need a "delete" button within a hijack, and "delete" in the hijack table for multiple hijacks.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Benign BGP updates that are older than a certain age are not currently deleted.
Describe the solution you'd like
ENV variable (e.g., DEL_NON_HIJ_UPDATES_AFTER) to specify maximum age for benign BGP updates, and functionality (backend) that deletes
the old BGP updates (only those not related to a hijack). Default value = None, which means no deletion.
Updates can be cleared periodically from the db using a clock signal (e.g., every hour)
Describe alternatives you've considered
N/A
Additional context
N/A
Describe the bug
Trying to follow the wiki for restoring the database but its failing on import as it thinks all of the tables already exist
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should just fill all of the data from the old db into the new one.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
Additional context
postgres_errors.txt
Is your feature request related to a problem? Please describe.
The taps on the backend compete for resources with the detection and database. We need to check if we can separate them in a different container for scalability reasons.
Describe the solution you'd like
Without changing anything in the configuration logic and control mechanisms (e.g., UI monitor on/off), need to check if we can detach and monitor.py taps from backend
and clone listener.py and supervisor in a new "taps" container
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Describe the bug
Old Firefox versions returns different Content-Type that throws a Syntax Error and disables all the communication with GraphQL.
https://stackoverflow.com/questions/34624099/json-syntax-error-in-firefox-only
Affected Component(s)
To Reproduce
Open tool with Firefox and JWT tokens will not be retrievable.
Expected behavior
parseJSON should work on all browsers.
Screenshots
System (please complete the following information):
Additional context
N/A
Is your feature request related to a problem? Please describe.
On hijack view, the tooltip for the hijacker AS on the hijack table and for the route collectors on the bgp update table are not activated.
Describe the solution you'd like
Add/activate the tooltips, as done in other tables (e.g., BGP update).
Also check that the route collector tooltip works in "More" view within a BGP update entry of the hijack view.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
When no export is supported, the user needs to specify no-export exceptions, so that we also catch violations with path lengths = 2 (currently we assume that the last hops are monitors, and all of them have export rights).
Describe the solution you'd like
User-supplied list of no-export exceptions (ASNs)
Describe alternatives you've considered
N/A
Additional context
#101
Is your feature request related to a problem? Please describe.
Currently, besides this wiki page, we do not have a gif for a full ARTEMIS workflow on README.
Describe the solution you'd like
Gif showing a lifecycle of ARTEMIS use:
Describe alternatives you've considered
Think of other things that could go in the gif.
Additional context
Need low-size gif that can be rendered in a .md file.
Is your feature request related to a problem? Please describe.
Support no-export prefixes
Describe the solution you'd like
Add an additional field on the configuration rules to enable no-export functionality
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Nope. Its only improvements.
Describe the solution you'd like
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Currently we do not have a formal workflow to test ARTEMIS functionality in the backend
Describe the solution you'd like
Generate test BGP updates
Feed them into the monitor module
Make sure that rabbitmq handles updates correctly
Make sure the updates make it to the db properly
If related to hijacks, make sure the correct hijacks are created (detection module) and handled by watching rabbitmq
Make sure that the hijacks make it to the db properly
Make sure that consequent updates for the same hijack, update the hijack
Other possible steps
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
circleci is not configured
Describe the solution you'd like
write configuration scripts and test circlci
Describe alternatives you've considered
N/A
Additional context
https://circleci.com/gh/FORTH-ICS-INSPIRE/artemis
Example: https://github.com/hasura/graphql-engine/tree/master/.circleci
Is your feature request related to a problem? Please describe.
Nope
Describe the solution you'd like
Create migration for the container and the previous db.
Describe alternatives you've considered
NA
Additional context
Check this:
https://docs.timescale.com/v1.1/using-timescaledb/update-db
Describe the bug
The current formation is not optimal.
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
N/A
Screenshots
N/A
System (please complete the following information):
N/A
Additional context
N/A
Describe the bug
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
Additional context
Add any other context about the problem here.
Is your feature request related to a problem? Please describe.
Trigger workflow of ignored hijack learning upon user request.
Describe the solution you'd like
When a user presses "hijack ignore", a UI prompt should ask: "Add this event to ARTEMIS configuration?". If yes, then the workflow of issue #25 should be followed. If no, nothing should happen (like in the current implementation). A positive answer should result to a message with the hijack information (including the related BGP updates, queried via graqhql) being sent to the configuration module.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Currently, backend testing is not automated
Describe the solution you'd like
Check and integrate framework to automate the testing of micro-services
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
When a hijack alert has not seen any updates for a user-defined time window (e.g., 24 hours), it should
be considered still active (ongoing), but also have an extra tag called "dormant". There is no need to change existing DB constraints for this, except add a constraint that active and dormant flags cannot be set as (false, true), but need to be within [(true, true), (true, false), (false, false)].
Describe the solution you'd like
An extra "dormant" field in the db (defaulting to false), that is automatically set if the alert has not seen sth for at least X hours (defined by the user in .env). This can be dealt with with a cron job in postgres, that does sth like this in pseudocode:
SELECT all hijack alerts with time_last < NOW - interval, which have the active flag set to True and the dormant flag to False, and set the dormant flag to True.
This will also require support from the frontend, since a new tag is added. Note that whenever the active flag is set to false, the dormant flag should also change too (see proposed constraints).
Whenever the time_last is updated (see database.py actions), the dormant flag should be directly set to False again!
DB migration will also be required to add the new field in the hijacks table.
This change will require changes in the wiki too.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Plotting BGP updates per second.
Describe the solution you'd like
A plot in grafana.
Describe alternatives you've considered
Grafana applies DB polling (we can set it every 10 seconds or so, depending on an .env variable). The user selects if he/she will start grafana or not in the compose file. Connection to the db cna be implemented by accessing the .env variables.
Additional context
http://docs.grafana.org/reference/sharing/#embed-panel
Describe the solution you'd like
Bgpmon.io is online again (https://www.bgpmon.io/join-the-peering.html)
Check this: https://github.com/CSUNetSec/bgpmon
Is your feature request related to a problem? Please describe.
Need to adjust to the RIPE RIS prod service for live BGP feeds.
Describe the solution you'd like
Example:
"""
Subscribe to a RIS Live stream and output every message to stdout.
IMPORTANT: this example requires 'websocket-client' for Python 2 or 3.
If you use the 'websockets' package instead (Python 3 only) you will need to change the code because it has a somewhat different API.
"""
import json
import websocket
ws = websocket.WebSocket()
ws.connect("wss://ris-live.ripe.net/v1/ws/?client=py-example-1")
params = {
"moreSpecific": True,
"host": "rrc21",
"socketOptions": {
"includeRaw": True
}
}
ws.send(json.dumps({
"type": "ris_subscribe",
"data": params
}))
for data in ws:
parsed = json.loads(data)
print(parsed["type"], parsed["data"])
For iding the message, please add support for an ENV signaling e.g., the AS that requests this information, prefixed by "artemis", e.g.,
ws.connect("wss://ris-live.ripe.net/v1/ws/?client=artemis-AS<ASN>")
Describe alternatives you've considered
Javascript implementation
Additional context
https://ris-live.ripe.net/
Is your feature request related to a problem? Please describe.
Need to implement an alert that will inform users when to run the database migration process.
Describe the solution you'd like
On container's entrypoint there will be a compare of database's DB_VERSION and current's source code DB_VERSION.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Right now we treat ignore as an implicit FP and resolve as an implicit TP.
Describe the solution you'd like
Use the already available field (orthogonal to the tagging mechanism), to help the user signal this explicitly. Ignore would still trigger a non-ack, while resolved and mitigate an ack.
Describe alternatives you've considered
New field, but since we already have an internal one (and we can do without migrating the DB again), this is quite cost-effective.
Additional context
N/A
Is your feature request related to a problem? Please describe.
Currently we mark a hijack as withdrawn only upon receiving explicit withdrawals. However,
hijacked paths can be implicitly withdrawn (e.g., by being changed to a legal path).
Describe the solution you'd like
Investigate how we can treat path changes as implicit withdrawals (we can use the currently available fields, no need for db changes). For example, if a new benign BGP update comes, and it includes a path to a prefix P and is learned from monitor X, and P and X are the prefix and one of the monitors of an ongoing hijack, then we can mark X as having seen a withdrawal.
Optional, to discuss: Note that if the benign update is for a sub-prefix of a currently hijacked prefix, then we need to see all sub-prefixes that build the hijacked super-prefix being corrected. to consider a monitor withdrawal.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Currently we do not have visual examples of ARTEMIS UI in the wiki and README
Describe the solution you'd like
Create gifs/pictures for the different functionalities of the tool. Examples:
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
Nope
Describe the solution you'd like
Expose the graphql API to the outside world using custom authentication
Describe alternatives you've considered
Additional context
Is your feature request related to a problem? Please describe.
We should add a test that validates the redis entries to avoid future system failures.
Describe the solution you'd like
We could try using the SUBSCRIBE method of redis to receive all new incoming messages.
Describe alternatives you've considered
N/A
Additional context
N/A
Describe the bug
The BGP updates in 1.1.0 seem to be handled much slower than in the past.
It is either a bottleneck in the db or the detection microservice. I could manage
to replicate it only on an installation with a large DB (>1M BGP updates), and detection
seems to operate as expected (expected speeds). So maybe a bottleneck query that takes
into account the size of the DB is taking place. Or maybe it is only a visual delay.
Affected Component(s)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The speed should be back up at normal levels.
Screenshots
N/A
System (please complete the following information):
N/A
Additional context
ARTEMIS release-1.1.0
Describe the bug
When a new user registers on the system the primary user role is 'pending'. However, it also has a secondary role the default 'user' role.
Affected Component(s)
Expected behavior
User should only have the 'pending' user role.
Is your feature request related to a problem? Please describe.
The hijack view and AS-PATH search are REST-based instead of graphql (hasura-) based.
This is because currently the "IN" query for lists is not implemented in hasura (under development).
Describe the solution you'd like
Migrate REST to hasura functions by creating custom "IN" membership function
Describe alternatives you've considered
N/A
Additional context
hasura/graphql-engine#1073
Is your feature request related to a problem? Please describe.
End-to-end workflow for adding an ignored hijack event in ARTEMIS config.
Describe the solution you'd like
Describe alternatives you've considered
N/A
Additional context
N/A
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.