Michael

I think if the file upload could check at first hand for the hash of the (entire) upload.  The idea is to have warning if the upload is already...

indeed, OTHO, deleting an upload is a heavy thing (because some analysis work might be lost)

@tma-hmquan did it actually help? there is also: * https://github.com/fossology/fossology/wiki/Improving-IO-performance * https://github.com/fossology/fossology/wiki/Configuration-and-Tuning

Ahh. and I think from what you write also tuning postgresql sounds promising. You could consider pgtune for adjusting settings: https://pgtune.leopard.in.ua/#/

right, is still an issue (with 3.0.0). So there seem to be two solutions, a cheap one to match commonly known characters, such as " ' < > \ etc....

still valid, important for operations that do not use sso. also good to have password reset for operational

@bufferoverflow hm, not quite my idea, I see 4.3.1 as file type in the file system sense and it is not clear if these is distribution relevant (Text, Image, Audio,...

It sounds like that there is still a large document with all files and their license assessment and then some of the pointing to a separate document or a use...

Export will be about ECC information, such as in: > https://github.com/openssl/openssl/blob/master/README (last paragraph) in a file? There is another file case which could be considered for marking in a similar...

Hello @pengale thanks for pointing out it is useful. it is already in progress. (and I thought you might have been aware of it?) There are two points to this...