News for hackers. Stuff that matters.
Re:Hello, GitHub by SiVal on Monday June 04, 2018 @04:58PM (#17232399)
That's amazing. Contrast that to my friend who works on code at Apple that's so guarded that he can't even access it from Apple HQ. He has to travel to his office in an unmarked Apple bldg several miles from HQ (in an unmarked van) and access the code from inside the bldg. Any attempt to work on his code outside that bldg, on the Apple employee shuttle for example, will result in immediate firing with possible criminal charges. Admittedly, that's not the usual Apple employee, but the contrast between that and Microsoft's, which may as well be hosted on a set of Chinese night market DVDs, is LOL-worthy.
Re:Hello, GitHub by jodrellblank on Monday June 04, 2018 @05:15PM (#17232530)
LOL-worthy

and yet, which company released an OS update with an open root account with no password, patched it in a way that broke file sharing, then a couple of months later released an update with another password bypass bug? Hobbling people with security theatre isn't begetting good or secure code.

Re:Hello, GitHub by spydum on Monday June 04, 2018 @07:55PM (#17233759)
Opsec and AppSec usually handled by different teams :)
Re:Hello, GitHub by shubb on Monday June 04, 2018 @05:56PM (#17232968)
This sounds proportionate if a state might go after the code. For example phone encryption might be a big prize for the Chinese or even American government.

Microsoft actually hand over OS code to states regularly for certain contracts so I figure they don't need to protect most of thier code like that.

Re:Hello, GitHub by electronvolt on Monday June 04, 2018 @06:23PM (#17233177)
I disagree. Phone encryption should ideally be open source-able and it's security should rely as entirely on a device specific key as possible.

I think this makes more sense for a secret project (e.x. the next iPhone), but honestly as a security person it seems overkill for anything outside national security responsible code, like state sponsored malware.

I also find it strange that the code is apparently somehow accessible outside that building (see the fired comment). If this was anything beyond security theatre, it'd be on an airgapped network and that wouldn't even be a concern (as the employee wouldn't be able to access the code from their laptop). Seems excessive for very little gain.

Re:Hello, GitHub by doctorsher on Monday June 04, 2018 @07:29PM (#17233587)
I wouldn't take SiVal's comment as ground truth. I think it conflates rules for general employees with rules for his friend, and mixes it with a dash of unfounded hyperbole (criminal charges?).
Re:Hello, GitHub by SiVal on Monday June 04, 2018 @08:19PM (#17233906)
The code isn't available outside the building unless someone takes it outside, which they make clear is not only a fireable offense but might qualify as criminal. They made it quite clear: If you're in crunch mode, don't be tempted to just take a bit of work with you to get a bit more done on the long shuttle ride.
Re:Hello, GitHub by doctorsher on Monday June 04, 2018 @09:31PM (#17234257)
Fair enough. I obviously don't know your friend or his project, so I can't with certainty say anything about his situation. I viewed your post through a critical lens because the details given didn't match my experience or the experience of any of my old colleagues, and you are a second-hand witness.
Re:Hello, GitHub by foo101 on Monday June 04, 2018 @09:37PM (#17234281)
I am going to agree with what doctorsher said in response to your comment. I can confirm that what SiVal said is not a typical experience in Apple.
Re:Hello, GitHub by ergothus on Monday June 04, 2018 @06:49PM (#17233339)
For reading, I agree, but if you're making changes it is a different story.
Re:Hello, GitHub by nathantotten on Monday June 04, 2018 @05:10PM (#17232492)
This has to be something very mission critical like phone encryption. No way this is the norm even at Apple.
Re:Hello, GitHub by crazypyro on Monday June 04, 2018 @05:25PM (#17232659)
I thought it was widely known Apple was extremely secretive, compared to the broader tech company at the very least.
Re:Hello, GitHub by saagarjha on Monday June 04, 2018 @05:22PM (#17232618)
> unmarked van

You may think it’s unmarked, but if you know how to spot them they’re very easy to pick out.

Re:Hello, GitHub by sullyj3 on Monday June 04, 2018 @07:03PM (#17233429)
If I was an intelligence agency, I would do the trivially obvious thing and only use "unmarked cars" when I didn't care about being spotted, and an actual nondescript vehicle the rest of the time.
Re:Hello, GitHub by gowld on Monday June 04, 2018 @07:32PM (#17233615)
What's the difference between an "unmarked car" and a "nondescript vehicle" ?

You think the CIA would do their clandestine work on cars labeled "CIA" ?

Re:Hello, GitHub by dragonwriter on Monday June 04, 2018 @07:36PM (#17233649)
> What's the difference between an "unmarked car" and a "nondescript vehicle" ?

Unmarked police cars often have multiple radio antennae, flexible lights, and even government plates, they simply lack explicit police markings and light bars.

Re:Hello, GitHub by bambataa on Tuesday June 05, 2018 @03:16AM (#17235571)
Surely an unmarked van owned by Apple would have none of that?
Re:Hello, GitHub by jey on Tuesday June 05, 2018 @10:23AM (#17237853)
The point is that the "unmarked" vehicle sticks out as unusual even without having "Apple" or "Police" emblazoned on its side.