Skip to content
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

Weird new File("blah") in nextByte #86

Open
Kretikus opened this issue Jan 21, 2022 · 3 comments · May be fixed by #77
Open

Weird new File("blah") in nextByte #86

Kretikus opened this issue Jan 21, 2022 · 3 comments · May be fixed by #77

Comments

@Kretikus
Copy link

After 1 Minute of Code Review, I found this weird line.

Does nobody look at the code, before using it (with admin privilidges)?

@rgmz
Copy link

rgmz commented Jan 21, 2022

After 1 Minute of Code Review, I found this weird line.

Does nobody look at the code, before using it (with admin privilidges)?

I noticed that as well. It appears to be a harmless remnant of testing/debugging code that wasn't cleaned up.

private static int nextByte(int[] four, InputStream in) throws IOException {
four[0] = four[1];
four[1] = four[2];
four[2] = four[3];
four[3] = in.read();
File f = new File("blah");
return four[3];
}

There are other examples of code — for example, Strings.java — which seem 'strange', but make sense when you consider that this project was developed in a hurry and doesn't have any third-party dependencies.

@Kretikus
Copy link
Author

There are several companies which use this tool to scan all computers of all employees.
So my comment was not a critisism of the original authors, but more a call out to all the users of this software to make an own code review before using it!
better would be a code contribution... , but I am not in charge of using this software on a corporate level.

@tweimer
Copy link

tweimer commented Feb 5, 2022

Actually, I made a pull request for that in #77 already.

@tweimer tweimer linked a pull request Feb 5, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants