Author |
Topic: PEEK() function (Read 1056 times) |
|
carninesix
New Member
member is offline
Posts: 9
|
 |
Re: PEEK() function
« Reply #10 on: May 3rd, 2015, 10:26am » |
|
Hello,
This is not copy protection, this is for a security measure.
The reason I want to use PEEK() as a command is to look at specific memory, the ROM on the mother board.
PEEK() is the direct command I know and it is not reliant on any drivers, API's, DLL's or OS's.
Most modern OS's run in protected memory or just don't allow you to look directly at motherboard ROM's.
I want to write code that reads the ROM memory directly and use some values as part of a password. Some of the password will come from the user, the rest from ROM. Each chip has a serial number, this is one of the things I want to use.
Two reasons for this. Most people use or pick easy passwords, including 40-50 unique characters will stop this, but do it invisibly as far as the user is concerned. Second, will mean that the encryption/decryption will only work on one machine.
I know that any cypher can be broken, it is only a matter of time. I will be using multiple layer of various types.
Steve
|
|
 Logged
|
|
|
|
Richard Russell
Administrator
member is offline
Posts: 1348
|
|
Re: PEEK() function
« Reply #11 on: May 3rd, 2015, 11:07am » |
|
on May 3rd, 2015, 10:26am, carninesix wrote:| I want to write code that reads the ROM memory directly and use some values as part of a password. |
|
As I said that can be spoofed so that when you think you are looking at the ROM memory "directly" actually you aren't because your code is running in a VM. Don't you care about that?
Richard.
|
|
Logged
|
|
|
|
carninesix
New Member
member is offline
Posts: 9
|
|
Re: PEEK() function
« Reply #12 on: May 3rd, 2015, 10:25pm » |
|
Hello,
VM's are not perfect, and I shall be exploiting the flaws in them. Also I will not just be relying on this as a sole check.
This is both an exercise and a problem to be solved for me, I am doing this to push myself.
I have been around computer since '77, whilst everything appears to have got easier on the surface when looking under the hood it is much more difficult.
I have worked in binary, machine code, Cobol, Fortran, Basic ( my preferred language ) and dabbled with a couple of others. My problem today is I am way too rusty, not been actively programming hard stuff for a long time. Most of my recent work ( last 15 years ) has been solving communication/translation issues.
I may never get this to work the way I want, but it will be fun trying.
I am also pleased with the help/attitude here, I was on another forum and was just shot down there. Here I am being given the help and also the reasons behind the help.
Steve
|
|
Logged
|
|
|
|
|
