Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
tls-tracking
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Frank Sauerburger
tls-tracking
Commits
91295ab1
Verified
Commit
91295ab1
authored
6 years ago
by
Frank Sauerburger
Browse files
Options
Downloads
Patches
Plain Diff
Rephrase privacy policy
parent
444a1cb1
No related branches found
Branches containing commit
No related tags found
1 merge request
!2
Resolve "Add static files"
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
app/assets/privacy.html
+6
-6
6 additions, 6 deletions
app/assets/privacy.html
with
6 additions
and
6 deletions
app/assets/privacy.html
+
6
−
6
View file @
91295ab1
...
...
@@ -170,21 +170,21 @@
<li>
You may exercise any of your rights in relation to your personal data by written notice to us.
</ol>
<h3>
Cookies that we use
</h3>
<p>
We do neither use nor set any cookies
</p>
<p>
We do neither use nor set any cookies
.
</p>
<h3>
About TLS and HSTS based tracking
</h3>
<p>
TLS is a protocol used to transmit data via an encrypted communication
channel over the internet.
It is used for th
e HTTPS protocol. HSTS is a
security policy that can be employed by websites using HTTS. A website using
channel over the internet.
The secur
e HTTPS protocol
uses TLS
. HSTS is a
security policy that can be employed by websites using HTT
P
S. A website using
HSTS signals the browser to use secure HTTPS connections for any request in
the future even when the unsecure HTTP version
is requested by the user
.
</p>
the future even when the
user requests the
unsecure HTTP version.
</p>
<p>
By using many subdomains, and employing HSTS selectively for the
subdomains the website can identify the browser on subsequent requests by
checking for which subdomains the browser remembers the HSTS policy
</p>
<h3>
How we use TLS and HSTS based tracking
</h3>
<p>
The demonstration of the TLS and HSTS based tracking for educational
purposes is the sole purpose of this website. The website uses TLS and HSTS
based tracking to encode a user
defined string. The user
defined string is
not decoded on the server. The user
defined string is only decoded in the
based tracking to encode a user
-
defined string. The user
-
defined string is
not decoded on the server. The user
-
defined string is only decoded in the
browser. The decoded string is not transmitted.
The string can only be removed by clearing the browser data. The
string is arbitrary and must not contain personal information.
</p>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment