Re: [TLS] Fwd: I-D Action: draft-lemon-tls-blocking-alert-00.txt

[Hubert Kario <[e-mail]>]

On Monday 06 June 2016 13:21:12 Ted Lemon wrote:
> I've posted a new document to the datatracker that adds some TLS alert
> codes that can be sent to indicate that a particular TLS request has
> been blocked by the network.   This attempts to address the problem
> of notifying the user of what went wrong when a site is blocked,
> without creating a channel that can be used by a hostile network to
> attack a user.

why separate malicious_site and policy_violation? Why not provide just a 
single administratively_prohibited? I don't see a difference to the 
user, in both cases the site will remain unavailable when retrying 
connection and in both cases if the user thinks it's a mistake he or she 
will need to contact the network administrator.

I don't understand the account_attention_* alerts. What account does the 
user need to log in? In what scenarios would they be used? How is it 
different from the captive_portal?
-- 
Regards,
Hubert Kario
Senior Quality Engineer, QE BaseOS Security team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic