-
Updated
Oct 15, 2020 - Python
cybersecurity
Here are 1,239 public repositories matching this topic...
-
Updated
Oct 15, 2020 - Go
-
Updated
Jan 22, 2020
-
Updated
Oct 8, 2020
-
Updated
Oct 15, 2020 - PHP
-
Updated
Jul 19, 2020 - Shell
-
Updated
Oct 13, 2020 - Python
-
Updated
Oct 13, 2020 - JavaScript
-
Updated
Mar 18, 2019 - Go
-
Updated
Oct 13, 2020
-
Updated
Oct 14, 2020 - JavaScript
-
Updated
Oct 14, 2020
-
Updated
Oct 15, 2020 - Python
The project works with 8 modules < reference source/Module >
- Creating issue to accelerate/track test frame building of each module
- The test folder has a very basic example to start with.
- Feel free to make a pull request for the test cases
-
Updated
Oct 11, 2020
-
Updated
Dec 23, 2018 - Python
Hi,
For safety use, it's better to have null check for all variables which are used in this function.
if (!_sessionPriv.$clientAlarmList) {
return;
}
↓
if (!_sessionPriv.$clientAlarmList
|| !_sessionPriv.$monitoredItemForAlarmList
|| !_sessionPriv.$subscriptionforAlarmList ) {
return;
}
-
Updated
Jun 13, 2020 - Python
-
Updated
Oct 15, 2020 - Jupyter Notebook
-
Updated
Oct 12, 2020 - JavaScript
-
Updated
Sep 22, 2020 - Python
-
Updated
Oct 15, 2020 - TypeScript
-
Updated
Oct 15, 2020 - Jupyter Notebook
-
Updated
Jun 7, 2020 - Python
-
Updated
Jul 15, 2019 - Ruby
-
Updated
Oct 15, 2020 - Jupyter Notebook
Most .py files use #!/usr/bin/python3 as shebang, but few others use #!/usr/bin/env python3.
Files which use #!/usr/bin/env python3:
./contrib/eventdb/common.py
./intelmq/bin/intelmq_generate_misp_objects_templates.py
./intelmq/tests/bots/parsers/github_feed/test_parser.py
These files should use #!/usr/bin/python3 for the sake of consistency.
-
Updated
Sep 24, 2020 - Shell
-
Updated
Aug 28, 2020 - HCL
Improve this page
Add a description, image, and links to the cybersecurity topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cybersecurity topic, visit your repo's landing page and select "manage topics."
unicode_literalswas necessary pre-Python 2.6;absolute_importpre-2.5.It's especially not necessary on Py3.
Hence in the sence of cleaning up the source tree, deletion of all
from __future__ import somethingfrom the python files is desirable. This should ideally not happen manually, but with a script, or command line: we need to do that onmaster, but it might also be desirable to