SHA384 online Hash Generator

Sorry for my bad English...The string:

NFkwYnB5cjA0V09HK1Q2SHZXZHNydz09

I think it's a MD5 hash, but a MD5 returns only lower case characters and, as you can see, the result returns the both (lower and upper case).

I have run into a CSR generation problem I can't seem to explain and was wondering if someone could either help me with my command, or tell me what I am generating.

I think I am generating CRT Certificates in PEM format, but it seems my key is not in PEM format !?

Here is what I do, and what I get.I create a CSR with:

openssl req -nodes -new -newkey rsa:2048 -sha256 -out test.csr

This generate 2 files:privkey.pem and test.csr

Now when I try and update some servers, they complain that my Private key is not in PEM format. nginx and apache seem happy with my key.

When I then convert the key with:

openssl rsa -in privkey.pem -out privkey.rsa.pem

It works !?!

vimdiff shows me the difference in the files visually, and one can see that not only is the heading different, but the content is also been changed (after the first 4 characters)

And thus my question

is the key created in DER - PEM format, even though I specify not to use DER in the create line ?

What are the differences between SHA1 and RSA? Are they just different algorithms or are they fundamentally (i.e. used for different things) different on some level.

We have one ASP.NET web application which is built in .NET Framework 4.5 version. Currently on production this application is using SHA1 encryption algorithm. This algorithm is set in "MachineKey" tag of application's web.config file. This application uses ASP.Net Membership concept for maintaining Login credentials.

As the SHA1 algorithm is on verge of degradation so we want to update our application from SHA1 to SHA2. For this we have set "HMACSHA256" in "MachineKey" tag of application's web.config file.

After upgrading our application to SHA2 with the above settings, we expect that the older user's passwords (which were encrypted using SHA1 and already present in membership database) will not work with SHA2 algorithm. But it allows older users to login without any modification in previously encrypted password.

Question 1: Are the changes made in "MachineKey" tag of application's web.config file enough/recommended for this migration?

Question 2: As we are still able to login into the application using previously encrypted passwords, does the membership database really uses the SHA2 encryption set in web.config file? Or we need to add some additional settings to enable SHA2 encryption on membership database level? Please advice.

Please suggest if there is any best way to enable SHA2 encryption on Membership database level.

Please can someone tell me the itunes/SHA-1 backup file name for Safari browser history for iOS 11.0 Beta 1 or iOS 10.3.2.

I tried searching for the file name but with no luck.

Your help will be appreciated.

Thanks in advance.