Re: Armory crashing firefox consistently now
- From: hume.spamfilter@xxxxxxx
- Date: Wed, 30 Jan 2008 11:16:21 +0000 (UTC)
Pla <pla@xxxxxx> wrote:
No it doesn't. No software can be made to be %100 secure, it's
impossible. You don't even know where the problem resides.
So you don't even try?
Do you know what an asymptote is? That's the curve that measures software
quality versus expended effort debugging it. Sometimes called the 90/10
rule, where "The last ten percent of a project requires ninety percent of
the effort". Software debugging is the same way. Sure, 100% reliability
and security may not be possible. But you don't let flaws pass ignored.
That's called laziness and negligence.
You're ("you are") wasting ridiculous amounts of effort defending your
softwares' right to be crap. And the authors of said software wouldn't
even agree with you!
Go ahead, try to repeat what you've said here to someone like Linus or
Theo de Raat. Just tell me where to find the posts, because that thread
would be short and very hilarious. Especially in Theo's case.
One can very easily do things in java for instance that will cause
functionality problems, that's not the fault of java, hell I could do
that in any language, once you exicute it problems can start. Improper
Java the language or Java the JVM?
If you can exploit and attack the sandbox model in a JVM, then publish the
exploit code to Bugtraq. Sun and the other JVM vendors will jump on it
like nobody's business... just like they have, in the past.
But that's not really relevant, because the source language is irrelevant.
If you can write bad code and run it yourself, then you've *become a software
publisher*, and you are responsible for the bugs in YOUR code! The difference
between you and someone who knows what they're doing is that *they* usually
want to fix the bugs, and will value bug reports.
If you're doing something as idiotic as a forkbomb, or malloc-ing all
available memory, the vendor will close the bug and refer you to the
existing resource controls built into the OS. Or, in the case of a JVM,
the max memory/heap command flags.
Did you have any other point besides saying, "Look, I can write bad
software, and I don't care?"
Besides the issue with the armory causes a temporary lock up of the
browser -- it is not 'causing an all out crash.
Then that's a starvation of resources issue, or a bad algorithm. Regardless,
you can still file a bug report on it. The only difference is the main tool
will be a profiler rather than a debugger.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
.
- Follow-Ups:
- Re: Armory crashing firefox consistently now
- From: hume . spamfilter
- Re: Armory crashing firefox consistently now
- References:
- Armory crashing firefox consistently now
- From: Mark (newsgroups)
- Re: Armory crashing firefox consistently now
- From: hume . spamfilter
- Re: Armory crashing firefox consistently now
- From: Smid
- Re: Armory crashing firefox consistently now
- From: hume . spamfilter
- Re: Armory crashing firefox consistently now
- From: Pla
- Armory crashing firefox consistently now
- Prev by Date: Re: What is the cap on CRIT
- Next by Date: Re: I didn't complain, but someone did
- Previous by thread: Re: Armory crashing firefox consistently now
- Next by thread: Re: Armory crashing firefox consistently now
- Index(es):
Relevant Pages
|