FiveTech Support Forums

FiveWin / Harbour / xBase community
Board index FiveWin for Harbour/xHarbour Cryptowall or similar
Posts: 1091
Joined: Thu Nov 17, 2005 11:08 AM
Cryptowall or similar
Posted: Tue Aug 25, 2015 05:19 PM

Hi to all,
So many our customer are victims of cryptowall or similar virus that
crypts many many files in so few minutes.
This time also dbf tables.
The tables "in use" are non affected by this tremendous and diabolic program.
So why do not open for instance in the server all dbf tables? I think to do so.
King regards
Marco

Marco Boschi
info@marcoboschi.it
Posts: 2706
Joined: Fri Oct 07, 2005 01:50 PM
Re: Cryptowall or similar
Posted: Tue Aug 25, 2015 05:58 PM

Marco

I have seen the destruction the crypto virus causes and it also hits .mdb ( access ) files. Back when I worked for state gov, I used advantage database server and I created a task that started in the morning before staff got in til just before the server backup started in the evening. That task went through and opened every .dbf I had effectively locking out anyone using the FoxPro interpreter from making any ( back door ) changes to my files, but it would still allow staff to use FoxPro to make queries.

With that said .. I was not worried too much about having ALL my tables opened because Advantage was server based and my servers all had battery backup and ( hopefully ) would never lose power and crash.

I will say this, it is dangerous to have all .dbf's open in a traditional DBfCdx application, just because workstations ( especially in a network environment ) tend to hang or lock up intermittently and wrecking havoc with your indexes.

No good answer here .. On one hand you have potential virus corruption ( for non opened tables ) .. on the other hand you could have index corruption with badly mis-behaving workstations. If it were me, the customer needs to understand they were a victim of their own 'self infliction' and should bear the brunt and your 'paid' services to put their business application back together... and hopefully they kept a decent off-site backup to restore their data from or ... 'shame on them'.

I did not mean to be ugly, Just my 2 cents worth.

Rick Lipkin

Posts: 389
Joined: Mon Oct 13, 2008 11:26 AM
Re: Cryptowall or similar
Posted: Wed Aug 26, 2015 11:20 AM

Maybe if you change the extension of the DBF files will solve this

Email: SamirSSabreu@gmail.com
xHarbour 1.2.3 + Fwhh 20.2
Posts: 1091
Joined: Thu Nov 17, 2005 11:08 AM
Re: Cryptowall or similar
Posted: Wed Aug 26, 2015 12:53 PM
Rick,
my idea is to launch this program on the server
table indici contains all dbf of my program.

Code (fw): Select all Collapse
...
...
SELECT 1
USE indici
SET INDEX TO indici

GO TOP
DO WHILE !EOF()
      cDbf := ALLTRIM( indici->rdbf )
      SELECT 0
      ?? cDbf , ","
      USE &cDbf
      SELECT indici
     SKIP
ENDDO
inkey(0)
...
...


sambomb,
It might be a good idea

King regards
Marco
Marco Boschi
info@marcoboschi.it
Posts: 2706
Joined: Fri Oct 07, 2005 01:50 PM
Re: Cryptowall or similar
Posted: Wed Aug 26, 2015 06:21 PM

Marco

Crypto is brutal .. if you re-name the files you will need to go through your program and enter the name and extension of the table you wish to open. That may be a lot of re-coding :

Select 1
Use ( "\server\App\MyTable.Dat" ) via "DBFCDX" SHARED

If you want to make a name change to your tables .. now may be the time to think about SQL and Ado .. get those tables on Sql Server, MySql or even Advantage Database Server and you can bundle those changes to your customer and sell it .. might just be a new opportunity!

Rick Lipkin

ps -- .Dat is not immune to Crypto

Posts: 302
Joined: Fri Apr 23, 2010 04:30 AM
Re: Cryptowall or similar
Posted: Wed Aug 26, 2015 09:53 PM

Do not use network maps to open files use UNC path format.

Regards

Nicanor Martinez M.
Auditoria y Sistemas Ltda.
MicroExpress Ltda.
FW + FWH + XHARBOUR + HARBOUR + PELLES C + XDEVSTUDIO + XEDIT + BCC + VC_X86 + VCC_X64 + MINGW + R&R Reports + FastReport + Tdolphin + ADO + MYSQL + MARIADB + ORACLE
nnicanor@yahoo.com

Continue the discussion