Hi
user
Admin Login:
Username:
Password:
Name:
Playing to lose: making sensible security decisions by assuming the worst
--client
kiwipycon
--show
kiwipycon2015
--room Track_2 10295 --force
Next: 1 Cython: get the benefits of C without leaving Python
show more...
Marks
Author(s):
Tom Eastman
Location
Track 2
Date
sep Sun 06
Days Raw Files
Start
16:00
First Raw Start
error-in-template
Duration
00:30:00
Offset
None
End
16:30
Last Raw End
Chapters
Total cuts_time
None min.
https://kiwi.pycon.org/schedule/presentation/95/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Playing_to_lose_making_sensible_security_decisions_by_assuming_the_worst.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
The unfortunate truth about networked applications is that an attacker only needs to know one thing you didn't know to get past your defences. You need to know everything, they don't. The odds aren't in your favour. You're eventually going to get hacked. That's the bad news. But if you stop thinking about a security compromise as "that thing you close your eyes and hope never happens", and instead start thinking about it as an inevitability, then you can start making better security decisions. "If they compromise my web servers, how do I protect my application servers?" "If they break my application server code, how can I prevent them from gaining a foothold on my infrastructure?" "If they poison my web-site with cross-site scripting, how do I find out before my users get hurt?" In short: "If I'm going to get hacked, how do I make it hurt less?" This is a talk about defence in depth. Building a secure system isn't about luck, it’s about planning.
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