Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment After reading that... (Score 1) 542

... I wanted to kill myself, but then again, throwing myself in front of a bus isn't carbon neutral. What's the carbon-footprint of a handgun? A rope? A bridge, calulated per jumper? Aaaarrgggh.... Damned if i do and damned if i don't I guess i'll just hold my breath... (...and no, i'm _not_ being all that serious...)
IOS

Submission + - IPhone4 track user location (gsmarena.com)

kleuske writes: "Two security researchers in the UK have uncovered a disturbing truth. It appears iPhone 4's everywhere have been tracking their users movements with startling accuracy (unbeknownst to the users) and what is more, the ease at which this information can be deciphered is apparently as easy to open as say, a JPEG."

Comment Trust... (Score 1) 515

Ok. Along with Sony, Samsung is now on my personal purchase blacklist. I just don't get it, do these guys think they'll get away with stuff like that? Have the marketing&management clowns that came up with and approved of this crap even considered what this does to the firms credibility? Have they an IQ that exceeds their shoesize? (rethorical question).

Comment Just waiting for a crash and burn (Score 1) 112

Methinks the inventors have dramatically underestimated a) the learning capabilities of 2-to-5-year-olds b) the social intelligence of same, b) the destructive potential of same, and dramatically overestimated a) the everyday authority these toys will have in the eyes of 2-to-five year olds b) the electronics ability to differentiate between c) the willingness and/or ability of parent to feed toy with the behaviors mentioned. In short, this is a disaster waiting to happen. Woe to the parent that relies on one of these contraptions.

Comment Examples contain bugs... (Score 1) 534

The fun thing is that i've found at least three bugs in their example code other than the ones MITRE intended to illustrate. The most glaring of which would prevent the code from even getting compiled. http://cwe.mitre.org/data/definitions/805.html void host_lookup(char *user_supplied_addr){
struct hostent *hp;
in_addr_t *addr;
char hostname[64];
in_addr_t inet_addr(const char *cp);
/*routine that ensures user_supplied_addr is in
the right format for conversion */
validate_addr_form(user_supplied_addr);
addr = inet_addr(user_supplied_addr);
hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET);
strcpy(&hostname, hp->h_name);
}
The final strcpy will not work, since the first parameter is a pointer-to-pointer-to-char, instead of pointer-to-char.
Programming

The 25 Most Dangerous Programming Errors 534

Hugh Pickens writes "The Register reports that experts from some 30 organizations worldwide have compiled 2010's list of the 25 most dangerous programming errors along with a novel way to prevent them: by drafting contracts that hold developers responsible when bugs creep into applications. The 25 flaws are the cause of almost every major cyber attack in recent history, including the ones that recently struck Google and 33 other large companies, as well as breaches suffered by military systems and millions of small business and home users. The top 25 entries are prioritized using inputs from over 20 different organizations, who evaluated each weakness based on prevalence and importance. Interestingly enough the classic buffer overflow ranked 3rd in the list while Cross-site Scripting and SQL Injection are considered the 1-2 punch of security weaknesses in 2010. Security experts say business customers have the means to foster safer products by demanding that vendors follow common-sense safety measures such as verifying that all team members successfully clear a background investigation and be trained in secure programming techniques. 'As a customer, you have the power to influence vendors to provide more secure products by letting them know that security is important to you,' the introduction to the list states and includes a draft contract with the terms customers should request to enable buyers of custom software to make code writers responsible for checking the code and for fixing security flaws before software is delivered."

Comment Who cares (Score 1) 959

Not my computer, It does not give a damn wether i'm wearing casual clothes, corporate suit or nothing. not the customer, who can't see helpdesk personnel over the phone anyway. The suits care. The jocks care. The fashion-bitches care. Not any one who matters. So why bother? If I get a choice between a programmer with two different colored socks and ill matching shirt and trousers and once nicely-dressed up and quite fashionable when I need to get the code working, i'll _gladly_ choose the first. At least his mind isn't on his appearance all the time.

Slashdot Top Deals

Work is the crab grass in the lawn of life. -- Schulz

Working...