News for hackers. Stuff that matters.
Re:Creative usernames and Spotify account hijacking by eli on Tuesday June 18, 2013 @06:56PM (#5902588)
Easy to implement in a small project. Not so easy in a large enterprise project likely comprised of multiple interconnected systems.
Re:Creative usernames and Spotify account hijacking by TillE on Tuesday June 18, 2013 @07:56PM (#5902822)
Not a good excuse. There are plenty of enormous projects that provide only one basic interface to a bit of information. See every operating system API for examples.
Re:Creative usernames and Spotify account hijacking by jzwinck on Tuesday June 18, 2013 @08:09PM (#5902864)
How about the API to allocate memory in Windows?

VirtualAlloc: http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

VirtualAllocEx: http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

VirtualAllocExNuma: http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

It all started out nice and clean I'm sure, but within a few years you start to see many more than one basic interface to some things.

Re:Creative usernames and Spotify account hijacking by brokenparser on Wednesday June 19, 2013 @02:33AM (#5904020)
And {Global,Heap,Local}{,re}{Alloc,Free,Lock,Unlock}. 4 sets of APIs just to allocate memory. Although Local* and Global* are mapped to Heap for a while now and (IIRC) (un)lock functions don't do anything (but they used to). This BC is still required today.