Uploading to the library directory does not confirm file overwrite

[Steve Organ]

Rich Text Editor Upload Images does not warn of existing file with same name and overwrites it causing data loss. Any prior articles that were using the prior image now have the new image instead of the old one. Not only does the RTE not prevent this from happening, it doesn't even warn the user that another file it out there with the same name.

Issue description from customer: When users upload images, there does not appear to be any control over the filenames. Also, there is no control/tracking of what attachment is being used by what article, which makes the issue potentially more risky because files will pile up over time. If there is a file in the attachment directories with a given filename, and somebody uploads a file with the same name, there is no warning or restriction, the newly uploaded file simply overwrites the existing file. Now that filenames are a free-for-all, I think it is highly likely that we will encounter this issue going forward.

[Michael Osipov]

Any implementation renames a new file if another with the same name already exists.

Which server-side implementation do you use?

[Alfonso Martínez de Lizarrondo]

If they use a custom connector (as stated in #3823) it's a problem in their code