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

ocb-open-source-2013 not recognized #2670

Closed
mmurto opened this issue Aug 26, 2021 · 4 comments
Closed

ocb-open-source-2013 not recognized #2670

mmurto opened this issue Aug 26, 2021 · 4 comments

Comments

@mmurto
Copy link

mmurto commented Aug 26, 2021

Description

ScanCode does not recognize ocb-open-source-2013 in https://github.com/bcgit/bc-java/blob/master/core/src/main/java/org/bouncycastle/crypto/modes/OCBBlockCipher.java.

System configuration

ScanCode commit 5db9d05.

@mmurto mmurto added the bug label Aug 26, 2021
pombredanne added a commit that referenced this issue Aug 27, 2021
This is a basic correction for this license detection issue.

Reported-by: Mikko Murto <mikko.murto@gmail.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Aug 27, 2021
This is an extra set of extended license detection rules from
researching some variant notices for this OCB license which is seen
in the popular libgcrypt (C) and BouncyCatsle (Java) packages.

Reported-by: Mikko Murto <mikko.murto@gmail.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
@pombredanne
Copy link
Member

pombredanne commented Aug 27, 2021

@mmurto Thank you ++ for this report!
In case you could be interested to help fix similar issues in the future I tried to make a didactic PR in #2677

  • The first commit e9286de adds the minimal rule and a test to fix the issue

  • The second commit at 98c4393 adds a bunch of extra rules that have been collected left and right for other mentions of this license

Your review there is much welcomed!

pombredanne added a commit that referenced this issue Aug 27, 2021
This is an extra set of extended license detection rules from
researching some variant notices for this OCB license which is seen
in the popular libgcrypt (C) and BouncyCatsle (Java) packages.

Reported-by: Mikko Murto <mikko.murto@gmail.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Aug 27, 2021
This was missed before

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Aug 28, 2021
This is a basic correction for this license detection issue.

Reported-by: Mikko Murto <mikko.murto@gmail.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Aug 28, 2021
This is an extra set of extended license detection rules from
researching some variant notices for this OCB license which is seen
in the popular libgcrypt (C) and BouncyCatsle (Java) packages.

Reported-by: Mikko Murto <mikko.murto@gmail.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Aug 28, 2021
This was missed before

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Aug 28, 2021
@pombredanne
Copy link
Member

This fixed and merged in develop. Thank you++

@mmurto
Copy link
Author

mmurto commented Aug 30, 2021

@mmurto Thank you ++ for this report!
In case you could be interested to help fix similar issues in the future I tried to make a didactic PR in #2677

  • The first commit e9286de adds the minimal rule and a test to fix the issue
  • The second commit at 98c4393 adds a bunch of extra rules that have been collected left and right for other mentions of this license

Your review there is much welcomed!

Thank you, I'll try a fix next time!

One thing that's not immediately obvious from the rules you added is that why is relevance 100 in all of them? Could it be something else and what would that mean? This generally describes what it's about, but if there's any more information about what relevance should be for different kind of rules, that may come useful 🤓

@pombredanne
Copy link
Member

Actually the relevance is not needed. The only time when a relevance is needed is when you have a small rule *(small as a in made of only a few words) and that is still highly relevant. For instance: license: gpl3+ would be two words, but would be 100% relevant as a license tag for the gpl 3.

pombredanne added a commit that referenced this issue Sep 14, 2021
It is not needed for longer rules above the 18 words threshold. And it
was confusing to always add this as 100 when not needed

Reported-by: Mikko Murto <mikko.murto@gmail.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants