Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A new method of leveraging transparent authentication and encryption to protect confidential information on Instant Messaging Apps.

IP.com Disclosure Number: IPCOM000248709D
Publication Date: 2016-Dec-28
Document File: 6 page(s) / 104K

Publishing Venue

The IP.com Prior Art Database

Abstract

The invention provides a method to protect confidential information on Instant Messaging Apps by typing a secondary password anywhere without prompted authentication and utilizing it to specify what content you'd like to protect. The combination of two advantages will offer very easy hands-on experience to mobile users and prohibit sensitive information from stealing when default user credential of your Apps is exposed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

1

A new method of leveraging transparent authentication and encryption to protect confidential information on Instant

Messaging Apps.

Currently most of Instant Messaging users on mobile are experiencing a similar embarrassment that the confidential or private information in chatting history are easily exposed to the ones they wouldn't like to share, especially for some cases as below:

1. The family, friends or colleagues of App owner reach the App unintentionally. 2. App owner is willing to hide sensitive information in chatting history but wish the process could be totally transparent to others. 3. App owner would like to protect part of text, images or videos from being glanced by other people when auto login is enabled on the App.

Based on above requirements, we need figure out a new method to protect the data over the sessions in a very convincing and flexible way, not only able to handle authentication spoofing to others but also have the capability of specifying and encrypting the content needs protection.

By default one App has its own user credential and this part of authentication has nothing to with this invention.

1. Firstly, need design "Transparent Data Protection" to switch chatting mode in the global settings of the App. After logon App owner can go to settings and set a "Data-Protection Password" like an example "passw0rd", then two underlying passwords will be generated automatically for next usage that include "Start-Point" and "End-Point" password with adding a suffix "1" or "2" after "Data-Protection Passwor...