DEVISED IDEA : Non Socket Programmed ShareFolder Based (Featured AES256 conversation Encrypt/Decrypt by SSK) Portable Chatting App
-
Multi-Users executing the "sharechat" in the same shared folder concurrently via INTRANET(also works without internet), Dialogue perfectly secured by preset password's encryption for each user input.
-
No server, No client, and No mercy for not knowing the password. Any wrong login attempt will be notified to the others in chatroom, with logging the typed wrong passwords and the IP address of the intruder on the Encrypted chatlog.
-
Without a certification key file or a password, it's Non-admissible and should start over the key making process with empty chatlog
-
If any user needs to instant clean-up with leaving no evidence including using of the chatapp, call "자비스, 메리크리스마스(Jarvis, merry christmas)" with typing password for next input. It all terminates every app process instantly from world-wide chat-app users.
Since the "TERMINATE" ChatBot command is written inside the encrypted sharing chatlog, it's impossible to start the app again without deleting the previous chatlog("said.log"). Same password will be retained while not deleting the previously created SSK("rkey.cer")
and
DEFAULT PASSWORD IS password
챗봇을 쓰려면 자비스, 를 부르세요(호출시 비밀번호 필요)
자비스, 메리크리스마스를 명령하시면 해당 암호화 채팅을 공유하는 전 세계 sharechat의 클라이언트 채팅 내역이 삭제되고 해당 모든 컴퓨터들에서 즉시 종료됩니다.
(기존 암호화 대화 로그-said.log 삭제 전에는 앱 재실행 불가)
(e.g. Secure mode switch:F6, Windows Start up program registry registration:F10...)
In "BALLOON" mode the main app UI flickers when any new change turns out, while "POP" mode throws notifications from the right-corner taskbar.
Type password for initial use when start from the scratch, or login with predefined password + created Symmetric Single Key pair.
Start from the scratch: Modal for creating initial password and its Secret Symmetric Single Key (signed by password).
The First field for admin password login, granting an authority of making a new password of its app.
(pre-defined in the source code to make a customizable release for each app in the compiling stage.)
The Second field will be activated by successful login of the First field, so create new password thereafter by writing on the Second field.
After making a new password, the modal will be closed and should write that password exactly on the main UI dialogue textInput.
With the successful MainUI login, a new password key signed Secret Symmetric Single Key file("rkey.cer") and conversation dialogue("said.log") written in AES256 encrypted by the key will be created in the current app executing folder.
Thereby starts ShareChat in the SECURE MODE which hides the contents and turns into the previous login mode when outfocused(clicking another app) by the user.
Contents are AES256 encrypted with the key and only decryptable by the pre-authorized MainUI.
If a wrong password is tried for logging in, the system alerts the wrong password in the contents and kicks out that user by exiting the app of the user.
For using multiple chat apps simultaneously for each person, the app's name is consisted of current app running folder's name
(e.g. Since below screenshot's running folder is named as sharchat, the app's notification title is the "sharchat")