Skip to main content

GitHub confirms it has blocked developers in Iran, Syria and Crimea

The impact of U.S. trade restrictions is trickling down to the developer community. GitHub, the world’s largest host of source code, is preventing users in Iran, Syria, Crimea and potentially other sanctioned nations from accessing portions of the service, chief executive of the Microsoft-owned firm said.

Over the weekend, GitHub CEO Nat Friedman wrote on Twitter that like any other “company that does business in the US,” GitHub is required to comply with the U.S. export law. The confirmation comes months after work collaboration service Slack, too, enforced similar restrictions on its platform.

As part of the push, Friedman said GitHub has enforced new restrictions to prevent users in sanctioned countries from accessing private repositories and GitHub Marketplace, as well as maintaining private paid organization accounts.

A selection of GitHub services such as access to public repositories will remain available to everyone, the company said in a statement on its website. “This includes limited access to GitHub public repository services (such as access to GitHub Pages and public repositories used for open source projects), for personal communications only, and not for commercial purposes.”

For developers intending to store export-controlled data, GitHub points them to its enterprise server offering, a self-hosted virtual appliance that can be run within users’ own data center or virtual private cloud.

Several developers began to complain about their inability to access some of GitHub’s services last week. News outlet ZDNet reported about a Russian developer living in Crimea whose GitHub account had been restricted, for instance. Hamed Saeedi Fard, a developer who is based in Iran, wrote in a Medium post that his GitHub account was blocked without any prior notice or the option to back up his data.

Interestingly, the restrictions are imposed based on a user’s location — by tracking their IP address and payment history — instead of validating their nationality and ethnicity, GitHub said on its website, where it mentions that Cuba and North Korea are also facing the U.S. sanctions. For those who are considering a workaround by using VPNs (virtual private networks), GitHub has ruled out that possibility: People in U.S.-sanctioned countries “are prohibited from using IP proxies, VPNs, or other methods to disguise their location when accessing GitHub.com services.” It remains to be seen how GitHub enforces the rule.

Banned users who believe their accounts have been wrongfully suspended can fill out an appeal form, where they must provide a copy of their government-issued photo ID to prove their current residency along with a selfie, signaling GitHub’s step towards imposing real-name identity check.



from TechCrunch https://ift.tt/2Ms8NLb
Labels:

Comments

Post a Comment

Popular posts from this blog

How To Play Doom – And More – On An NES

Doom was a breakthrough game for its time, and became so popular that now it’s essentially the “Banana For Scale” of hardware hacking. Doom has been ported to countless devices, most of which have enough processing ability to run the game natively. Recently, this lineup of Doom-compatible devices expanded to include the NES even though the system definitely doesn’t have enough capability to run it without special help. And if you want your own Doom NES cartridge, this video will show you how to build it . We featured the original build from [TheRasteri] a while back which goes into details about how it’s possible to run such a resource-intensive game on a comparatively weak system. You just have to enter the cheat code “RASPI”. After all the heavy lifting is done, it’s time to put it into a realistic-looking cartridge. To get everything to fit in the donor cartridge, first the ICs in the cartridge were removed (except the lockout IC) and replaced with custom ROM chips. Some modifica...
Post a Comment
Read more

Try NopSCADlib for your Next OpenSCAD Project

Most readers of this site are familiar by now with the OpenSCAD 3D modeling software, where you can write code to create 3D models. You may have even used OpenSCAD to output some STL files for your 3D printer. But for years now, [nophead] has been pushing OpenSCAD further than most, creating some complex utility and parts libraries to help with modeling, and a suite of Python scripts that generate printable STLs, laser-ready DXFs, bills of material, and human-readable assembly instructions complete with PNG imagery of exploded-view sub-assemblies. Recently [nophead] tidied all of this OpenSCAD infrastructure up and released it on GitHub as NopSCADlib . You can find out more by browsing through the example projects and README file in the repository, and by reading the announcement blog post on the HydraRaptor blog . Some functionality highlights include: a large parts library full of motors, buttons, smooth rod, et cetera many utility functions to help with chamfers, fillets, precis...
Post a Comment
Read more

The Newbie’s Guide To JTAG

Do you even snarf? If not, it might be because you haven’t mastered the basics of JTAG and learned how to dump, or snarf, the firmware of an embedded device. This JTAG primer will get you up to snuff on snarfing, and help you build your reverse engineering skills. Whatever your motivation for diving into reverse engineering devices with microcontrollers, JTAG skills are a must, and [Sergio Prado]’s guide will get you going. He starts with a description and brief history of the Joint Test Action Group interface, from its humble beginnings as a PCB testing standard to the de facto standard for testing, debugging, and flashing firmware onto devices. He covers how to locate the JTAG pads – even when they’ve been purposely obfuscated – including the use of brute-force tools like the JTAGulator . Once you’ve got a connection, his tutorial helps you find the firmware in flash memory and snarf it up to a file for inspection, modification, or whatever else you have planned. We always apprec...
Post a Comment
Read more