Cryptography Sys. admin in a bit of a pickle with backup of a passcode program that doesn't work on iOS 11 and doesn't exist in the app store anymore |
- Sys. admin in a bit of a pickle with backup of a passcode program that doesn't work on iOS 11 and doesn't exist in the app store anymore
- Populating PostgreSQL DB using bitcoind RPCs and API
- Displaying encrypted text without the os being capable of accessing it
- private.key file?
- Suggest build for personal crypto?
| Posted: 21 Nov 2017 04:36 PM PST tl;dr: I have a backup file from an iPhone app iPasscode, a deprecated app that is no longer on the app store, developer is AWOL, Apple sends me to developer, trying to figure it out myself as it contains a bunch of stuff for a client. Inane examples below Hi! I'm a systems admin in a small MSP that manages mostly windows environments. Server setup, basic things, etc etc. I understand the uber basics of how cryptographic algorithms work (I think), a client hit me with a curve ball and I want to help him but really don't know where to start as this quickly went above my level of knowledge. Client had a program on iPhone called iPasscode. This program predates iOS 11, so it's 32-bit. As such, when client upgraded from 10.x to 11.x, the program ceased to function. The developer has gone AWOL and pulled it from the app store, Apple sends me in a loop to try to contact the aforementioned developer, clients backup situation was non-existent (it was a BYOD and we remedied that, but too little too late). During the process of the iOS 11 upgrade, client was asked to backup the database from iPasscode. He obliged, and proceeded to send me a file called backup_local.ipb I opened it in notepad just to see what it is, and the format is loosely this: 1:Base64 name of entry:username:password:note 2:... etc I'd never really delved into trying to decrypt or whatever things before, so I found a bunch of sites that helped figured out what the type of encryption/hash was and that's how I was able to figure out what the Base64 thing was. Example 1:Q2hhc2UgTUM= I was able to use John's Base64 decoder to figure out that was Chase MC The same decoding would not work on what I assume are usernames or passwords, but would work on some of the ancillary text: eg 'cat's name'. Here's an example of one of the ancillary texts: V1BBL1dQQTI= That comes back as: WPA/WPA2 I know some of the passwords on this list, but not all of them. One of the passwords is this: 1wHdeyTXkU+EuZWDuZUT8WVm1jM= Now, I know that password is, now at least, actually: password1234 I have no idea how to figure out how one equals the other. When I put the 1wHdeyTXkU+EuZWDuZUT8WVm1jM= in any of the 'check this hash' websites, they are unable to determine what it is. An interesting caveat about this program, it was touted as 'just remember this one password' -- I also know what that one password is, but at a certain point the whole salting and hashing thing is just above my pay grade. I don't want to send this file out, obviously it contains sensitive information. I just want a direction to go. I tried hashcat earlier today but as I don't know what kind of encryption/hash this is, I was unable to use it. The usernames are largely different lengths and bits. The password list itself starts at this line, which I am willing to provide as I don't believe it gives any information that is useful without the rest of it: 12;0:YXBw:owner2:fec541317157cfb7992b7f483a6f783f1bdb0b73e78e3435d00a54067f637aa7:bnVsbA==;app I have figured out that: YXBw is Base64 for app fec541317157cfb7992b7f483a6f783f1bdb0b73e78e3435d00a54067f637aa7 is SHA256 for hunter0704 <- that is the master password if it matters. Also, none of the other username or passwords are recognized as SHA256. The list itself starts at that line, then goes sequentially from 1 to 15, then each row is an odd number from there to 83. I am unsure why. Any advice you fine folks can give would be very helpful. Also if this is a lost cause, please let me know. It's an exercise in learning and trying to be helpful to the client. At the very least, I was able to provide him a list of the entries he had so he knows which passwords he needs to reset. [link] [comments]  |
| Populating PostgreSQL DB using bitcoind RPCs and API Posted: 22 Nov 2017 01:42 AM PST I'm attempting to create a PostgreSQL database with block data on:
And transaction data on:
I'm struggling to figure out the best way to use the bitcoin daemon RPCs/API to get the data, so that I can put it into the database. If anyone has any ideas, I'd be grateful! Cheers. [link] [comments]  |
| Displaying encrypted text without the os being capable of accessing it Posted: 21 Nov 2017 07:19 AM PST So, this is a super specific and theoretical question, but has anyone explored cryptography assuming you have a compromised machine ? Specifically if it is possible to decrypt and display a given encrypted text without the OS being able to access either the key or the unencrypted text . [link] [comments]  |
| Posted: 21 Nov 2017 11:09 AM PST I found this file when I was doing a file recovery on hd.. I found it in under lost files.. I was able to open the file and it has over 2000 characters... any idea what it is?? [link] [comments]  |
| Suggest build for personal crypto? Posted: 21 Nov 2017 02:51 PM PST Can someone help me decide on what sort of computer to get/build for personal computer security? I'd like to be able to rely on it for cryptography purposes. Specifically I'm worried about firmware backdoors, etc that I don't have access to or control over. How can I know my hardware is behaving the way I tell it to? And what about peripherals? The USB standard is completely insecure and wireless cards use closed source firmware/drivers, so even if I got a secure computer interfacing with it securely is a bit of a conundrum. Please help [link] [comments]  |
| You are subscribed to email updates from Cryptography news and discussions. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment