Base your white-list filter on a system that will only accept PGP signed emails from people who exist in your PGP keyring then regardless of the headers if the signature verification fails then the mail isn't from the valid sender.
First off I like Firefox and its my primary browser of choice. HOWEVER this calling a bug a feature doesn't half remind me of a certain other company I could mention (and several Dilbert cartoons).
If this feature is for my benifit then let me decide whether to use it or not. Apart from that it does not explain why when I leave firefox idle with only one window open on a simple HTML page over time my memory useage goes up...
Stop hiding behind feable excuses and actually work on reducing the footprint firefox uses... FF is suposed to be a lightweight browser alternative to the usual browser bloatware - it is failing at the moment (rather like my spelling;) ).
Yep, at my place our major document repository is... browser based, bugzilla does our bug tracking (albeit on a closed server in our comms room), our test case database is web based, our system model has a web version for read-only use, our expenses and time card system is web based.
As someone who works in the defence industry I'd rather see Linux being used where applicable than a certain Redmond based OS - atleast when an app breaks on linux the rest of the system chugs along, the source code is there so if we have a specific issue we can trace all calls right back to the os kernel calls if needed and fix where needed etc etc etc.
If you said to the 7 astronauts there is a 50/50 chance that this mission could go wrong and and end up killing you I wonder how many of the 7 would have still said yes we'll do it?
I'm prepared to bet given (okay, all bar one - the teacher) these people fully knew the risks of the space programme that all of them would have said yes.
What is the real tradegy with this loss is that is was preventable (for god's sake engineers are paid to know things like spec's etc so if we say no it will not it probably won't) and may well have been a callous exploitation of the shuttle for policatal means.
1) Add a Compact Flash port 2) Enable the CF port to use wireless lan cf cards 3) Ditch 2nd cpu and replace with touch screen 4) Provide some PDA apps (email client, browser, diary, address book, notepad, pdf reader) - I know most of these can probably be ported from their Linux equiv's but would be nice to have out of the box.
Actually given it relies on the hardware implementing the TTL I'd suspect operators would be required to log the messages without applying the TTL.
It only really protects you for messages you've got on your phone when you lose your phone and not messages being intercepted while in transit. If you're worried about people reading messages off your phone I've got an even better idea - delete them once you've read them and then you don't go "whoops - didn't read that in the 40 seconds as someone was talking to me oh dear";)
I think (hope) it refers to an objective for the GPL 3 revamp not an actual clause in the new GPL: IE the changes to GPL should do no harm to existing GPL'd projects.
With all this talk of the new features etc in Office a quick thought...
How many of you use 90% of all the features in Office 97/2000?
Not many I'd guess... Looking at some notes I've got from previous studies into feature use most people only use between 20 and 60% of the feature set in current versions. MS would be better making sure the 60% that people use work well, do not cause any unwanted side effects, and make those the quickest and easiest to access.
I work in a lab environment as well as at desk and so a neck tie isn't just a pain its a hazard - the only time I wear a tie is for presentations to customers.
(Currently sat here in a nice thick wooley jumper as our aircon has decided after a summer off to start working and the heating has decided after working all summer to take the winter off... grrr. )
What makes me laugh with these electromagnetic therapies that keep poping up is that most of them use fields way in excess in terms of strength than you'll get from powerlines running through your estate but those fields are bad... the same field strapped to you is good??? DOH!
Trouble is performance wise and interface wise its my favourite browser... so while its not the leanest its still going to be my first choice (Opera second and IE only for MS specific needs (outlook webaccess, windows update etc)).
If I write a book and put a comma in the wrong place or a maths article and put a + instead of - I'm not going to get sued. So why should I get sued if I by mistake in my code... On the other hand though:
If I deliberately release software with a design flaw which I or others can exploit ANd you can prove I knew about the flaw prior to release and chose to do nothing then there might be case to answer. (Anyone fancy trying that one against the practices of a certain large purveyour of office applications and operating systems;) )
I'll stick with apt-get from the command line... does exactly what I want - which is install packages, resolve dependency problems with no fuss and no frilly bits which do damn all other than eat resources.
(Assuming the package is available from one of the apt sources you've got no problems - when it isn't I agree it gets more interesting;) ).
That might make life interesting for Google (and probably Yahoo) as I'd bet a large chunk of googles operations are based on FOSS code including their clustering software, mail etc.
While I can see the point of making distributors in the conventional sense having to release the source I've a nasty feeling making web service companies reveal their source might only harm the OSS movement in the longer term... Google might be Okay as they've got the bandwidth to be able to release the source code for all OSS code used internally but not sure about the smaller providers...
/. proves once more its sliding down the relevance scale:(
Anyway:
Firefox: Compartively new browser and gaining wider and wider useage. Hence an initial low number of holes which is now ramping up as people use it more and it gets on to hackers radar. IE: Rather long in the tooth and has been around for a while as the most popular browser. Almost continual flurry of holes for the last few years which is now slowing down as all the easy (and most of the not so easy) holes are found.
Any product will have a bell curve distribution of holes...
It would be more relevant to compare the number of holes discovered since release. OR even better track the faults as a metric based on the lines of code affected vs the total lines of code contained in the product. Might be awkward with IE given its dependencies on other M$ dll's etc... but would alot fairer.
Slashdot Mirror
Base your white-list filter on a system that will only accept PGP signed emails from people who exist in your PGP keyring then regardless of the headers if the signature verification fails then the mail isn't from the valid sender.
First off I like Firefox and its my primary browser of choice. HOWEVER this calling a bug a feature doesn't half remind me of a certain other company I could mention (and several Dilbert cartoons).
;) ).
If this feature is for my benifit then let me decide whether to use it or not. Apart from that it does not explain why when I leave firefox idle with only one window open on a simple HTML page over time my memory useage goes up...
Stop hiding behind feable excuses and actually work on reducing the footprint firefox uses... FF is suposed to be a lightweight browser alternative to the usual browser bloatware - it is failing at the moment (rather like my spelling
Please remain seated. Do not panic. Help will arrive shortly - please cooperate with the men in white coats.
You will be taken to a place of healing.
Thank you for your cooperation.
Yep, at my place our major document repository is... browser based, bugzilla does our bug tracking (albeit on a closed server in our comms room), our test case database is web based, our system model has a web version for read-only use, our expenses and time card system is web based.
Just turn your computer room into Faraday Cage, make sure you've got a good earth and do what you like knowing all emissions will be earth spiked...
Do you want an honest answer to that?
If so then neither...
a WMD needs a reliable, robust, hard-real time OS not an OS more designed for a desktop or server.
VX Works etc are still widely used in the RTOS domain and yes linux is making steady ground but I'm not 100% convinced by its realtime capabilities.
As someone who works in the defence industry I'd rather see Linux being used where applicable than a certain Redmond based OS - atleast when an app breaks on linux the rest of the system chugs along, the source code is there so if we have a specific issue we can trace all calls right back to the os kernel calls if needed and fix where needed etc etc etc.
Apart from that what's cute got to do with Linux?
If you said to the 7 astronauts there is a 50/50 chance that this mission could go wrong and and end up killing you I wonder how many of the 7 would have still said yes we'll do it?
I'm prepared to bet given (okay, all bar one - the teacher) these people fully knew the risks of the space programme that all of them would have said yes.
What is the real tradegy with this loss is that is was preventable (for god's sake engineers are paid to know things like spec's etc so if we say no it will not it probably won't) and may well have been a callous exploitation of the shuttle for policatal means.
Mention flasing your bios to the average home user and you'll get typically one of two responses:
:)
One an offer of much more interesting time than you planned for, or more likely,
a threat of arrest for obscene behaviour
I dunno know, a cubic foot of any metal is going to seem pretty huge when it lands on your head.
If it is C++09 should we read it as (C++)09 or C(++09) (in case of the later why not just C10?)
1) Add a Compact Flash port
2) Enable the CF port to use wireless lan cf cards
3) Ditch 2nd cpu and replace with touch screen
4) Provide some PDA apps (email client, browser, diary, address book, notepad, pdf reader) - I know most of these can probably be ported from their Linux equiv's but would be nice to have out of the box.
Actually given it relies on the hardware implementing the TTL I'd suspect operators would be required to log the messages without applying the TTL.
;)
It only really protects you for messages you've got on your phone when you lose your phone and not messages being intercepted while in transit. If you're worried about people reading messages off your phone I've got an even better idea - delete them once you've read them and then you don't go "whoops - didn't read that in the 40 seconds as someone was talking to me oh dear"
I think (hope) it refers to an objective for the GPL 3 revamp not an actual clause in the new GPL: IE the changes to GPL should do no harm to existing GPL'd projects.
With all this talk of the new features etc in Office a quick thought...
How many of you use 90% of all the features in Office 97/2000?
Not many I'd guess... Looking at some notes I've got from previous studies into feature use most people only use between 20 and 60% of the feature set in current versions. MS would be better making sure the 60% that people use work well, do not cause any unwanted side effects, and make those the quickest and easiest to access.
Better hope that is a typo as I'd have thought HDTV quality media would require a throughput greater than 27MB/Sec....
Well said.
I work in a lab environment as well as at desk and so a neck tie isn't just a pain its a hazard - the only time I wear a tie is for presentations to customers.
(Currently sat here in a nice thick wooley jumper as our aircon has decided after a summer off to start working and the heating has decided after working all summer to take the winter off... grrr. )
What makes me laugh with these electromagnetic therapies that keep poping up is that most of them use fields way in excess in terms of strength than you'll get from powerlines running through your estate but those fields are bad... the same field strapped to you is good??? DOH!
Trouble is performance wise and interface wise its my favourite browser... so while its not the leanest its still going to be my first choice (Opera second and IE only for MS specific needs (outlook webaccess, windows update etc)).
That's the one thing I don't like about FF - I've got FF running now with two tabs - one on Slashdot and one viewing my websites stat's on sitemeter.
... 28 MB for two instances viewing the same pages as in FF.
Memory useage: 49MB...
Just fired up IE
If I write a book and put a comma in the wrong place or a maths article and put a + instead of - I'm not going to get sued. So why should I get sued if I by mistake in my code... ;) )
On the other hand though:
If I deliberately release software with a design flaw which I or others can exploit ANd you can prove I knew about the flaw prior to release and chose to do nothing then there might be case to answer. (Anyone fancy trying that one against the practices of a certain large purveyour of office applications and operating systems
Not impossible but shooting the right rocket down might just tax some of the more trigger happy brains ;)
I'll stick with apt-get from the command line... does exactly what I want - which is install packages, resolve dependency problems with no fuss and no frilly bits which do damn all other than eat resources.
;) ).
(Assuming the package is available from one of the apt sources you've got no problems - when it isn't I agree it gets more interesting
That might make life interesting for Google (and probably Yahoo) as I'd bet a large chunk of googles operations are based on FOSS code including their clustering software, mail etc.
While I can see the point of making distributors in the conventional sense having to release the source I've a nasty feeling making web service companies reveal their source might only harm the OSS movement in the longer term... Google might be Okay as they've got the bandwidth to be able to release the source code for all OSS code used internally but not sure about the smaller providers...
/. proves once more its sliding down the relevance scale :(
Anyway:
Firefox: Compartively new browser and gaining wider and wider useage. Hence an initial low number of holes which is now ramping up as people use it more and it gets on to hackers radar.
IE: Rather long in the tooth and has been around for a while as the most popular browser. Almost continual flurry of holes for the last few years which is now slowing down as all the easy (and most of the not so easy) holes are found.
Any product will have a bell curve distribution of holes...
It would be more relevant to compare the number of holes discovered since release. OR even better track the faults as a metric based on the lines of code affected vs the total lines of code contained in the product. Might be awkward with IE given its dependencies on other M$ dll's etc... but would alot fairer.