For starters, let me tell you about my life. I hate my job. I really do. But I live in a town where there is nowhere else to work.
I have come to learn something in my life...
Ignore your job. Remember, it is just a means to an end. My manager makes stupid decisions. My co-workers are all stupid and spend hours each day congratulating themselves on a job "well done".
The secret is to care just enough to keep your job and do it well. Forget about all of the other crap.
You work to feed your family and your children. Your company will never thank you for all of the hard work you put in. They will never recognize you for your talents.
Just do your job... and go home to what realy counts....
The authentication needs to be done using GPG (GNU Privacy Guard) or PGP (Pretty
Good Privacy). This will prevent anyone in the future from inappropriately
placing code in the kernel.
These two programs provide an excellent means of determining the authenticity of
the author.
Moreover, the origins of all code submissions can easily be tracked and
catalogued using some open source software some friend of mine and I have been
working on.
In a nutshell it works like this:
Code is received either by FTP, E-mail or (virtually) any other mans. At the
end of the encrypted code, the code is signed and encrypted with the writer's
key.
Each of these keys is kept in a database that contains verified information
about the writer. This can include their name, and address, or whatever is
appropriate.
This database is kept as a public record of which code belongs to whom, and when
it was created (or submitted).
Think about it... anybody who wants to submit code should not be able to do so
anonymously. This stands to reason in light of what has been going on lately
with SCO. Moreover, this method looks good to executives who have no idea how
software is developed and is a legitimate method of proof.
So far as being on the Internet, this project is not right now, some friends of
mine and I at the University have been beta testing it and it works wonderfully
and is very secure.
Thank you for your interest!!!!
Any thoughts?
Slashdot Mirror
Well, I guess I'm not supprised. Does anybody else smell a Rat? After all, Micro$oft would love to sue OpenOffice and Open Document to the ground!!!!
By reading the Article I was surprised by their argument. Not only is it flimsy, it just doesn't add up.
a ns_for_Technology_Leadership
Now I know why....
http://www.sourcewatch.org/index.php?title=Americ
We need to get in contact with Fox News and see that this stops here.
foxnewsonline@foxnews.com
For starters, let me tell you about my life. I hate my job. I really do. But I live in a town where there is nowhere else to work.
I have come to learn something in my life...
Ignore your job. Remember, it is just a means to an end. My manager makes stupid decisions. My co-workers are all stupid and spend hours each day congratulating themselves on a job "well done".
The secret is to care just enough to keep your job and do it well. Forget about all of the other crap.
You work to feed your family and your children. Your company will never thank you for all of the hard work you put in. They will never recognize you for your talents.
Just do your job... and go home to what realy counts....
Your family.
And Half-Life 2...
YEAH, BABY, YEAH!!!!!!!
The authentication needs to be done using GPG (GNU Privacy Guard) or PGP (Pretty Good Privacy). This will prevent anyone in the future from inappropriately placing code in the kernel. These two programs provide an excellent means of determining the authenticity of the author. Moreover, the origins of all code submissions can easily be tracked and catalogued using some open source software some friend of mine and I have been working on. In a nutshell it works like this: Code is received either by FTP, E-mail or (virtually) any other mans. At the end of the encrypted code, the code is signed and encrypted with the writer's key. Each of these keys is kept in a database that contains verified information about the writer. This can include their name, and address, or whatever is appropriate. This database is kept as a public record of which code belongs to whom, and when it was created (or submitted). Think about it... anybody who wants to submit code should not be able to do so anonymously. This stands to reason in light of what has been going on lately with SCO. Moreover, this method looks good to executives who have no idea how software is developed and is a legitimate method of proof. So far as being on the Internet, this project is not right now, some friends of mine and I at the University have been beta testing it and it works wonderfully and is very secure. Thank you for your interest!!!! Any thoughts?