Re:User beware: Modified AGPLv3 removes freedoms, adds legal...
by didibus on Friday April 08, 2022 @01:10AM
(#30953533)
Seems a better solution would be a checksum on the license text no?
[ Parent
| on HN ]
Re:User beware: Modified AGPLv3 removes freedoms, adds legal...
by pabs3 on Friday April 08, 2022 @02:34AM
(#30953959)
The most accurate license detector is ScanCode. I think it uses some sort of rolling checksum thing for detection.
Re:User beware: Modified AGPLv3 removes freedoms, adds legal...
by pombreda on Saturday April 09, 2022 @02:26AM
(#30965677)
Hey, pabs3! Actually this is not using a rolling checksum for detection but rather a combo of language model, checksums, automatons, bitvectors, inverted indexes and multiple sequences alignment (e.g. a specialized diff). I put some docs there to explain the approach at ahttps://github.com/nexB/scancode-toolkit/blob/develop/src/li...
Re:User beware: Modified AGPLv3 removes freedoms, adds legal...
by pombreda on Saturday April 09, 2022 @02:31AM
(#30965700)
You need a bit more than checksums for this. If anything the FSF published many different versions of the "official" GPL2 texts and this would defeat checksums. See https://github.com/pombredanne/gpl-history ... so in the general cases hashing a text does not work consistently and safely.
Eventually you need a diff for a pairwise comparison, and the only difficulty is making diff fast or find ways to approximate it fast enough to avoid doing a full diff.