Re: Database wiped clean

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61171
interpreted = N
texte = >I have read the talk list about incidents where "chunks" of data in the >database was lost. We have experienced multiple occasions on different DB's >where the entire database gets wiped clean. The .db file is still there, but >it is totally blank. Has anyone else experienced this, and if so did you >find the cause? Does anyone have any guesses as to what may be causing this? Once I had a client who insisted that I deliver my results immediately -- even though he had not paid me yet -- so he could get funding for his business by showing my work to his investors. I trusted him so I sent him my results, but then he tried to cheat me by refusing to pay. Fortunately I anticipated his dishonesty and I built in some code that would erase all the values in the db if I ever activated it by sending a unique "name=value" pair to a specific page on his site. This code also erased all the templates and include files on his site, thus leaving him with a bunch of files that were totally blank. It was amazing how fast he paid me after I activated that code. The point I'm trying to make here is that someone who is writing webdna that's being used on your server could have written code that would do this, thus leaving your db file completely blank. The same person could follow this up with code that erases the code that deleted the db data, thus 'covering his tracks' so to speak. This is probably not what's gong on in your case, but anyone who doesn't use individual sandboxes to isolate one person's webdna code from another is 'at risk' for this kind of threat. -- Sincerely, Kenneth Grome www.kengrome.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Database wiped clean ( "Nitai @ ComputerOil" 2005)
  2. Re: Database wiped clean ( David Cate 2005)
  3. Re: Database wiped clean ( Kenneth Grome 2005)
  4. Re: Database wiped clean ( John Hill 2005)
  5. Re: Database wiped clean ( Kenneth Grome 2005)
  6. Re: Database wiped clean ( John Hill 2005)
  7. Re: Database wiped clean ( Donovan Brooke 2005)
  8. Re: Database wiped clean ( Donovan Brooke 2005)
  9. Re: Database wiped clean ( Marc Thompson 2005)
  10. Re: Database wiped clean ( David Cate 2005)
  11. Re: Database wiped clean ( Phil Herring 2005)
  12. Re: Database wiped clean ( Donovan Brooke 2005)
  13. Database wiped clean ( "Eric Miller" 2005)
>I have read the Talk List about incidents where "chunks" of data in the >database was lost. We have experienced multiple occasions on different DB's >where the entire database gets wiped clean. The .db file is still there, but >it is totally blank. Has anyone else experienced this, and if so did you >find the cause? Does anyone have any guesses as to what may be causing this? Once I had a client who insisted that I deliver my results immediately -- even though he had not paid me yet -- so he could get funding for his business by showing my work to his investors. I trusted him so I sent him my results, but then he tried to cheat me by refusing to pay. Fortunately I anticipated his dishonesty and I built in some code that would erase all the values in the db if I ever activated it by sending a unique "name=value" pair to a specific page on his site. This code also erased all the templates and include files on his site, thus leaving him with a bunch of files that were totally blank. It was amazing how fast he paid me after I activated that code. The point I'm trying to make here is that someone who is writing webdna that's being used on your server could have written code that would do this, thus leaving your db file completely blank. The same person could follow this up with code that erases the code that deleted the db data, thus 'covering his tracks' so to speak. This is probably not what's gong on in your case, but anyone who doesn't use individual sandboxes to isolate one person's webdna code from another is 'at risk' for this kind of threat. -- Sincerely, Kenneth Grome www.kengrome.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] An unknown error occured // Deadlock avoided (2011) and vs or vs not (1998) Bug in loop context ... (2000) Protect and Serve (1999) WCf2 and nested tags (1997) WC2b12: Yes, Formulas.db is for real (1997) Search results templates (1996) RED QUESTION MARK (1999) Unable to open the demo file (1998) Searching/sorting dates (1997) Formatting dates stored in db (2003) [WebDNA] FCKeditor (2009) [OT] DNS Problems (2004) Freeze (2003) Digest for 4/18/97 (1997) Single Link browsing (1997) Emailer pref's won't save (2005) Um...how do I ask this? (1999) problems with 2 tags (1997) generator prob (2001)