close
  • To chevron_right

    Takedown Notice Wipes Game Boy Advance Emulator From GitHub

    news.movim.eu / TorrentFreak · Friday, 24 June - 20:59 · 2 minutes

gba mario Playing games using browser-based emulators is a niche pastime of some of the most dedicated gamers.

For Game Boy Advance fans there are a few websites that offer this option, albeit without permission from Nintendo.

While emulators that utilize all of their own code don’t break the law, they can face legal issues when packaged with pirated ROMs and distributed to the public. Nintendo is not happy with this activity and has cracked down on it on several occasions.

Nintendo’s Emulator Crackdown

In 2015, the Japanese gaming giant already asked GitHub to remove a Game Boy Advance repository, hosted by the user “jsemu.” This worked out initially but soon after GitHub took action, copies started to appear. This included one shared by the user “jsemu3”, which Nintendo took down in 2018.

Since then many passionate Nintendo fans have found their way to yet another alternative game collection. Again, it was uploaded by a user with a familiar-sounding name; jsemu2.

This site , hosted by GitHub, has been online for a few years but this week visitors were welcomed by a 404 error. The error doesn’t mention the reason for the removal but we tracked down a DMCA notice that provides an explanation.

ESA Steps In

The takedown request was sent by the Entertainment Software Association (ESA), which represents Nintendo and other videogame companies. According to ESA, the site in question infringes on the copyrights and trademarks of its members.

“Our review of the Website indicates that it is has been marketing or otherwise making available products and/or services that infringe on ESA Members’ copyrights and trademarks,” the notice reads.

esa takedown

It appears that this is the third time that ESA has targeted this site. In its takedown request, the Association mentions that two earlier attempts failed, as GitHub requested “additional notice.”

“We are hopeful that this revised notice contains the necessary information to cause removal of the infringing uses of ESA Members’ intellectual property,” ESA writes. And indeed, this one was sufficient.

ESA’s takedown request lists the main URL where all the games were stored and also points to 75 of the ‘launchers’ directly. The site itself actually listed 98 games, but those that aren’t specifically mentioned have been removed as well.

Persistent Problem

Whether this will solve the problem completely seems doubtful. As history has shown, new copies are bound to pop up. In fact, nostalgic gamers can easily find alternatives, even on GitHub.

Finally, it is worth noting that the code for the Game Boy Emulator itself, without the pre-loaded games, is open source and still hosted elsewhere on GitHub . Nintendo doesn’t appear to have an issue with it, or it has no legal grounds to take action, as it has been online for over a decade now.

From: TF , for the latest news on copyright battles, piracy and more.

  • chevron_right

    Github Copilot, l’IA qui aide à coder, connait toujours des limitations

    news.movim.eu / Numerama · Wednesday, 22 June - 13:01

Présenté il y a un an, le logiciel d'aide à la programmation de Github est désormais ouvert à tous et toutes. Il reste encore beaucoup de questions sans réponses sur ses capacités. [Lire la suite]

Abonnez-vous aux newsletters Numerama pour recevoir l’essentiel de l’actualité https://www.numerama.com/newsletter/

  • To chevron_right

    Blizzard: No Piracy Filters? That’s Evidence of Intentional Infringement

    news.movim.eu / TorrentFreak · Wednesday, 25 May - 17:57 · 5 minutes

epic fail This week marked the 10th anniversary of Google’s important decision to begin publishing DMCA takedown notices sent to the company.

Over the last decade, online platforms including Twitter, Wikipedia, Medium and Github joined this transparency movement by submitting their notices to the Lumen Database . This archive not only allows rightsholders to monitor trends relevant to them, but also shines light on how copyright can be abused to impede the free flow of information.

A DMCA notice we’re highlighting today is available thanks to Github’s transparency. The notice, sent by anti-piracy company Irdeto on behalf of Blizzard Entertainment, is verifiably legitimate and addresses a genuine case of copyright infringement.

Github user ‘Chef Nomi’ (who was central to the SushiSwap crypto controversy ) had not only taken the name of one of Blizzard’s characters but was also using Blizzard’s artwork in his avatar. As expected, the notice received full cooperation from Github under the DMCA and the offending content was removed as the law requires.

So that’s that then? Well not exactly.

No Proactive Piracy Filters? That’s Evidence of Intentional Infringement

In addition to the takedown request, the notice also contains an unsolicited lecture on Github’s supposed liabilities under copyright law. It includes a strong suggestion that Github’s failure to deploy proactive piracy filtering technologies to prevent any future violations of Blizzard’s rights is “evidence of intentional facilitation” of its users’ copyright infringements.

