michael2to3 / c2-search-netlas Goto Github PK

Describe the bug
Cyrillic characters in the path to the config file and build.gradle are not supported on Windows, causing issues when trying to build the project or load configuration settings.

To Reproduce
Steps to reproduce the behavior:

1. Create a directory with Cyrillic characters in its name.
2. Place the config file and/or build.gradle in the directory created in step 1.
3. Attempt to build the project or load configuration settings on a Windows machine.
4. Observe that the build fails or the configuration settings are not loaded correctly.

Expected behavior
The project should be able to build and load configuration settings correctly on Windows, regardless of the presence of Cyrillic characters in the path to the config file or build.gradle.

Desktop (please complete the following information):

• OS: Windows
• Java Version: 16+

Description

When using a direct detect on connect TCP socket, similar to the netcat program, the Search for C2 Search Netlas utility can take a very long time to receive a response from the C2 server. This can cause delays and slow down the overall performance of the program, even when not using the Netlas API.
Steps to Reproduce

• Run the Search for C2 Search Netlas utility.
• Perform a search for C2 servers using the direct detect on connect TCP socket method without using the Netlas API.
• Wait for the program to receive a response from the C2 server.

Expected Behavior
The Search for C2 Search Netlas utility should receive a response from the C2 server in a reasonable amount of time when using the direct detect on connect TCP socket method without using the Netlas API.

Additional Context
This issue may be related to network latency, server load, or issues with the direct detect on connect TCP socket method. Further investigation is needed to identify and address the underlying cause of the issue.
Possible solutions may include optimizing the program, implementing a more efficient data processing algorithm, or using multi-threading or multiprocessing to improve performance.

Describe the bug
The ClassScanner is broken when attempting to create a build using shadow. It fails to load classes and throws a ClassNotFoundException.

To Reproduce
Steps to reproduce the behavior:

1. Build the project using shadow.
2. Use the ClassScanner to load classes from a package.
3. See the ClassNotFoundException.

Expected behavior
The ClassScanner should be able to load classes from a package when building the project using shadow.

Screenshots
N/A

Additional context
The issue is caused by the ClassLoader not being able to find the resource file when using shadow. The current implementation assumes that the resource file is a directory, which is not always the case when using shadow. A fix for this issue would be to use the getResourceAsStream() method instead of getResource() to load the resource file.