Re:The greatest threat...
on
Real Security?
·
· Score: 1
The Krypticon website has been updated. Download the challenge and crack away. Should we be slashdotted, contact mazonn at yahoo dot com for the challenge message to be emailed to you.
The successfully decrypted message contains instructions on how to collect your reward.
Similar open projects include FreePM (I've used it in the past, but can't find links now) OpenEMR and FreeMed
Worth a look so you don't reinvent the wheel... Show that your project adds something significant that the others don't have and it'll help your grant proposal. Ask yourself "What makes mine unique?"
Yeah folks, it sucks, but lets not forget history here. Those who fail to learn from history are doomed to repeat it's mistakes.
It's really too bad, they used to be a decent group of companies (Lineo, et al.). They seemed to change tracks as they were bought, and sold off the embedded side, which was the only side that made measurable revenue.
If you look at SCO's parent company's history, you will find that this is typical behavior for them. Sue for nebulous IP Rights, act shocked, hurt and singled out when you get the predictable mono-digit response.
It's really too bad, because the original group of companies used to be decent (Lineo et al.). It would be more productive to spend their legal budget on R&D and production, but this won't happen. Why?
Those who can, do
Those who can't, sue.
Pray for a judge with a big-ass clue-by-four who isn't afraid to use it.
I guess it all depends what you are after. Four friends and I worked in IT hell for a good number of years, but it took the Y2K crunch to tell me how rare and valuable (read: sucker) we were.
At a meeting over beer, we realized that the company would just replace us if we tipped our hand or played it straight. No benefit to my coworkers or clients, no learning experience to management, no wicked smile in the mirror. So... I planned our departure for a bit.
That UNIX training I was begging them to give to my coworkers? I quit begging. All our production code (non-approved but used anyway) migrated to my home directory... etc. One by one we left. I left last of all of us. "turned out the lights" so to speak. When my D-day came I reminded management of their security responsibilities since I had root on nearly all machines, and I was known to be a card carrying member of se2600 (local hacker community).
Pursuant to a procedure written by the Internal Security Auditor (one of 22 hats I had) he killed all logins and directories I had, including the ones containing scripts used in production.
Results? Late production (to the tune of 3-4 weeks instead of 24 hours) and a loss of 85% of the clients my department served. Most of us went on to work in other simular shops, while I opened my own PC repair biz and doubled my income.
My ass was covered here for a few reasons. 1. I was not a programmer, therefore could not write production code. 2. None of my scripts were in the procedure manual. The hand scrawled notes that explained how to use them was in my bosses hand. 3. The Ops foks were lazy. If there was a simpler way, not only did they use it, they never leared from it, and soon forgot the old way. 4. No documented company property was destroyed.
I will not specify company nor industry, but for those that know: NEO for life, baby!
They can, they have, and they will. The power source is available (provided you can pass the background check). It's called a radioisotope thermoelectric generator or RTG. Links follow, beware of wrap.
Slashdot Mirror
The Krypticon website has been updated. Download the challenge and crack away. Should we be slashdotted, contact mazonn at yahoo dot com for the challenge message to be emailed to you.
The successfully decrypted message contains instructions on how to collect your reward.
Good luck to all.
Dan Harper
Similar open projects include FreePM (I've used it in the past, but can't find links now) OpenEMR and FreeMed
Worth a look so you don't reinvent the wheel... Show that your project adds something significant that the others don't have and it'll help your grant proposal. Ask yourself "What makes mine unique?"
Best of luck.
Yeah folks, it sucks, but lets not forget history here. Those who fail to learn from history are doomed to repeat it's mistakes.
It's really too bad, they used to be a decent group of companies (Lineo, et al.). They seemed to change tracks as they were bought, and sold off the embedded side, which was the only side that made measurable revenue.
If you look at SCO's parent company's history, you will find that this is typical behavior for them. Sue for nebulous IP Rights, act shocked, hurt and singled out when you get the predictable mono-digit response.
It's really too bad, because the original group of companies used to be decent (Lineo et al.). It would be more productive to spend their legal budget on R&D and production, but this won't happen. Why?
Those who can, do
Those who can't, sue.
Pray for a judge with a big-ass clue-by-four who isn't afraid to use it.
I guess it all depends what you are after. Four friends and I worked in IT hell for a good number of years, but it took the Y2K crunch to tell me how rare and valuable (read: sucker) we were.
At a meeting over beer, we realized that the company would just replace us if we tipped our hand or played it straight. No benefit to my coworkers or clients, no learning experience to management, no wicked smile in the mirror. So... I planned our departure for a bit.
That UNIX training I was begging them to give to my coworkers? I quit begging. All our production code (non-approved but used anyway) migrated to my home directory... etc. One by one we left. I left last of all of us. "turned out the lights" so to speak. When my D-day came I reminded management of their security responsibilities since I had root on nearly all machines, and I was known to be a card carrying member of se2600 (local hacker community).
Pursuant to a procedure written by the Internal Security Auditor (one of 22 hats I had) he killed all logins and directories I had, including the ones containing scripts used in production.
Results? Late production (to the tune of 3-4 weeks instead of 24 hours) and a loss of 85% of the clients my department served. Most of us went on to work in other simular shops, while I opened my own PC repair biz and doubled my income.
My ass was covered here for a few reasons.
1. I was not a programmer, therefore could not write production code.
2. None of my scripts were in the procedure manual. The hand scrawled notes that explained how to use them was in my bosses hand.
3. The Ops foks were lazy. If there was a simpler way, not only did they use it, they never leared from it, and soon forgot the old way.
4. No documented company property was destroyed.
I will not specify company nor industry, but for those that know: NEO for life, baby!
They can, they have, and they will. The power source is available (provided you can pass the background check). It's called a radioisotope thermoelectric generator or RTG. Links follow, beware of wrap.
2 32 59.shtml?tid=126
x pl oration.and.Development.of.Space/Human.Space.Fligh t/Shuttle/Shuttle.Missions/Flight.031.STS-34/Galil eos.Power.Supply/RTG.Fact.Sheet
S pa ce%20Batteries.htm
http://nuclear.gov/space/space-desc.html
http://science.slashdot.org/science/02/10/28/17
http://spacelink.nasa.gov/NASA.Projects/Human.E
http://www.snakeriveralliance.org/PhotoGallery/