Live data from Hacker News

GitHub is investigating unauthorized access to their internal repositories

twitter.com

311–320 of 359 posts

Re: GitHub is investigating unauthorized access to their internal repositories

#311
post #240

Will they revisit the decision to not add a permission model to VSCode extensions? https://news.ycombinator.com/item?id=43181789

how would that be enforced? unless extensions now be required to be WASM blobs, or otherwise using some very simple runtime. (ie. not JS/Node) I think we learned this with the JVM (applets) and the Flash player.

Is there no setfenv-like functionality in JavaScript (setfenv is Lua's way to set a sandboxed execution environment)? That's surprising. TIL.

Re: GitHub is investigating unauthorized access to their internal repositories

#312

Unfortunately if it was from a compromised extension this is going to be more justification for creating closed environments like what Google is doing with android and Apple has already done with iPhone.

In the age of LLMs, vetting can even be done in a CI/CD. What's the big deal?

Re: GitHub is investigating unauthorized access to their internal repositories

#313
post #18

The security issue aside, seeing more companies push announcements like these on X as the only official source is a trend I'm not sure I like. I can understand the rationale, this feels lighter and not something that belongs on status.github.com or the blog. Maybe what's actually missing is an official channel for ephemeral stuff on a domain they own, somewhere between a status page and a tweet? Just sharing an obser…

I don't see why this wouldn't fit on status.github.com. Social media posts were literally called "status updates" at some point.

It is a closed ecosystem, where - as a viewer - you have gated access and - as a publisher - require your viewers to consent to a third-partys rule. Accessibg ststus.github.com has only the terms of GitHub involved, not also Twitter/X/...

Re: GitHub is investigating unauthorized access to their internal repositories

#314
post #130
post #18

The security issue aside, seeing more companies push announcements like these on X as the only official source is a trend I'm not sure I like. I can understand the rationale, this feels lighter and not something that belongs on status.github.com or the blog. Maybe what's actually missing is an official channel for ephemeral stuff on a domain they own, somewhere between a status page and a tweet? Just sharing an obser…

Are you from 2015? Companies have been announcing stuff on Twitter for a decade, and the rest of social media has been regurgitating Twitter posts for almost as long. Newspapers routinely quote Twitter. All that happened before they even renamed it to X. I’m not saying it’s a good idea. I am saying it somehow became the single source of truth for the Internet with all that entails.

Totally agree but I think that it's fairly common for an enterprise company (like GitHub) to also have a central place that platform publishes these kinds of updates in addition to socials. I think it's odd, personally, that it's literally only been announced on twitter without a link to an announcements page or similar. Lots of enterprises still block crap like twitter and facebook, so it feels goofy to broadcast this _only_ to a source that paying customers may not even be able to access it.

Re: GitHub is investigating unauthorized access to their internal repositories

#316
post #127

Earlier quoted context omitted.

Who the heck follows Github on Snapchat, TikTok, YouTube, Pinterest, Instagram, Reddit, Facebook, WeChat? Wherever they posted, there’s at this time two articles on the Hacker News front page. Sounds like they have reached their audience.

It's to point out how comparatively small X is. It's in the same ballpark as Pinterest and Quora. Github decided not to use email (which every Github customer has), their sites, or their otherwise active BlueSky.

It's not small in the tech community though. Users are not distributed evenly among platforms. Others may have more users but not as many tech users.

Re: GitHub is investigating unauthorized access to their internal repositories

#317

That's the reason I stopped installing random extensions and even themes in VS Code, they are too dangerous.

Same (Only some default plugins, and from known sources), and VS code even don't have a html preview functionality so I had to vibecode one (took about 10 mins, e2e).

Re: GitHub is investigating unauthorized access to their internal repositories

#318

Earlier quoted context omitted.

As a developer or security researcher, you're able to download and run GitHub Enterprise Server. I'm not sure having access to the full source code makes a meaningful difference for most of GitHub's surface area, given it's largely Ruby.

LLMs can't really parse compiled code to find exploits, maybe code in scripting languages (python, js, etc) even if minified. So I don't quite agree with you, having access to the source can definitely help find exploits even in pre-LLM days.

Also, the Github enterprise code is "obfuscated" but it uses a trivially reversible method just meant to be a minor roadblock. After you get past that you get the full ruby source code, no minification or anything.

For a while the key was literally:

> This obfuscation is intended to discourage GitHub Enterprise customers from making modifications to the VM. We know this 'encryption' is easily broken.

Re: GitHub is investigating unauthorized access to their internal repositories

#319

Unfortunately if it was from a compromised extension this is going to be more justification for creating closed environments like what Google is doing with android and Apple has already done with iPhone.

Why not simply have both? This does not have to be an either-or decision. Have a default repository with vetted extensions, but leave the option to install from other sources open.

Enterprise will always choose the less risky option so if there is either-or its vetted extensions only.

For consumer it's kind of already like this in a way, there are "verified" extension providers.

Overall, I think this is just going to lead to a lot more scrutiny. I'm sure one of the first things asked when this was discovered was how can it be prevented and I'm sure one of the first answers was get VsCode to lock down extensions. Enterprises love the easy answers

Re: GitHub is investigating unauthorized access to their internal repositories

#320

Earlier quoted context omitted.

I installed Zed on a work machine at a well-known software company and a week later they forced me to reimage my machine because they got some alert that the app was attempting to access browser credentials :( No shade on Zed, sometimes in-house security tools just don't like new software.

> they got some alert that the app was attempting to access browser credentials :( That sounds pretty specific.

According to the email I initially received for this alert, zed.exe was attempting to access its own folder within the AppData directory. Nothing more normal than that, no?

No idea how that related to what I was told by the sec people shortly afterwards.

Post reply on HN