There was oh, Perl. And this little thing called IP. And a few other protocols, like, say, SMTP and HTTP. COM is merely the Windows version of RPC. cfengine, Puppet, config, BCFG2...
What you see referred to often is because "enterprises" want the fancy software (and need it in some cases).
It's called configuration management. The old standard was cfengine (this is basically the Sendmail of configuration management systems), there are quite a few newer alternatives out there with different strengths and weaknesses.
Thin clients make life easier, but that's a business call.
http://homepages.inf.ed.ac.uk/group/lssconf/ is a good place to start off with. You do need at least one guru level person, but not too many of those, somewhat similar to having good Windows admin skills.
There are no pretty frontends yet, but it shouldn't be too hard to write one of those.
I don't know. I'd rather have my data fail closed than be stolen or otherwise abused. A resilient mail system (to bring it back to SPAM) would just be able to send/receive that much more spam.
A resilient system would not collapse under the load of spam.
Without all data objects having self-contained security attributes which require legitimate participating systems for access and a real semantic security policy taking advantage of those attributes, pretty much any data on the network can be intercepted, altered, or denied somehow.
And you can never trust security attributes coming from the client. In essence, what it boils down to is that you build a trusted system, and only allow trusted users access (like a telephone network, where the only groups till recently who could do things like setting caller ID were telcos).
What we need is resilient systems, which can be attacked, but not collapse under load.
How do you deal with identity theft (including zombies)? This has been asked before in the context of micro-payments and hash-cash and other such ideas as well.
There is a difference between "I signed it" and "The computer signed it". One can't be hijacked easily, the other can.
Plus, you have to send the identifier during the SMTP part of the transaction, not in the headers (otherwise, the bandwidth transfer rise itself can kill smaller sites).
Javascript is in essence, the equivalent of closed source. You can read the code, but there is no guarantee that it is the same code the next time you go to that page.
With TLS, you are guaranteed to get the authentic exploit.
Slashdot Mirror
No, it is free as in speech. Free beer is optional.
There was oh, Perl. And this little thing called IP. And a few other protocols, like, say, SMTP and HTTP. COM is merely the Windows version of RPC. cfengine, Puppet, config, BCFG2 ...
What you see referred to often is because "enterprises" want the fancy software (and need it in some cases).
Cthulhu comes!
And if the closed source product is better at that task, we're fine with paying for it.
And do you pay for the FOSS products?
Unless of course, the controllers are using relays of zombie PCs distributed globally.
Ignorance is strength.
Try asking here http://www.thedailywtf.com/
Return your geek cred as you leave.
5 935
Forty-two is the answer to "What is six multiplied by nine?"
http://answers.google.com/answers/threadview?id=3
The terrorists already have high resolution maps. It's the citizens the government officials are afraid of.
Actually, attacking government offices/infrastructure in India won't do much good. There are better targets.
http://www.discountlaptops.com/ sells laptops without operating systems.
Or Slashdot's posting departments.
It's called configuration management. The old standard was cfengine (this is basically the Sendmail of configuration management systems), there are quite a few newer alternatives out there with different strengths and weaknesses.
Thin clients make life easier, but that's a business call.
http://homepages.inf.ed.ac.uk/group/lssconf/ is a good place to start off with. You do need at least one guru level person, but not too many of those, somewhat similar to having good Windows admin skills.
There are no pretty frontends yet, but it shouldn't be too hard to write one of those.
Errr, having staging and build servers does not remove the need for testing upgrades. On any OS.
The trick is to build your own packages on one host. Set that one up as a centralised distribution server. Then everything just pulls from it.
Hmmm, sounds like my employer, except that we have a ton more outbound. Is your employer part of MAAWG yet?
Bill them for the call. Add that clause into your ToS.
Email has never been about "immediate, guaranteed delivery". Email can and will be delayed.
If you want immediate, use IM or make a phone call.
I wish. My systems tend to collapse more than I do, from the sheer volume of crap.
BTW, are you the same jofny as on Freenode? (If yes, lets discuss this in #security or #postfix after the 25th, when I get back to my home system).
Unix MTAs log to syslog. Syslog is perfectly capable of sending stuff over the network.
Grab a PC, setup a syslog server on it listening to the network, tell your MTAs to log there in addition to local logging.
I don't know. I'd rather have my data fail closed than be stolen or otherwise abused. A resilient mail system (to bring it back to SPAM) would just be able to send/receive that much more spam.
A resilient system would not collapse under the load of spam.
Opem Source isn't a gang-bang, it's an orgy.
Without all data objects having self-contained security attributes which require legitimate participating systems for access and a real semantic security policy taking advantage of those attributes, pretty much any data on the network can be intercepted, altered, or denied somehow.
And you can never trust security attributes coming from the client. In essence, what it boils down to is that you build a trusted system, and only allow trusted users access (like a telephone network, where the only groups till recently who could do things like setting caller ID were telcos).
What we need is resilient systems, which can be attacked, but not collapse under load.
My swimming pool is the Pacific ocean, you insensitive clod.
How do you deal with identity theft (including zombies)? This has been asked before in the context of micro-payments and hash-cash and other such ideas as well.
There is a difference between "I signed it" and "The computer signed it". One can't be hijacked easily, the other can.
Plus, you have to send the identifier during the SMTP part of the transaction, not in the headers (otherwise, the bandwidth transfer rise itself can kill smaller sites).
Wrong. TLS secures data transfer, not the code.
Javascript is in essence, the equivalent of closed source. You can read the code, but there is no guarantee that it is the same code the next time you go to that page.
With TLS, you are guaranteed to get the authentic exploit.