Hi
user
Admin Login:
Username:
Password:
Name:
Playing to lose: making sensible security decisions by assuming the worst
--client
lca
--show
lca2016
--room r4mix 10708 --force
Next: 12 Preventing Cat-astrophes with GNU MediaGoblin
show more...
Marks
Author(s):
Tom Eastman
Location
D4.303 Costa Theatre
Date
feb Thu 04
Days Raw Files
Start
16:35
First Raw Start
16:34
Duration
0:45:00
Offset
0:00:02
End
17:20
Last Raw End
17:19
Chapters
00:00
Total cuts_time
37 min.
https://linux.conf.au/schedule/30232/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
host
archive
tweet
mp4
svg
png
assets
release.pdf
Playing_to_lose_making_sensible_security_decisions_by_assuming_the_worst_2.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 defenses. 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 defense in depth. Building a secure system isn’t about luck, it’s about planning.
Comment:
production notes
2016-02-04/16_34_58.dv
Apply:
16:35:17 - 17:13:05 ( 00:37:48 )
S:
16:34:58 -
E:
17:18:12
D:
00:43:14
(
Start:
19.0) (
End:
2287.0)
show more...
vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-04/16_34_58.dv :start-time=019.0 --audio-desync=0
Raw File
Cut List
16:34:58
seconds: 19.0
Wall: 16:35:17
Duration
00:43:14
17:18:12
seconds: 2287.0
Wall: 17:13:05
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2016-02-04/17_18_10.dv
Apply:
17:18:10 - 17:19:19 ( 00:01:09 )
S:
17:18:10 -
E:
17:19:19
D:
00:01:09
show more...
vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-04/17_18_10.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
17:18:10
seconds: 0.0
Wall: 17:18:10
Duration
00:01:09
17:19:19
seconds: 0.0
Wall: 17:18:10
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2016-02-04/16_34_58.dv
2016-02-04/17_18_10.dv
Veyepar
Video Eyeball Processor and Review
