Hi
user
Admin Login:
Username:
Password:
Name:
Building Persona: federated and privacy-sensitive identity for the Web
--client
lca
--show
lca2013
--room MCC1 1673 --force
Prev: 1 Why kernel space sucks
Next: (none, at end of list)
show more...
Author(s):
Francois Marier
Location
MCC1
Date
feb Fri 01
Days Raw Files
Start
14:15
First Raw Start
error-in-template
Duration
0:45:00
Offset
None
End
15:00
Last Raw End
Chapters
Total cuts_time
None min.
http://lca2013.linux.org.au/schedule/30049/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Building_Persona_federated_and_privacysensitive_identity_for_the_Web.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
Unknown
Yes
No
has someone authorised pubication
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
Identity systems on the Web are a bit of a mess. Surely in 2013, we would have something else than usernames and passwords for logging into websites. A solution that doesn't require trusting a central authority with a privacy policy that can change at a whim. It turns out that solving the general identity problem is very hard. Some of these solutions require complicated redirections, an overwhelming amount of jargon and lots of verbose XML. The technology has been around for a long time, but implementing it properly (and safely) is often incredibly difficult. It's a lot to ask of the millions of part-time developers out there that are building sites out of some quick HTML, a MySQL database and some PHP code samples. This talk will explore the challenges of the existing Web identity solutions and introduce the choices that we made during the development of Persona (formerly BrowserID), a new Open Source federated identity solution from Mozilla, designed and built to respect user privacy. It will cover: - a quick overview of existing identity systems on the Web - a discussion of the complexities and privacy-related concerns that existing identity solutions have - the cryptographic protocol behind Persona (including how crypto is used to provide both authentication and privacy, even from your identity provider) - the Persona federation approach: fully distributed with fallbacks - demos and actual code from sites that have implemented Persona - the basics of the Persona API so that attendees can go out and support this technology on their own sites without much trouble Identity is a very significant piece of Internet infrastructure and so it is critical that the solution that gets widely adopted be free-as-in-freedom, cross-browser, distributed and ruthlessly focused on making it easy for developers and end-users.
markdown
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review