News for hackers. Stuff that matters.
Re:We are currently taking a DDoS attack and are working to ... by analog on Saturday March 23, 2013 @08:07PM (#5430424)
Yes, but if the repo was hosted on Github rather than internally then the slow VPN provisioning wouldn't have been an issue.

(Good) web services like Github tend to reduce friction, corporate bureaucracies tend to increase friction.

Re:We are currently taking a DDoS attack and are working to ... by pifflesnort on Saturday March 23, 2013 @08:35PM (#5430501)
(Good) corporate services wouldn't have had slow VPN provisioning.

This has nothing to do with Github, other than the fact that Github would let you end-run all rules about data protection, backups, centralized administration of user access, and everything else that you don't individually have to worry about, but the management and IT at the company you work for does.

Re:We are currently taking a DDoS attack and are working to ... by analog on Saturday March 23, 2013 @09:03PM (#5430569)
"centralized administration of user access"

This is exactly the sort of thing I'm talking about. Let the team working on the code decide who has access to the code. Not some person in a different part of the country who has no idea what the code does.

Re:We are currently taking a DDoS attack and are working to ... by hp50g on Sunday March 24, 2013 @04:47AM (#5431499)
Actually most of our developers can't be trusted with this. We have certain regulatory requirements.

We have active directory and its all managed there. If someone needs access, their role defines it. If someone wants access they have to ask.

Re:We are currently taking a DDoS attack and are working to ... by pifflesnort on Saturday March 23, 2013 @11:04PM (#5430905)
That's a short-sighted selfish view that fails to take into account the responsibilities of the organization at large.
Re:We are currently taking a DDoS attack and are working to ... by hp50g on Sunday March 24, 2013 @04:57AM (#5431512)
Actually it would be even worse as we can't risk people pushing our code to their private repo so Mr Firewall goes "no way". Another problem: we dont know which repo we're pushing to at a network level.

Code theft is a major problem. Not because the code is crap and we're embarrassed (unlike VMware and Microsoft code leaks), but because its valuable.

Re:We are currently taking a DDoS attack and are working to ... by analog on Sunday March 24, 2013 @07:52AM (#5431795)
What do you do to stop people emailing code out?
Re:We are currently taking a DDoS attack and are working to ... by hp50g on Sunday March 24, 2013 @08:46AM (#5431902)
We have content filters and policy based email management. You can't send documents or content through the mail gateway at all.
Re:We are currently taking a DDoS attack and are working to ... by analog on Sunday March 24, 2013 @10:13AM (#5432081)
And gmail?
Re:We are currently taking a DDoS attack and are working to ... by hp50g on Sunday March 24, 2013 @01:17PM (#5432695)
They don't have access to that :)
Re:We are currently taking a DDoS attack and are working to ... by analog on Sunday March 24, 2013 @02:25PM (#5432930)
Haha, I guess I should have seen that one coming:)

Do you whitelist or blacklist the internet?

Re:We are currently taking a DDoS attack and are working to ... by hp50g on Monday March 25, 2013 @08:31AM (#5436627)
Whitelist and restrict to certain staff.

We have to cover our asses as we deal with classified information and financial data.

We even search people leaving the building.