From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] interwindow bleed
Date: Sun, 15 Nov 2020 07:45:46 -0500 [thread overview]
Message-ID: <20201015074546.eklhad@comcast.net> (raw)
In-Reply-To: <20201115122657.GA10863@toaster>
> Does the presence of this global object still open a ... path ...
No. Here is an analogy.
You and I open a joint checking account, with nothing in it.
I can't steal any money from you unless you put it there.
A bank isn't going to put its valuable customer data in this shared object for others to look at.
Karl Dahlke
next prev parent reply other threads:[~2020-11-15 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 4:22 Karl Dahlke
2020-11-09 23:11 ` Adam Thompson
2020-11-10 1:28 ` Karl Dahlke
2020-11-15 12:26 ` Adam Thompson
2020-11-15 12:45 ` Karl Dahlke [this message]
2020-11-16 3:27 ` Kevin Carhart
2020-11-16 7:54 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201015074546.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).