Hi
user
Admin Login:
Username:
Password:
Name:
Enforcement of a system-wide crypto policy
--client
debian
--show
debconf15
--room Heidelberg 10090 --force
Next: 1 Philosophy of Free Software
show more...
Marks
Author(s):
Nikos Mavrogiannopoulos
Location
Heidelberg
Date
aug Sun 16
Days Raw Files
Start
15:00
First Raw Start
error-in-template
Duration
00:20:00
Offset
None
End
15:20
Last Raw End
Chapters
Total cuts_time
None min.
https://summit.debconf.org/debconf15/meeting/252/enforcement-of-a-system-wide-crypto-policies/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
public
mp4
svg
png
assets
release.pdf
Enforcement_of_a_systemwide_crypto_policy.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:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
Currently each and every shipped application in distributions enforces its own policy on the allowed cryptographic algorithms/protocols. While for some this is a desirable property, for most unmanaged applications like wget, curl, and similar, it prevents enforcing a consistent security level. The purpose of this talk is to describe the approach we've taken in Fedora to counter the issue, and enforce a system-wide policies, discuss the current outcome, lessons learned, and invite Debian maintainers to participate.
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