If applicable, this would be an extraordinarily big deal for Github but absolutely terrifying for a small yet honest tech platform responding in good faith to a DMCA notice. But, as astronomer Carl Sagan once said, an extraordinary claim requires extraordinary proof. And here’s another applicable wisdom: context is everything .

In this case, there is no proof that the additional statements in the notice are relevant to the conduct of Github, or its liability under copyright law. Indeed, the very lawsuit the notice’s claims are culled from was the subject of a landmark U.S. Supreme Court copyright ruling that adds significant nuance.

Among other things, it broadly establishes that a responsible platform like Github, that takes its legal responsibilities seriously, can not be held liable for its users’ infringements simply due to the absence of proactive filtering. And here’s why.

Context is Everything

When major movie studios, record labels, and other copyright holders sued peer-to-peer file-sharing companies Grokster and Streamcast, little did they know their case would end in a landmark 2005 ruling by the Supreme Court.

In a nutshell, the plaintiffs in MGM v. Grokster argued that users of the defendants’ file-sharing software (Grokster and Morpheus) were sharing millions of music tracks and videos with each other, in breach of copyright law. Crucially, the copyright holders insisted that since Grokster and Streamcast were complicit in those violations, they could be held liable for third-party infringement.

In response, the peer-to-peer companies pointed to a Supreme Court precedent set in the so-called ‘ Betamax case ‘, noting that a maker of technology used to infringe copyright can not be held liable for infringement (even if it knew that the technology was being used for infringement) as long as the technology is “capable of substantial non-infringing uses.”

That defense served the companies well in the lower courts but in the Supreme Court, all hope of relying on the Betamax case evaporated when the thorny issue of intent was factored into the equation.

In brief, the peer-to-peer companies specifically targeted their software at former users of Napster in the knowledge that the overwhelming majority of files available on Napster (before it was shut down) were infringing and that many of its users were infringers.

Internal documentation also revealed that the aim of the defendants was to have as many copyrighted files on their networks as possible. Grokster even sent out a newsletter stating that popular copyrighted content could be downloaded from its client.

“Grokster and StreamCast’s efforts to supply services to former Napster users, deprived of a mechanism to copy and distribute what were overwhelmingly infringing files, indicate a principal, if not exclusive, intent on the part of each to bring about infringement,” the Supreme Court wrote .

“The unlawful objective is unmistakable,” it added.

So What About Filtering?

Rather than dealing directly with the decision in the Betamax case, the Supreme Court ultimately settled on intent as the key factor in Grokster. Since the owners of the file-sharing clients advertised them as tools for infringing purposes, other aspects of their behavior could also be considered as contributing factors in the case against them.

Specifically, MGM showed that Grokster and Streamcast made no attempt to develop tools that could have diminished the volume of copyright infringements being carried out by users of their software. MGM said that the companies could’ve used filtering software to prevent piracy, but did not.

The Supreme Court agreed this was indeed a contributing factor. In light of the companies’ established unlawful objective, “ ..this evidence underscores Grokster’s and StreamCast’s intentional facilitation of their users’ infringement.

And there it is in black and white. It’s almost exactly the same text sent in the Github notice informing the company that a “failure to use available filtering technologies to diminish infringement is evidence of intentional facilitation of infringement.”

By now it should be crystal clear why this statement demands context and why it doesn’t apply to Github – it does not have an established unlawful objective. But just in case more clarity is needed on filtering and similar mechanisms, here’s the Supreme Court’s assessment:

“Of course, in the absence of other evidence of intent, a court would be unable to find contributory infringement liability merely based on a failure to take affirmative steps to prevent infringement, if the device otherwise was capable of substantial noninfringing uses. Such a holding would tread too close to the Sony safe harbor.”

The DMCA notice sent to Github can be found here

From: TF , for the latest news on copyright battles, piracy and more.

  • chevron_right

    Devs discover “realityOS” hints in Apple logs and code

    news.movim.eu / ArsTechnica · Wednesday, 9 February - 21:40

An enormous ring-shaped building on a green campus.

Enlarge / Apple's global headquarters in Cupertino, California. (credit: Sam Hall/Bloomberg via Getty Images )

Software developers have discovered apparent references to a new Apple operating system called "realityOS" in App Store upload logs and in GitHub repositories used by the company.

The references were shared widely by developers Rens Verhoeven and Steve Troughton-Smith on Twitter. Verhoeven tweeted :

The tweet was accompanied by a screenshot from the logs that included "com.apple.platform.realityos" alongside a similar reference for an existing platform, "com.apple.platform.watchos."

