I backed up my last iPhone a few months ago, before purchasing a new XR so I could move all of the info from my past phone on to the new one. At the Apple Store, I ended up just connecting the two phones together to do the data transfer, so I didn’t end up needing the iTunes backup from my PC after all.
Fast forward to last week, my iPhone stopped working, and since shelter in place is still in full effect in CA, I had to send my phone in and they sent me a new replacement today. Since it stopped working suddenly, I wasn’t able to get my current data back, but I fortunately still have the backup I made in February. Problem is, it is asking for a decryption pass code that I never created (at least not within the last 10 years).
I have called Apple Support, and they told me that they have no way of accessing or resetting this password, does anyone have any idea what it could have been? Could it have been a password that I entered when I first setup my Apple ID in 2008? Could it have been a password I set on another computer?
This backup contains years of photos of travelling, life events, and moments with those who have passed away. Any help would be graciously appreciated.
I need help I feel like I lost documents I worked on for 2 long years, it’s a huge problem to me even if it looks simple.
here is my issue :
when I enter my password trying to login, the screen becomes black for 5 seconds then comes up again with the login screen … login loop
so when I tried to access tty1
I found this message :
Signature not found in user keyring
Perhaps try the interactive ‘ecryptfs-mount-private’
I issued ‘ecryptfs-mount-private’, but it asks for the Login passphrase, I don’t remember it , it’s maybe one of my old password that I changed so many times but I still have the Passphrase, I mean the “mount passphrase”
the mount passphrase actually is the encryption key, wrapped (encoded) using login passphrase.
and I know my password I can access tty
I can’t remember the “Login passphrase”.
is there any way to mount the encrypted home directly using the mount passphrase, without the login passphrase ? or disable the encryption so I can access my home. if possible disable the encryption without deleting any file ???
Let’s Encrypt is a free https certificate you can install on your cheap VPS for free, browser-validated https. In this tutorial, we’ll walk through setting up Let’s Encrypt https on an nginx host running on Debian 10.
We’ll be installing nginx from scratch but not will not be getting into php-fpm and other extensions in this tutorial. I’ll be starting from a spanking new VPS on Vultr.
This tutorial assumes that you’ve already got your DNS records setup. In other words, if you’re setting up for www.example.com, then www.example.com already has an A record or CNAME that points to your VPS. Note that the certbot installer we’ll be using will query DNS, so this must be working properly.
We want separate logs for each domain we host, and we want to rotate those logs. We can Debian’s log rotation system to accomplish this. We do this by placing the appropriate rules file in /etc/logrotate.d. Start with nginx’s basic log rotation rule:
I would like to install Ubuntu on a two-disk RAID 1 with dm-integrity and LUKS2-encryption.
Unfortunately, neither Ubiquiti, nor the textmode-installer offer such a solution.
However, this seems simple enough to execute: Formatting both drives with “physical partitions for encryption” in gparted and then calling cryptsetup luksFormat --type luks2 --integrity sha256 <device> for either drive as a basis to create the RAID device, LVM and filesystem on top of in the manual installer.
Is there anything that needs to be considered with this approach? Does Ubuntu demand certain LUKS-parameters or is something particularly advisable to use for this purpose?
Do the devices need to be “opened” in any particular way before launching the installer and/or do they have to be added manually to a file to be decrypted at boot? Is the --integrity function used automatically?
Is this even the best approach or is there another way to accomplish this? (Excluding the usage of Btrfs/ZFS filesystems)
And, a related side-question, would the Btrfs-filesystem be of any additional value regarding data integrity in this scenario, rather than Ext4, even though its RAID-functions are not used?
I’m trying to access my backup from an SSD with Linux Mint on it, but my user is password-protected and encrypted. I have tried numerous methods to try and input the password, but nothing has worked and neither has booting from a live USB. (I was using encryptfs on the USB.) Fiddling with BIOS settings is quite tedious, and not something I’d want to do.
I would like to keep local time machine backups for my Mac mini and network backups for my MacBook on a single partition USB drive connected to Mac mini. I know I can do this if the backups are not password protected. Can the local time machine backup database and sparsebundle database be password protected and still be on the same drive?
The drive was not previously encrypted (it was Journaled HFS +) but it is currently being encrypted by Mac mini when I selected it to secure Backups.backupdb with a password. Will this ruin the sparse package for the MacBook that is on the same partition?
Let's say I create a 100 KB file that only contains 1234567890, that is, a known value. This file would be in several folders as bait.
Once a Rasomware reaches the folder and encrypts this file (considering that all other forms of anti-rasomware protection failed), could it generate what is the private key that would decrypt that file and all other files, knowing the contents of the previous file?
Does it also help to have the captured public key in memory?
Does having a large known file help?
I know this goes against the asymmetric key theory but there is generally a difference between crypto theory and practice as hashes should be unique for each input but in practice there is always the possibility of collisions .
Let me start by saying that I am not questioning the usefulness of encrypting EBS volumes, nor asking how it works.
I wonder what specifically encrypting EBS volumes is protecting against.
For my personal laptop, the reason for encrypting the hard drive is if it is ever stolen, while the thief could create a copy of my hard drive, the data is encrypted at rest and cannot be decrypted without logging into my laptop and / or provide the decryption key.
For unencrypted EBS volume connected to an EC2, I guess the data can only be accessed by the EC2 it is connected to. Or at least, nothing else can access data other than that EC2 without specifically allowing access to it. Is this assumption incorrect?
If this assumption is correct, then encrypt EBS volume protects against … what? The possibility of the hard drive being stolen from the Amazon data center? Or am I assuming someone could infiltrate your network and digitally copy data from hard drives, which would then be encrypted?