Decrypting a file
#1
Posted 30 March 2009 - 08:28 PM
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.
#3
Posted 30 March 2009 - 09:21 PM
The file that is encrypted ends with .ift i have 3 other files there that end with .dsh, .dat and .lst which all have the word KEY in there filename.
If the "KEY" files are opened in notepad, through all the jargon there is "VeriSign INC" shown in plain text. The file contains a list of compatible HDD models i can use, this device is very picky and the HDD just died...
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.
#4
Posted 30 March 2009 - 09:59 PM
For all practical purposes, if the file really is encrypted, as opposed to just encoded, the likelihood of being able to decrypt it is slim, especially if you do not know the file that created it, or uses it. It may be a Verisign license file, it might not.
#5
Posted 30 March 2009 - 10:20 PM
It is a file off a photocopier hard drive that stores what hard drive models can be used for the machine, it is installed with the system software and the copier checks the harddrive's model number, if it matches it works, otherwise it errors.
an 80GB hard drive from the manufacture is $500, so if i can get the model's out of the file, i can save myself $500...
And yes, i suppose you would need a pole too... lol
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.
#6
Posted 30 March 2009 - 10:28 PM
#7
Posted 30 March 2009 - 10:47 PM
- these hard drives are listed in a "encrypted or encoded" file on the hard drive, this get placed there when you install the system software (via a connected PC).
- hard drives from the photocopier manufacture cost $500 for an 80GB.
- to avoid this cost, we are trying to find out what other hard drives are supported, which is in the file mentioned above, and get one of them instead of forking out $500.
does that make sense?
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.
#10
Posted 31 March 2009 - 06:26 PM
Quote
This means it is probably signed, this doesn't really say anything about the algorithm since you can use different algorithms for most protocols.
Quote
Can you perhaps post these files? This might provide some information.
Quote
Exact make&model?
This post has been edited by Carpetsmoker: 31 March 2009 - 06:27 PM
#11
Posted 31 March 2009 - 07:52 PM
Carpetsmoker, on Apr 1 2009, 10:26 AM, said:
What program would i use to "try" those algorithms?
I don't have the files with me at the moment, i am at home, i will try to post them all though.
EDIT: Here is a link to the files http://202.45.110.174/canon
This post has been edited by KamakaZ: 31 March 2009 - 07:57 PM
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.
#12
Posted 31 March 2009 - 11:50 PM
KamakaZ, on Apr 1 2009, 01:52 AM, said:
There are many, google seems to turn up a good result at the first hit:
http://www.google.com/search?client=opera&...-8&oe=utf-8
http://www.google.com/search?hl=en&cli...amp;btnG=Search
... ect.
A quick glance doesn't tell me anything, other than:
[~/decrypt]% file * hdformat.ift: data key.dat: data key.dsh: DOS executable (COM) key.lst: data
The .dsh seems to be an executable? Perhaps used for decrypting?
#13
Posted 01 April 2009 - 04:51 PM
if that key file is used to encrypt/decrypt the file, how would i use it??
What program did you use to give you that information? About what each file is?
There's no place like 127.0.0.1
There are 10 types of people in the world, those that can read binary, and those who can't.
#14
Posted 01 April 2009 - 06:55 PM
You can try running a disassembler on the program and see if that yields any useful information...
Other than that, it is very difficult for me to do anything, since I have no ciphertext at all ...
Quote
I don't know, it didn't come with a manual.
Quote
I used file(1), it is a command found on most UNIX-like systems, it can recognize file types based on known header, footer, data patterns.
A Windows version can be fetched from:
http://gnuwin32.sourceforge.net/packages/file.htm

Help


Back to top