Read 7 remaining paragraphs | Comments

index?i=LbWbs-Cm2RI:Niv7qlKFBwE:V_sGLiPBpWUindex?i=LbWbs-Cm2RI:Niv7qlKFBwE:F7zBnMyn0Loindex?d=qj6IDK7rITsindex?d=yIl2AUoC8zA
  • chevron_right

    Au fait, pourquoi GitHub s’appelle GitHub ?

    news.movim.eu / Numerama · Sunday, 23 January - 20:13

La fin de l'article va vous surprendre. [Lire la suite]

Abonnez-vous aux newsletters Numerama pour recevoir l’essentiel de l’actualité https://www.numerama.com/newsletter/

  • chevron_right

    Microsoft a dépensé autant pour Activision Blizzard que pour ses 5 rachats les plus chers

    news.movim.eu / Numerama · Tuesday, 18 January - 19:30

Difficile de se figurer le montant mobilisé par Microsoft pour se payer Activision Blizzard. Une autre manière d'appréhender ces 70 milliards de dollars est de noter qu'il a fallu un montant similaire à Microsoft pour se payer... les 5 entreprises suivantes qui lui ont coûté le plus cher. [Lire la suite]

Abonnez-vous aux newsletters Numerama pour recevoir l’essentiel de l’actualité https://www.numerama.com/newsletter/

  • chevron_right

    Comment trouver les adresses emails des utilisateurs de Github

    news.movim.eu / Korben · Sunday, 28 November, 2021 - 08:00 · 1 minute

Vous faites du logiciel libre et vous cherchez à contacter l’un de vos pairs ?

Pas de souci avec l’outil d’OSINT baptisé Zen qui scanne les dépôts publics Github et vous sort la liste de toutes les boites mail et pseudo des contributeurs au projet que vous visez. Attention, ça ne pirate rien… ça scanne simplement les dépôts et les pages Github à la recherche d’emails en clair.

Pour l’installer, faites un

git clone https://github.com/s0md3v/Zen.git

Puis placez-vous dans le répertoire

cd Zen

Et installez les dépendances :

pip install -r requirements.txt

Ensuite vient le moment d’utiliser le script. Si vous avez uniquement le pseudo de la personne et que vous voulez son mail, entrez simplement :

python zen.py username

Si vous avez l’URL du dépôt Github, c’est comme ça :

python zen.py https://github.com/username/repository

Et si vous ciblez une organisation / société précise, c’est cette commande qu’il vous faudra :

python zen.py organization --org

Il n’y a pas de limite mis à part le nombre de requêtes que vous pouvez adresser à Github à la minute. Si vous n’êtes pas authentifié sur le site, vous serez limité à 60 requêtes par heure. Authentifié, ce chiffre passe à 6000 requêtes par heure.

Zen permet de faire du multithreading histoire d’aller plus vite. Et vous pouvez même vérifier sur la base haveibeenpwned.com si tel ou tel email a été poutré.

python zen.py username --breach

Amusez-vous bien, mais ne faites pas de bêtise. Je vous rappelle que le spam est illégal. Et si votre email traine sur Github, pensez à l’enlever ou à en changer. Je vous invite à lire ce guide qui vous expliquera comment protéger vos données personnelles sur Github .

KorbensBlog-UpgradeYourMind?d=yIl2AUoC8zAKorbensBlog-UpgradeYourMind?i=iZ2qBIWK2ao:-lwraesVAFM:D7DqB2pKExkKorbensBlog-UpgradeYourMind?i=iZ2qBIWK2ao:-lwraesVAFM:GG6oivYVkFsKorbensBlog-UpgradeYourMind?d=qj6IDK7rITsKorbensBlog-UpgradeYourMind?i=iZ2qBIWK2ao:-lwraesVAFM:gIN9vFwOqvQKorbensBlog-UpgradeYourMind?d=7Q72WNTAKBA
  • In chevron_right

    GitHub will require 2FA for some NPM registry users

    pubsub.slavino.sk / infoworldcom · Monday, 22 November, 2021 - 11:00 edit

In light of two recent security incidents impacting the popular NPM registry for JavaScript packages, GitHub will require 2FA (two-factor authentication) for maintainers and admins of popular packages on NPM.

The 2FA policy, intended to protect against account takeovers, will be put in place starting with a cohort of top packages in the first quarter of 2022, GitHub said in a bulletin published on November 15. GitHub became stewards of the registry after acquiring NPM in 2020 .

To read this article in full, please click here


Značky: #JavaScript, #Security, #Node.js, #GitHub, #Rozne