Home
Morc .'s Library tagged → View Popular
Layer 8
"The meaning of metrics.
I started writing about metrics at the very beginning of this blog, and hadn’t really seen anything I could add to the ongoing blogo-discussion since then, but the planets aligned: I had a thought-provoking discussion with a super-sharp colleague, and it was followed by a Saturday in which I finally have a little time to write.
This provocateur kept referring to “security practitioners” as opposed to—well, everyone else in the security space, I suppose—and I began wondering what the cultural differences are between the two spheres. The implication is that “real practitioners” know what the real risks are, because they’re living them every day. (What is a practitioner, anyway? Let’s just say it’s someone who’s directly responsible for protecting an organization’s data, as opposed to someone who is developing problems or solutions for OTHER organizations’ data. You can argue with that definition if you like, but I’ll bet if you do, you’re not someone who meets the first description. wink) But I don’t find that necessarily to be the case. One of the great frustrations that I see with vendors, researchers, analysts and regulators is that they don’t believe most practitioners actually understand the risk landscape. The only group that arguably does is the one that’s getting attacked the most—the military—and they can’t talk about it. The only other group that kinda understands is the financial institutions, and they won’t talk about it even if they get caught with their cyber-pants down. I remember hearing a great talk by Aaron Turner that was eye-opening in its level of disclosure about things that were really happening, and that was only because of a confidentiality agreement; you’d never get that level of discourse in the public blogosphere.
The reason I think that most practitioners don’t appreciate the security risks in the same way that other security professionals do is this: [donning my asbestos undies] for the most part, security breaches don’t have observable impact in
A Modest Proposal - Wikipedia, the free encyclopedia
"A Modest Proposal
From Wikipedia, the free encyclopedia
Jump to: navigation, search
A Modest Proposal: For Preventing the Children of Poor People in Ireland from Being a Burden to Their Parents or Country, and for Making Them Beneficial to the Publick, commonly referred to as A Modest Proposal, is a Juvenalian satirical essay written and published anonymously by Jonathan Swift in 1729. Swift appears to suggest in his essay that the impoverished Irish might ease their economic troubles by selling children as food for rich gentlemen and ladies. By doing this he mocks the authority of the British officials. This is when Britain had taken over Ireland and put heavy restrictions on their trade, stifling their economy. The essay has been noted by historians as being the first documented satirical essay."
LibriVox
"LibriVox: free audiobooks
LibriVox volunteers record chapters of books in the public domain and release the audio files back onto the net. Our goal is to make all public domain books available as free audio books. "
Martin Bailey Interview|Outdoor Photo Gear
"Martin Bailey Interview
MBP_Martin_20090621-90
Martin Bailey is a British nature photographer living in Japan. If that doesn’t get you interested in this interview, nothing will! Martin is also a member of the Outdoor Photo Gear Review Board. This article contains excerpts from Martin’s interview by Scott Bourne.
1 – Scott: Please tell me how and when you got into photography.
[Martin Bailey] My induction into photography was a long process. My earliest photographic experience was with a Polaroid camera that Dad bought when I was around 7 or 8 years old. It disappeared from our house pretty quickly though when he realized how expensive the film was. I played with my friend’s Dad’s camera sometimes, and he let me shoot the odd frame, which was a real kick. I then had a number of basically plastic toy cameras over the years, which I enjoyed shooting with, but we didn’t have a lot of money, and so the developing costs held me back a lot. In my teens I remember asking my Mum if I could paint our bathroom black and find some way of sealing up the windows when necessary so that I could make my own darkroom. You can imagine that this conversation didn’t progress very far.
I started to really become interested in photography in my early twenties, when I started to go hiking in the hills of Derbyshire and the Lake District in England, and shot a lot of landscape images. I had a car by this time, and was earning enough to have film developed, but I was still using a plastic pretty much disposable camera, that I just kept in my jacket pocket looking for the right moment.
Then I moved to Japan when I was twenty four. With the beautiful scenery and a whole new eye opening culture to shoot, I got my first SLR, a Canon EOS 630, and a few lenses. Knowing that I’d gotten interested in photography, my brother sent me books on photographic techniques and composition, that I devoured. I never asked why he’d been so perceptive to do that. He’s not a photographer himself, but I guess he liked the odd 5×7 I started sending back
Nikon glass: custom sttings
"Wednesday, March 4, 2009
The KISS principle
Setting up a Nikon DSLR and using it
There are a number of small articles on my blog relating to my experiences and personal preferences with setting up and using the D300. Some of the info is old by now (in digital time) and because they are also separate pieces of my “thoughts” at various times I decided to put together a larger piece so as to bring everything up to date and into perspective.
Before I start I need to point out a few things about my subject matter and workflow. These days my subjects are mostly reportage and wildlife – two different themes requiring different equipment, styles and settings. I also have changed my workflow, since I no longer use Nikon Transfer, View and Capture NX and now prefer the speed and convenience of Adobe Lightroom. Plus I should mention that I only shoot in RAW mode and never have shot in JPG. All the above greatly influence the way I choose to setup my camera so it’s important that you have this in mind when reading my personal choices below.
Banks
You can save different banks of settings for the “Shooting” and “Custom Setting” menus for different shooting situations. In the “Shooting menu” I used to have 4 different combinations and just one in the “Custom Settings menu”. I don’t use banks anymore since the “My Menu” menu can provide all the power I need in one easy to access menu.
Playback menu
I don’t use the playback menu while shooting but did use it when I first got the camera where I unchecked the Focus point and the Data options in the Display mode. To keep from coming back to this menu, I have placed the Image review option in the “My Menu” for easy access in case I ever need it. Sometimes when shooting amongst crowds such as in weddings, parties, street photography etc I may want to switch off the image review and use the Play button instead when I need to do any checking of the histogram or the image.
Shooting menu
I also don’t use this menu while shooting since most of the important stuff that’s included are a
Caution: Contents Under Pressure. | Ask Metafilter
"Caution: Contents Under Pressure.
November 10, 2009 6:32 PM RSS feed for this thread Subscribe
I'm being overloaded with information in my academic and digital lives - how do I separate the signal from the noise?
There are two areas in which I'm completely overwhelmed at any given moment.
1) My academic work. I'm a teaching fellow who's working on his Master's thesis. I get great ideas for both my classroom teaching and my academic research. Over and over. I'll jot these down, and then they'll disappear forever. I'll go to a conference, and get a million great ideas - and then lose them all, or be so overwhelmed with something else that I never get the chance to implement them. I default back to standard, which drives me up the wall.
2) My digital life. I try to stay on the forefront be reading blogs on a bunch of different topics. I have various recipes stared in Google Reader, MeFi favorites that I've been meaning to go back and read for ages, and various things like this.
How do I process all this information, and distill it down to something useful? I get so excited and enthusiastic about new techniques, research, and news, but then I fall apart because I can't apply it to anything due to time constraints, or even a good system to process it all.
Thanks in advance, HiveMind.
posted by SNWidget to education (11 comments total) 24 users marked this as a favorite
I've found that using a web todo list like toodledo has helped me greatly. It allows me to file stuff away for "the future" as well as things that need to be completed sooner.
You can do classic "todo items" as well as attach a note to an item.
I use it to keep track of my needs to get done today and this month items, as well as my long term storage for "wouldn't it be great to do this some day" items.
They have folders, due dates (optional) and priorities. I got through periodically and cull things that are old, or update things that should be updated / split / joined /etc..
I've found it's much more productive than my older method of Palm
VRT: How do I become a Ninja?
"How
do I become a Ninja?
Earlier this week, we posted this blog
item:
Ask the
VRT a question
. We had a few people write in and ask us questions about
Snort, Snort rules and the other obvious Snort related questions. Then, we got
something interesting...
mish asks "How do I become a Ninja?"
(His
question was a little longer than that, and we of course assumed that he meant
"Vulnerability Research Ninja")
We threw this around between various VRT
people and it apparently hit the hot button on our Senior Director of
Vulnerability Research, Matt Watchinski. Here is his manifesto in reply to
mish's question:
1. You need to fix your thought process. Most people see
computers and programs as tools that have functions that complete the tasks they
need accomplished on a day to day basis. If you see everything around you as
something that needs to work to do your job then you'll never see it for what it
is, something to break and use to your advantage. The best way I've heard this
summed up is "Be Evil".
2. Reading books without ever turning that
information into practical knowledge is not going to make a ninja. Only
experience will make a ninja, sitting in a library never resulted in anything
useful.
Once you have the thought process down, technical skills now come
into play.
3. The main thing with technical skills is you don't need to
be a master of any of them, you need to be a master of recalling where the
information you need is located.
4. Get yourself an old ass RedHat box
without PAX/AppArmor/etc make sure stack randomization is off, then go download
all the
ABO's
from Gera
. Start working on the simple buffer overflow examples. All the
answers are on google if you get stuck (but don't cheat, it's not worth
it).
5. After that, you now hate GDB. Time to move on to a real debugger.
Get yourself a Windows XP box (no service pack), or a Windows 2000 box with any
service pack (VMWare is great, just saying). Start working through the
AWBO e
Selected Tags
Sponsored Links
Top Contributors
Groups interested in no_tag
-
Web 2.0 Tools
Items: 10 | Visits: 892
Created by: Claire Miller
-
Erotica
Items: 40 | Visits: 3367
Created by: Ainis
-
Digital Citizenship/Cyberbullying Video Clips
Items: 27 | Visits: 2047
Created by: Anne Bubnic
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo