IP Library Granted Patent US 12,363,080
Granted Patent B2
US 12,363,080 · App. 18/377,522 · Granted Jul 15, 2025

System and method for web-browser based end-to-end encrypted messaging and for securely implementing cryptography using client-side scripting in a web browser

Inventor: Michael A. Meixler (New Hope, PA)
Assignee: Meixler Technologies, Inc.
H04L63/0428G06F16/958G06F21/565G06F40/14H04L9/0643H04L9/3247G06F2221/033H04L9/0631H04L9/0637H04L9/3263H04L67/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,363,080
App. No.
18/377,522
Granted
Jul 15, 2025
Kind
B2
Abstract

A system and method for sending end-to-end encrypted messages comprising a sender's web browser, a recipient's web browser, and a server. The system and method avoid both the sender and the recipient having to download encryption programs themselves onto their respective computers. In addition, the system and method ensure that unencrypted messages are never disclosed to the server. The system and method operate by first downloading the web browser files, verifying them and then preventing the web browser page from refreshing, thereby preventing malicious code from entering the web browser each time the web browser page would normally be refreshed. The system and method also provide for securely implementing cryptography using client-side scripting in a web browser.

Claims (10)

1. A method of encrypting a message using a web browser comprising the steps of:

running said web browser on a user's computing device;

downloading, by said web browser, client-side scripting from an untrusted first server operated by a first provider;

verifying, by said web browser, integrity of said client-side scripting in conjunction with a cryptographic hash obtained from a second server, operated by a second provider, trusted by the user; and

executing, by said web browser, said client-side scripting to encrypt said message only upon success of said verification.

2. A method of decrypting an encrypted message using a web browser comprising the steps of:

running said web browser on a user's computing device;

downloading, by said web browser, client-side scripting from an untrusted first server operated by a first provider;

verifying, by said web browser, integrity of said client-side scripting in conjunction with a cryptographic hash obtained from a second server, operated by a second provider, trusted by the user; and

