Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
How To (And Not To) Make the Online Trust Honor Roll
Newest First  |  Oldest First  |  Threaded View
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
7/31/2017 | 2:46:22 PM
Re: impersonization, forgery, and fakes
100% behind you here, mack.  There is room for the Public Key Model to improve, of course.  Read an interesting paper "Soundness in the Public-Key Model" by Silvio Micali and Leonid Reyzin.  From the ABSTRACT:

The public-key model for interactive proofs has proved to be quite effective in improving protocol efficiency (see Canetti, Goldreich, Goldwasser, Micali, STOC 2001). We argue, however, that its soundness notion is more subtle and complex than in the classical model, and that it should be better understood to avoid designing erroneous protocols. Specifically, for the public-key model, we:

 
  • identify four meaningful notions of soundness;
  • prove that, under minimal complexity assumptions, these four notions are distinct;
  • identify the exact soundness notions satisfied by prior interactive protocols; and
  • identify the round complexity of some of the new notions.
macker490
100%
0%
macker490,
User Rank: Ninja
7/18/2017 | 8:21:33 AM
impersonization, forgery, and fakes
what do the sites do to prevent the "Bad Guys" from impersonating them -- or transmitting fakes and forgeries?

sites focus tons of effort on identifying their customers.    but what do customers do in order to authenticate sites?

we rely on a large list of x.509 certificates -- published by our web browsers  -- and most of us -- have no clue what's in that list.

For Critical Sites Only:    we all need to COUNTERSIGN trusted certificates using our own PGP/GnuPG key

in the Public Key Model this step is required in order to validate a key.   Keys must be validated before a trust level can be assigned.

give this some thought.   "They" want to authenticate you -- but -- you need to authenticate them -- and the model we use today -- fails.   That's an F


Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-15682
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.
CVE-2017-15683
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to create a site with specially crafted XML that allows the retrieval of OS files out-of-band.
CVE-2017-15684
PUBLISHED: 2020-11-27
Crafter CMS Crafter Studio 3.0.1 has a directory traversal vulnerability which allows unauthenticated attackers to view files from the operating system.
CVE-2017-15685
PUBLISHED: 2020-11-27
Crafter CMS Crafter Studio 3.0.1 is affected by: XML External Entity (XXE). An unauthenticated attacker is able to create a site with specially crafted XML that allows the retrieval of OS files out-of-band.
CVE-2017-15686
PUBLISHED: 2020-11-27
Crafter CMS Crafter Studio 3.0.1 is affected by: Cross Site Scripting (XSS), which allows remote attackers to steal users’ cookies.