Too bad your experience with Perl has been with shitty Perl developers. I've seen many large projects complete with Perl, and maintained successfully. YMMV as with any language.
So you should run password crackers on your own system, or configure the sstem to not accept weak passwords. Do both.
And if someone does abuse your SASL/Sendmail configuration, you should have alerts which notify you when someone is sending a large volume of email.
You can use SpamAssassin to filter ooutbound email.
Someone could get on your network illegal and abuse your services.
But it is commercially supported because RedHat developers and company are still behind the project. They aren't giving this to the community -- they retain a lot of control over Fedora. they just don't have to go through retail and support, which cost them a lot of money without a viable revenue stream.
They get jobs writing software for companies that don't sell software as a product. I am a programmer for a financials company. We use open source everywhere and this creates more opportunity for work for people like me who are adept with open source software.
Someone reverse engineer the protocol and create an open source bk clone (gk)! Their license cannot prevent you from doing this. But hurry -- once they add those cryto signatures, your reverse engineering won't be protected under the DMCA.
Slashdot Mirror
Too bad your experience with Perl has been with shitty Perl developers. I've seen many large projects complete with Perl, and maintained successfully. YMMV as with any language.
So you should run password crackers on your own system, or configure the sstem to not accept weak passwords. Do both. And if someone does abuse your SASL/Sendmail configuration, you should have alerts which notify you when someone is sending a large volume of email. You can use SpamAssassin to filter ooutbound email. Someone could get on your network illegal and abuse your services.
So you would prefer the monolithic Catholic Church of Linux?
But it is commercially supported because RedHat developers and company are still behind the project. They aren't giving this to the community -- they retain a lot of control over Fedora. they just don't have to go through retail and support, which cost them a lot of money without a viable revenue stream.
They get jobs writing software for companies that don't sell software as a product. I am a programmer for a financials company. We use open source everywhere and this creates more opportunity for work for people like me who are adept with open source software.
So go buy the RHEL product, which will be around for FIVE years. And you can still install Fedora, Debian, etc
What is your point?
How will it help identity theft? You are now sending all your mail to a third party, and anyone there can make a copy of hundreds of identities.
RedHat 9 released updated OpenSSL rpms. Argh, you are annoying.
Someone reverse engineer the protocol and create an open source bk clone (gk)! Their license cannot prevent you from doing this. But hurry -- once they add those cryto signatures, your reverse engineering won't be protected under the DMCA.
So does that mean if I have a Perl or Python module under the LGPL that is used/imported into a project, the LGPL applies?