As a continuation of the parent (which I forgot to type before I submitted)...
As a developer working under Windows, I do what I can to make sure my software is stable on that platform. I'll take logs from customers and, if I can identify something in my own code or something called from it that I can fix, then I'll fix it. If I can't, then, knowing the facts about the platform, I don't lose sleep at night.
Oh, a correction to the comment about Windows in the parent... that's only true if the processes are running under the same user.
An example of how some crashes can be hard to prove:
Since most recent versions of Windows allow any process to write in the memory space of any other process, it's hard to prove that a crash of one process is or is not the result of another misbehaving process corrupting it.
I'll stand behind my code, sure... that doesn't mean I can stand behind the code that it depends on.
a) the application of science and mathematics by which the properties of matter and the sources of energy in nature are made useful to people b) the design and manufacture of complex products <software engineering>
According to that, programmers are engineers. That's especially true for those programmers that do design as well (like myself).
It isn't like it's that hard to write Windows software that works from a certain version forward (going by the versions of certain APIs that may or may not be used). Most things can be made to work on 98 on up, while some things require stuff specific to NT (which still applies for 2000 and XP). That is, if things are done correctly.
Each version of Windows does bring in certain quirks that tend to screw with this compatibility, but they're small for the most part. This is probably what needs to be addressed with the problems that make people say that software doesn't work for them. That or laziness on the part of the developers (probably more common).
Of course, anything dealing with things on a system level can't follow that logic (drivers, etc.).
Hotmail subscribers are now limited to sending only 100 messages a day "in an effort to prevent spammers from using Hotmail to spread spam,"
They don't need to use hotmail itself (in fact, I've never seen a spammer that has). They just need to spoof Hotmail addresses, which is quite easy. Chalk that up as yet another episode of M$ letting itself sound stupid...
Exactly. The only thing I've seen before that it seems like this might affect is the search keyword bidding that Tucows makes available to developers. Not that I've ever used that anyway with my software listings, so I'm not sweating:-)
All software, papers, and other works of information are being licensed for use as laid out in the terms of this agreement and remain the property and copyright of Psionic except where noted otherwise. These works may not to be used in part or in whole of a commercial product offering without express written consent from Psionic. Permission is granted to modify source code for personal use only. DISTRIBUTION OF MODIFIED SOURCE CODE WITHOUT PSIONIC'S PERMISSION IS PROHIBITED.
Distribution
All distributed software, papers, and other works are free to use by any individual, organization, or commercial venture as long as the above conditions are agreed to. This software may be included with any freely distributed Operating System provided it is not sold separately or as part of a "security bundle" or similar packaging. Outside of the exceptions noted above, this software may not be re-sold without permission from Psionic.
IANAL, but it looks like you can, as long as you're not charging and you haven't modified it. It does say that it's "free to use", but only explicity grants distribution rights if it's part of a free OS. I haven't checked the license for Logcheck yet, but I'd imagine it's the same or very similar.
Facts are meaningless, you can use facts to prove anything that's remotely true! Facts, schmacks.
Indeed...
Theory: File sharing supports terrorism
Proof: File sharing allows a try-before-you-buy system A certain percentage of file traders buy CDs because they like the music they sampled RIAA gets a substantial fraction of the CD's price RIAA is a (legal) terrorist
Wouldn't surprise me. They recently bought Psionic as well and, as far as I can tell, handy tools like PortSentry and Logcheck are nowhere to be found anymore. Instead, PortSentry at least has been assimilated into overpriced Cisco products.
At least I still have the copies that I downloaded several months ago...
...whether the prices will change much at all "in the near term", since Linksys will still be using their own brand name, or if the prices will indeed skyrocket like everything else Cisco sells.
According to this article, nothing needs to be done to the satellites at all. Jammers can be deployed to scramble civilian GPS signals over a localized area.
After all, when's the last time you've seen a GPS receiver with a dish antenna? Ground-based signals can logically affect them just as easily as sky-based.
Re:If you can't beat them accept the threat model?
on
DRM and Threat Analysis
·
· Score: 3, Funny
No wait, I could just log on to the artist's homepage and pay the $.50 directly to him/her/them!!!
At least they'd be getting twice what they are now, so why not?
The number of BugTraq posts for holes in PHP itself doesn't begin to equal the number in applications that are built on it. That just goes back to my earlier statement.
One could rewrite PHP web applications in a number of other languages, and they'd still have just as many chances of containing security holes.
You would still need different parsing code for each file. Sure, the general XML portion of the syntax would be the same, but you would still need an understanding of the expected data that would be different in every case.
If there's one good thing about XML in those cases, it's expandability. Suppose you wanted to add an XYZ field in the middle of a password file record. With the current format, that would be quite difficult. With XML, you'd just define a new element (optional or required) that could then be inserted and not throw off parsing of any other part of the file.
It would still be a nightmare to maintain, though, unless you made heavy use of management utilities.
Easy to do... make it text-based :-)
If you need to be more bandwidth-friendly than that, compress it!
Ah yes... the typical /. article problem/solution race condition :-)
You've never done a screen capture in Windows without downloading software to do it, have you?
If only we could RTFA... can't get past the first page of it, myself, and there are apparently 8 in there somewhere.
Now all we need is reading a book (reverse engineering words back into thought) as a test for the DMCA, and they'll be on equal footing.
As a continuation of the parent (which I forgot to type before I submitted)...
As a developer working under Windows, I do what I can to make sure my software is stable on that platform. I'll take logs from customers and, if I can identify something in my own code or something called from it that I can fix, then I'll fix it. If I can't, then, knowing the facts about the platform, I don't lose sleep at night.
Oh, a correction to the comment about Windows in the parent... that's only true if the processes are running under the same user.
An example of how some crashes can be hard to prove:
Since most recent versions of Windows allow any process to write in the memory space of any other process, it's hard to prove that a crash of one process is or is not the result of another misbehaving process corrupting it.
I'll stand behind my code, sure... that doesn't mean I can stand behind the code that it depends on.
I've always said that software development was a black art... :-)
It isn't like it's that hard to write Windows software that works from a certain version forward (going by the versions of certain APIs that may or may not be used). Most things can be made to work on 98 on up, while some things require stuff specific to NT (which still applies for 2000 and XP). That is, if things are done correctly.
Each version of Windows does bring in certain quirks that tend to screw with this compatibility, but they're small for the most part. This is probably what needs to be addressed with the problems that make people say that software doesn't work for them. That or laziness on the part of the developers (probably more common).
Of course, anything dealing with things on a system level can't follow that logic (drivers, etc.).
Slip of the keyboard...
"Designed for replacing Windows XP".
Hotmail subscribers are now limited to sending only 100 messages a day "in an effort to prevent spammers from using Hotmail to spread spam,"
They don't need to use hotmail itself (in fact, I've never seen a spammer that has). They just need to spoof Hotmail addresses, which is quite easy. Chalk that up as yet another episode of M$ letting itself sound stupid...
I'm sorry... had to re-read that one. At first glance, looked like "...until Microsoft breaks it."
Agreed, despite the best efforts of software crackers to try and kill it.
Exactly. The only thing I've seen before that it seems like this might affect is the search keyword bidding that Tucows makes available to developers. Not that I've ever used that anyway with my software listings, so I'm not sweating :-)
As an update to the parent, Logcheck 1.1.1 is licensed under the GPL.
IANAL, but it looks like you can, as long as you're not charging and you haven't modified it. It does say that it's "free to use", but only explicity grants distribution rights if it's part of a free OS. I haven't checked the license for Logcheck yet, but I'd imagine it's the same or very similar.
Facts are meaningless, you can use facts to prove anything that's remotely true! Facts, schmacks.
Indeed...
Theory:
File sharing supports terrorism
Proof:
File sharing allows a try-before-you-buy system
A certain percentage of file traders buy CDs because they like the music they sampled
RIAA gets a substantial fraction of the CD's price
RIAA is a (legal) terrorist
Makes sense to me!
Wouldn't surprise me. They recently bought Psionic as well and, as far as I can tell, handy tools like PortSentry and Logcheck are nowhere to be found anymore. Instead, PortSentry at least has been assimilated into overpriced Cisco products.
At least I still have the copies that I downloaded several months ago...
...whether the prices will change much at all "in the near term", since Linksys will still be using their own brand name, or if the prices will indeed skyrocket like everything else Cisco sells.
According to this article, nothing needs to be done to the satellites at all. Jammers can be deployed to scramble civilian GPS signals over a localized area.
After all, when's the last time you've seen a GPS receiver with a dish antenna? Ground-based signals can logically affect them just as easily as sky-based.
No wait, I could just log on to the artist's homepage and pay the $.50 directly to him/her/them!!!
At least they'd be getting twice what they are now, so why not?
The number of BugTraq posts for holes in PHP itself doesn't begin to equal the number in applications that are built on it. That just goes back to my earlier statement.
One could rewrite PHP web applications in a number of other languages, and they'd still have just as many chances of containing security holes.
For PHP, add to that: resource hungry...
...and many of the apps written with it are notoriously insecure.
It's a web scripting language... what'd you expect?
That's not exactly the fault of the language, now is it? Sounds more like a problem with the people using it.
You would still need different parsing code for each file. Sure, the general XML portion of the syntax would be the same, but you would still need an understanding of the expected data that would be different in every case.
If there's one good thing about XML in those cases, it's expandability. Suppose you wanted to add an XYZ field in the middle of a password file record. With the current format, that would be quite difficult. With XML, you'd just define a new element (optional or required) that could then be inserted and not throw off parsing of any other part of the file.
It would still be a nightmare to maintain, though, unless you made heavy use of management utilities.