Skip to comments.
'DieHard' wards off memory attacks
Linux World ^
| 03 January 2007
| Matthew Broersma
Posted on 01/03/2007 5:13:04 PM PST by ShadowAce
click here to read article
Navigation: use the links below to view more comments.
first 1-20, 21-38 next last
1
posted on
01/03/2007 5:13:05 PM PST
by
ShadowAce
To: rdb3; chance33_98; Calvinist_Dark_Lord; Bush2000; PenguinWry; GodGunsandGuts; CyberCowboy777; ...
2
posted on
01/03/2007 5:13:20 PM PST
by
ShadowAce
(Linux -- The Ultimate Windows Service Pack)
To: ShadowAce
Has anyone downloaded this?
3
posted on
01/03/2007 5:16:48 PM PST
by
Kimmers
(It's not what you take when you leave this world behind, it's what you leave behind when you go)
To: ShadowAce
Rats! I thought this was about a cure for Alzheimer's.
4
posted on
01/03/2007 5:18:03 PM PST
by
pepperdog
To: Kimmers
I don't use Firefox so I guess I'll wait.
Probably MicroSoft will keep putting it off until the next OS upgrade. Or SP2 for Vista or something like that.
5
posted on
01/03/2007 5:19:33 PM PST
by
Duke Nukum
(To thine own self be true...or relatively true. --Guy Caballero)
To: ShadowAce
6
posted on
01/03/2007 5:19:37 PM PST
by
RebelTex
(Help cure diseases: http://www.freerepublic.com/focus/f-news/1548372/posts)
To: Kimmers
I wouldn't think we have many C and C++ programmers here.
If we do, they'll probably stick to malloc/free and new/delete. They're too proud that they never make mistakes to use something like this.
To: ShadowAce
Just get an iMAC...it just works.
I converted from PC to iMAC back in August.
This is the most fun I've had on a computer in a long time...
8
posted on
01/03/2007 5:19:57 PM PST
by
GRRRRR
( What's Next? - Get to the Driving Range and Groove My Swing...)
To: ShadowAce
I don't like probabalistic computing. Any properly-written program should know what memory pointers and handles are valid, and what ones aren't. Reducing the likelihood that careless memory accesses will cause damage will also tend to reduce the likelihood of them being found and fixed.
One thing I've been thinking I might like to see would be an eight-byte handle-plus-offset type, with both compiler support and hardware support for efficient access. I believe languages such as PostScript already implicitly use such types; if memory accesses using such types are validated, many types of memory corruption become impossible since access beyond the end (or before the beginning) of any allocated item will be trapped.
9
posted on
01/03/2007 5:20:27 PM PST
by
supercat
(Sony delenda est.)
To: ShadowAce
After reading how this works, my first reaction is to stand back and let other people be the guinea pigs for a good long while before venturing to try it.
I enjoy playing around with betas, but I steer clear of messing with the basic operating system.
10
posted on
01/03/2007 5:20:28 PM PST
by
Cicero
(Marcus Tullius)
To: ShadowAce
"Yippe kai yea, mother ....."
To: Kimmers
Has anyone downloaded this?You first!
To: ShadowAce
The problems Berger wanted to address were caused by the fact that despite the huge amount of memory installed in today's PCs, "programmers are still writing code as if memory is in short supply". Like hell they are. Programmers are writing code and using memory like socialists spend other peoples' money.
13
posted on
01/03/2007 5:22:40 PM PST
by
Centurion2000
(Judges' orders cannot stop determined criminals. Firearms and the WILL to use them can.)
To: ShadowAce
Bookmark to have the wife explain to me later what this means.
14
posted on
01/03/2007 5:25:54 PM PST
by
IrishCatholic
(No local communist or socialist party chapter? Join the Democrats, it's the same thing.)
To: operation clinton cleanup
15
posted on
01/03/2007 5:26:07 PM PST
by
Randy Larsen
(I'd rather be LUCKY than GOOD!)
To: Centurion2000
"Programmers are writing code and using memory like socialists spend other peoples' money."Ain't that the dammed truth!
16
posted on
01/03/2007 5:26:21 PM PST
by
KoRn
To: proxy_user
If we do, they'll probably stick to malloc/free and new/delete. They're too proud that they never make mistakes to use something like this. If a program isn't written right, it should be fixed. While allocation randomization is good for protecting against certain potential security weaknesses, programmers seem to be way too lazy at fixing memory-allocation bugs; allowing such bugs to exist silently doesn't seem like it will improve things. One thing I would think might be useful would be if programs and threads could give the operating system a "justify_memory" callback which would instruct them to notify the OS of all memory they knew about that they owned. Use of such a feature in development would make it possible for programmers to identify memory objects that were left stranded.
17
posted on
01/03/2007 5:26:24 PM PST
by
supercat
(Sony delenda est.)
To: Randy Larsen
I don't use Firefox...Oh well!
18
posted on
01/03/2007 5:28:50 PM PST
by
Randy Larsen
(I'd rather be LUCKY than GOOD!)
To: proxy_user
I wouldn't think we have many C and C++ programmers here.
If we do, they'll probably stick to malloc/free and new/delete. They're too proud that they never make mistakes to use something like this.
I haven't programmed in C++ in years, but memory leaks and heap overruns were a constant problem for every team I ever worked with - we'd have loved something like this though it would have hidden the effects of bad coding. I thought Java was supposed to save us from all that, while taking away our ability to do pointer arithmetic.
Anyway, this sounds like a nice way to prevent many of the buffer overflow exploits out there.
To: supercat
Reducing the likelihood that careless memory accesses will cause damage will also tend to reduce the likelihood of them being found and fixed. Bingo! Let's be enablers of lazy and sloppy coders... NOT!
Navigation: use the links below to view more comments.
first 1-20, 21-38 next last
Disclaimer:
Opinions posted on Free Republic are those of the individual
posters and do not necessarily represent the opinion of Free Republic or its
management. All materials posted herein are protected by copyright law and the
exemption for fair use of copyrighted works.
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson