-
-
While we're still on the subject of computers....
Last Saturday night I was trying to book air tickets on the Emirates website. However, the website kept crashing every time I tried to select my flight.
So I tried again on Sunday morning. This time I managed to get my tickets.
In a sense I was lucky the website kept crashing on Saturday night. They were charging $200 more on Saturday night than on Sunday morning.
So I saved quite a bit of dosh by booking my tickets on Sunday morning.
Edited by fudgester 27 Feb `12, 2:48PM
-
-
-
Originally posted by ^Acid^ aka s|aO^eH~:
no >___> I'm not saying u did... I'm just saying u shld know abt logic bombs >___>@fudgey: yeah... it's a crime to use logic bombs...
Fudgy and Acid.
This occured to me when I was at work some time back.
The DB table has a trigger to delete a particular record when an update or insert transaction action took place. The deleting was from a table that kept temp records. Useless until needed as audit or lookup. Otherwise considered as space wasting. As it was done in a hurry, no documentation or any form of agreement was taken down.
The guys who were in the project left. Some time later, new administrators and analyst took over and saw the delete trigger. as They could not understand the logic behind it, they dubbed it as "a malicious attempt to destablise a system thru means consider as blah blah blah".
So a lawsuit followed. Can't remember the outcome.
Will you consider this case as something to fight about?
-
Anyway I find it silly to plant logic bombs
Too easily detected.
I would want stuff that does not leave any trace or trail after execution. :D
-
-
-
Originally posted by shrekho:
Fudgy and Acid.
This occured to me when I was at work some time back.
The DB table has a trigger to delete a particular record when an update or insert transaction action took place. The deleting was from a table that kept temp records. Useless until needed as audit or lookup. Otherwise considered as space wasting. As it was done in a hurry, no documentation or any form of agreement was taken down.
The guys who were in the project left. Some time later, new administrators and analyst took over and saw the delete trigger. as They could not understand the logic behind it, they dubbed it as "a malicious attempt to destablise a system thru means consider as blah blah blah".
So a lawsuit followed. Can't remember the outcome.
Will you consider this case as something to fight about?
Well, I'm no lawyer to comment on this -___-
-
-
-
Originally posted by shrekho:
Fudgy and Acid.
This occured to me when I was at work some time back.
The DB table has a trigger to delete a particular record when an update or insert transaction action took place. The deleting was from a table that kept temp records. Useless until needed as audit or lookup. Otherwise considered as space wasting. As it was done in a hurry, no documentation or any form of agreement was taken down.
The guys who were in the project left. Some time later, new administrators and analyst took over and saw the delete trigger. as They could not understand the logic behind it, they dubbed it as "a malicious attempt to destablise a system thru means consider as blah blah blah".
So a lawsuit followed. Can't remember the outcome.
Will you consider this case as something to fight about?
That is more of a case of an administrative SNAFU than a true logic bomb planted out of malice....
It goes to show the need for proper documentation when it comes to things like this.
-
