Online SHA1 hash generator

I've been stuck on this for more than 4 days.I've searched and tried almost everything given on Google Developers website, StackOverflow and other helpful blog posts. But nothing has worked for me.

My app was successfully signing-into the Google account but when I made some basic changes in the app (not related to Google API at all) and uploaded the updated APK on playstore, Google Sign-In hasn't worked after that.

When I run the app from Android studio (using debug build-variant and release build-variant), sign-in works like a charm.Then I generate the signed-apk and upload it on PlayStore. And when I install app from PlayStore, it doesn't sign-in and gives statusCode=DEVELOPER_ERROR

I've created the project on Google Cloud Console, created OAuth 2.0 client ID for Android inside that project and added SHA1 (generated for release) inside that client ID.Then I downloaded google-services.json file and placed it inside app folder of my project.

I don't seem to miss anything. But Sign-in still doesn't work.Please let me know what's the problem.

P.S.: Firebase is also integrated into my Android Project.

Here is the set-up code for GoogleApiClient inside onCreate()

googleApiClient = new GoogleApiClient.Builder(this)                .enableAutoManage(MainActivity.this, this)                .addApi(Auth.GOOGLE_SIGN_IN_API, signInOptions).build();googleApiClient.connect();

This is the method invoked when Sign-In button is clicked.

public void signIN() {        Intent intent = Auth.GoogleSignInApi.getSignInIntent(googleApiClient);        startActivityForResult(intent, REQ_CODE);}

This is the code from onActivityResult()

if (requestCode == REQ_CODE) {            GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);            if(result.isSuccess()){                GoogleSignInAccount account = result.getSignInAccount();                //Do something            }else{                Toast.makeText(getApplicationContext(), "Unable to Sign in. Try again.", Toast.LENGTH_SHORT).show();            }            Log.d("GoogleResult", result.getStatus().toString());}

Help me improve the question before down-voting or reporting it.

I have database with following fields: id, q_id, text, session etc. and I have already 2 records there. I want to hash each line with SHA1 alghoritm (every line is unique of course). I tried this:

@w = Digest::SHA1.hexdigest(id+q_id+text+session)

but it doesn't work.

I've tried to deploy an OVF export on VMWare Workstation.I received the following message:

SHA1 digest of file "appliance.ovf" does not match manifest.

Upon investigating the issue, I've discovered that SHA1 has been dropped and VMWare only accepts manifests that have a SHA256 hash.

My questions are if I delete the appliance.mf file, will it still import maintaining the structure of the .ovf export? Or will it generate a new hash based on SHA256?? Or how can I generate a new SHA256 hash for the .ovf file?

I have to make a SOAP request to a WebService which expects only a StringThat string is the result of a Digital sign xml file converted to base64.I have the xml file, the private.key and the certificate.crtNow I need to generate the CMS signed data with the xml file, and signed with my certificate using SHA1 + RSA. The result of this I have to convert to base64.

Can somebody help me to do this?

I'm using Hibernate/Java to persist an entity to a database. The entity has a password field which is a String. When registring a user in my application, I hash the password using SHA-1 (I acknowledge this is a little weak). This produces a byte[] which I then convert to String using new String(byte[] arr);Whenever I want to log a user in, I simply retrieve the hashed password from the database (as String) and compare it with the digest of the input password at login using hashedPasswordFromDatabase.equals(SHA1_HASH(inputPassword));

This worked perfectly on my development system (Windows 7, JDK 1.6.0_23 / JDK 1.7, MySQL 5.5, Tomcat 6.0.26) but upon deploying it on our server (running JDK 1.6 on Linux), the equals method never evaluates to TRUE even for equal passwords. I quickly setup a new development system (Ubuntu 12.04, MySQL 5.5, JDK 1.7.0_03, Tomcat 7.0.22) and it doesn't work there too.

I'm aware of the possible encoding issues stated in the Java API documentation for the String class and also stated in several places here on SO. I've tried a couple of encodings suggested on this forum (e.g Base64, Latin-1) and I ended up with UnsupportedEncodingException. I think I'll be better off avoiding the String conversion. So how do I design my database such that the Hibernate-generated entity class comes up with byte[] for the password field instead of String?