#1
|
|||
|
|||
Access Database Program
Hi, could someone highlight how I would go about retrieving serial number for an access database program which has a time trial period, with obviously has no "exe" file or "dlls"
"Personnel Plus Training and Safety Program" Quote:
Last edited by robotics0; 07-19-2016 at 18:51. |
#2
|
|||
|
|||
If it's only an access software, you'll need to view the VBA code behind it and understand what it does.
Alt+F11 will open the VBA editor and allow you to view modules, class objects, etc. and that's the first place to start looking. |
The Following User Says Thank You to Mkz For This Useful Post: | ||
niculaita (07-18-2016) |
#3
|
|||
|
|||
show link to your program
|
#4
|
|||
|
|||
From the installation file you shared, here are some conclusions.
The binary is an MDE file, which is a compiled version of an Access database (MDB). AFAIK there is no way to go back from the MDE to the original code. Unlike VBA macros for Excel, for instance, which can be extracted with some tools, I don't know any for Access code to be extracted from the MDE. You can search the web for this, you'll likely find some paid services for this reversing but no free ones. Anyway, in addition to the MDE "binary" there are also 2 regular MDB files containing tables and records. The password to open these is "TerminalVelocity428". You can then browse the data and the tables and try to check where the expiry might be validated against. Tables genPreference* and genProgramRegistry look like interesting ones. Good luck! |
#5
|
|||
|
|||
Hi Mkz, Yes I was able to source passwords for tables and records, will look into the tables you mentioned more closely and see if i can solve.
cheers |
#6
|
|||
|
|||
Excellent answer, you always learn something
|
#7
|
|||
|
|||
Quote:
What tool used? |
#8
|
|||
|
|||
"strings"
It's in clear text all over the binary file (*.mde). Just run something like "strings HPPSXP2002_XP.mde | findstr PWD" and you can see for yourself. I'm using the SysInternals strings binary, which lists both Ascii and Unicode occurrences. Had this not been in cleartext, a password cracker for the *.mdb files would need to be searched for (can't remember any at the moment) or intercept API calls to the Access runtime to check which connection strings were used by the *.mde to open the database files. |
The Following User Says Thank You to Mkz For This Useful Post: | ||
ontryit (02-08-2017) |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to debug a program spawned by another program? | jonwil | General Discussion | 19 | 11-25-2012 18:39 |
Database programming in C++ | hmora | General Discussion | 1 | 07-12-2004 09:48 |