diff --git a/2024/02/2024-02-01-swe.md b/2024/02/2024-02-01-swe.md new file mode 100644 index 000000000..77b99d9e2 --- /dev/null +++ b/2024/02/2024-02-01-swe.md @@ -0,0 +1,181 @@ +**Are you the copyright holder or authorized to act on the copyright owner's behalf?** + +Yes, I am the copyright holder. + +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** + +No + +**Does your claim involve content on GitHub or npm.js?** + +GitHub + +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** + +The 18 uploaded repositories are customer projects and company data developed by our agency. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.** + +All 18 repositories under https://github.com/fiea85s?tab=repositories. + +swe_template +The Swe template contains the basis of a TYPO3 extension, which is based on the Swe core. +An extension generator can be used to generate an empty, new extension from this template. +- this repository has been removed since my last DMCA takedown request + +swe +Repo: https://github.com/fiea85s/swe +- internal Website + +stephans-garden +Repo: https://github.com/fiea85s/stephans-garden +Customer website (published) +- [private] + +region-nordhessen +Repo: https://github.com/fiea85s/region-nordhessen +Customer website (under development) +- [private] + +promotion-nordhessen +Repo: https://github.com/fiea85s/promotion-nordhessen +Customer website (under development) +- [private] + +pride-nordhessen +Repo: https://github.com/fiea85s/pride-nordhessen +Customer website (published) +- [private] + +payone +Repo: https://github.com/fiea85s/payone +Customer website (under development) +- [private] + +pajunk +Repo: https://github.com/fiea85s/pajunk +Customer website (under development) +- [private] + +metallbau-schwedes +Repo: https://github.com/fiea85s/metallbau-schwedes +Customer website (under development) +- [private] + +landingpage-swe +Repo: https://github.com/fiea85s/landingpage-swe +Internal Website (published) +- [private] + +konfigurator-prototyp +Repo: https://github.com/fiea85s/konfigurator-prototyp +Customer website (under development) +- [private] + +koebberling +Repo: https://github.com/fiea85s/koebberling +Customer Website (published) +- [private] + +inovagis +Repo: https://github.com/fiea85s/inovagis +Customer website (under development) +- [private] + +heracles-capital +Repo: https://github.com/fiea85s/heracles-capital +Customer website (published) +- [private] + +dahmen +Repo: https://github.com/fiea85s/dahmen +Customer website (published) +- [private] (master) +- [private] (dev) + +cdu +Repo: https://github.com/fiea85s/cdu +Customer website (under development) +- The project is currently only local to our development + +altenso +Repo: https://github.com/fiea85s/altenso +Customer website (under development) +- [private] + +lynx +Repo: https://github.com/fiea85s/lynx +- locally developed project; basis for all TYPO3 projects + +**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.** + +All 18 repositories under https://github.com/fiea85s?tab=repositories should be removed. + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +Yes + +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** + +The private [private] are located on a password-protected platform and can only be viewed and cloned with a password or a token. The suspected person was probably still in possession of an old token that allowed access to the [private]. +We have updated the tokens last week. + +**How is the accused project designed to circumvent your technological protection measures?** + +Unauthorized access to our private [private] and publication for the public on GitHub. + +**Have you searched for any forks of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.** + +We have found no forks right now. + +**Is the work licensed under an open source license?** + +Yes + +**Which license?** + +GNU General Public License, version 2 or later + +**How do you believe the license is being violated?** + +TYPO3 and the extensions are licensed under GNU General Public License, version 2 or later. + +However, the private [private] have been individually developed by us for our customers and contain customer data. +They were downloaded without authorization. +By publishing the [private], sensitive data such as user names, e-mail addresses and encrypted passwords were disclosed. + +**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.** + +All 18 repositories under https://github.com/fiea85s?tab=repositories should be removed completely. + +**What would be the best solution for the alleged infringement?** + +Reported content must be removed + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +We suspect a former [private] who previously uploaded software that was programmed in our company to GitHub. +A legal process is already underway with a cease-and-desist declaration regarding the publication of company information. +The lawyer has also already been informed about the incident reported here and initiated a criminal complaint. + +**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** + +**I have taken fair use into consideration.** + +**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** + +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +Smart Web Elements +[private] +[private] +[private] +[private] +[private] +Tel: [private] + +**Please type your full legal name below to sign this request.** + +[private]