executing, by said web browser, said client-side scripting to decrypt said encrypted message only upon success of said verification.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2023
From: MEIXLER, MICHAEL A.
To: MEIXLER TECHNOLOGIES, INC.
Reel/Frame 065186/0245 →
Continuity (4)
Continuation 16704475 · Dec 5, 2019
Provisional Application 62928737 · Oct 31, 2019
Provisional Application 62800800 · Feb 4, 2019
Related Publication 20240039899A1 · Feb 1, 2024
References Cited (83)
US 6314451B1 · Landsman et al. · 2001 [cited by applicant]
US 6418472B1 · Mi et al. · 2002 [cited by applicant]
US 6477550B1 · Balasubramanian et al. · 2002 [cited by applicant]
US 7565543B1 · Mungale · 2009 [cited by applicant]
US 8542823B1 · Nguyen et al. · 2013 [cited by applicant]
US 8769260B1 · Kwan · 2014 [cited by examiner]
US 9129095B1 · Lam et al. · 2015 [cited by applicant]
US 9148428B1 · Banga et al. · 2015 [cited by applicant]
US 9245108B1 · Khajuria et al. · 2016 [cited by applicant]
US 9292709B1 · Hundt · 2016 [cited by examiner]
US 9426171B1 · Jezorek · 2016 [cited by examiner]
US 9524398B1 · Hundt · 2016 [cited by examiner]
US 9635041B1 · Warman et al. · 2017 [cited by applicant]
US 9680873B1 · Halls et al. · 2017 [cited by applicant]
US 10505736B1 · Meixler · 2019 [cited by applicant]
US 20020049819A1 · Matsuda · 2002 [cited by examiner]
US 20020162003A1 · Ahmed · 2002 [cited by examiner]
US 20030105888A1 · Connelly et al. · 2003 [cited by applicant]
US 20040019780A1 · Waugh et al. · 2004 [cited by applicant]
US 20040049673A1 · Song et al. · 2004 [cited by applicant]
US 20070174915A1 · Gribble et al. · 2007 [cited by applicant]
US 20070192854A1 · Kelley et al. · 2007 [cited by applicant]
US 20070300057A1 · Corcoran et al. · 2007 [cited by applicant]
US 20090006860A1 · Ross · 2009 [cited by applicant]
US 20090110194A1 · Athsani · 2009 [cited by examiner]
US 20090144382A1 · Benninghoff, III · 2009 [cited by applicant]
US 20090287931A1 · Kinsella · 2009 [cited by applicant]
US 20110016169A1 · Cahill et al. · 2011 [cited by applicant]
US 20110191366A1 · Eustace et al. · 2011 [cited by applicant]
US 20110296179A1 · Templin et al. · 2011 [cited by applicant]
US 20120198234A1 · Chung · 2012 [cited by examiner]
US 20120215831A1 · Urbach · 2012 [cited by examiner]
US 20130019090A1 · Wicker · 2013 [cited by examiner]
US 20130198521A1 · Wu · 2013 [cited by applicant]
US 20130262851A1 · Hirvonen · 2013 [cited by applicant]
US 20140123279A1 · Bishop et al. · 2014 [cited by applicant]
US 20140173744A1 · Borohovski et al. · 2014 [cited by applicant]
US 20140331119A1 · Dixon et al. · 2014 [cited by applicant]
US 20150149775A1 · Gadotti · 2015 [cited by applicant]
US 20150195253A1 · Ander et al. · 2015 [cited by applicant]
US 20150207783A1 · Templin · 2015 [cited by examiner]
US 20150312217A1 · Lee · 2015 [cited by examiner]
US 20150350179A1 · Kobayashi · 2015 [cited by examiner]
US 20160294561A1 · Base et al. · 2016 [cited by applicant]
US 20170149782A1 · Bender et al. · 2017 [cited by applicant]
US 20170193464A1 · Sher · 2017 [cited by applicant]
US 20170244729A1 · Fahrny · 2017 [cited by examiner]
US 20180018468A1 · Williams et al. · 2018 [cited by applicant]
US 20180124007A1 · Ploch et al. · 2018 [cited by applicant]
US 20180137303A1 · Farkash · 2018 [cited by examiner]
US 20180205549A1 · Blinn · 2018 [cited by examiner]
US 20180205554A1 · Blinn · 2018 [cited by examiner]
US 20180351921A1 · Sharifi Mehr · 2018 [cited by applicant]
US 20190042283A1 · Urbach · 2019 [cited by examiner]
US 20190089706A1 · Rose et al. · 2019 [cited by applicant]
US 20190306248A1 · Swarangi et al. · 2019 [cited by applicant]
US 20200128086A1 · Lewis · 2020 [cited by examiner]
US 20200404005A1 · Greevy · 2020 [cited by applicant]
US 20220222342A1 · Ma · 2022 [cited by applicant]
AU 2014203156A1 · 2014 [cited by examiner]
CN 101321057A · 2008 [cited by examiner]
CN 102332071A · 2012 [cited by applicant]
CN 101689989B · 2012 [cited by applicant]
CN 104468477A · 2015 [cited by applicant]
CN 104503760A · 2015 [cited by examiner]
CN 108667799A · 2018 [cited by applicant]
EP 2685682A2 · 2014 [cited by applicant]
EP 3026557A1 · 2016 [cited by examiner]
JP 2000250408A · 2000 [cited by applicant]
JP 2008250903A · 2008 [cited by applicant]
JP 4581280B2 · 2010 [cited by examiner]
JP 4656359B2 · 2011 [cited by examiner]
KR 20130077359A · 2013 [cited by applicant]
WO WO0049786A1 · 2000 [cited by examiner]
WO WO2016179957A1 · 2016 [cited by examiner]
Emily Stark; (From Client-side Encryption to Secure Web Applications); pp. 55; Jun. 2013. [cited by examiner]
Ptacek, T. “What's the Chicken-Egg Problem With Delivering Javascript Cryptography?”, http://www.matasano.com/articles/javascript-cryptography. (2011). [cited by applicant]
White, K., “Firefox Send Is An Easy Way to Share Large Files Securely”, https://www.wired.com/story/firefox-send-encrypted-large-files. (2019). [cited by applicant]
“Web Crypto API”, https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API. (2019). [cited by applicant]
“What do client side and server side mean? Client side vs. server side.” Cloudfare, 2022, retrieved on Dec. 20, 2022 from https://www.cloudflare.com/learning/serverless/glossary/client-side-vs-server-side. [cited by applicant]
Dong et al., “Protecting Sensitive Web Content from Client-Side Vulnerabilities With Cryptons”. (2013). [cited by applicant]
Stark, “From Client-Side Encryption to Secure Web Applications”, Massachusetts Institute of Technology (2013). [cited by applicant]
D'Angelo et al., “Content Cloaking: Preserving Privacy With Google Docs and Other Web Applications” (2010). [cited by applicant]