Last Four FaiF Episodes

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2011/11/11/more-faif.html

Those of you that follow my blog have probably wondered we’re I’ve
been. Quite frankly, there is just so much work going on at Conservancy
that I have almost had no time to do anything but Conservancy work, eat
and sleep. My output on this blog and
on identi.ca surely shows that.

The one thing that I’ve kept up with
is the oggcast, Free as in
Freedom
that I co-host
with Karen Sandler, and which is
produced by Dan Lynch.

Since I last made a blog post here, Karen, Dan and I released four
oggcasts. I’ll discuss them here in reverse chronological order:

In Episode 0x1C, which was released today, we published Karen’s
interview with Adam Dingle
of Yorba. IMO (which is undoubtedly
biased), this episode is an important one since it relates to the
issues of non-profit organizations in our community who waiting in the
501(c)(3) application queue. This is a detailed and specific follow-up
to the issues that Karen and I discussed
on FaiF’s Episode
0x13
.

In Episode 0x1B, Karen and I discuss in some detail about the work that
we’ve been up to. Both Karen and I are full-time Executive Directors,
and the amount of work that job takes always seems insurmountable.
Although, after we recorded the episode, I somewhat embarrassingly
remembered
the Bush/Kerry
debate where George W. Bush kept saying his job as president is hard
work
. It’s certainly annoying when a chief executive goes on
and on about how hard his job is, so I apologize if I did a little too
much of that in Episode 0x1B.

In Episode 0x1A,
Karen and I discussed in detail Steve Jobs’ death and the various news
coverage about it. The subject is a bit old news now that I write this,
but I’m glad we did that episode, since it gave me an opportunity to say
everything I wanted to stay about Steve Jobs’ life and death.

In Episode 0x19, we
played Karen’s interview
with Jos Poortvliet,
discussed the identi.ca upgrade, and Karen discussed GNOME 3.2.

My plan is to at least keep the FaiF oggcast going, and I’m
even bugging
Fontana that he and I should start an oggcast too
. Beyond that, I
can’t necessarily commit to any other activities outside of that (and my
job at Conservancy and volunteer duties at FSF). BTW, I recently
attended a few conferences (both LinxCon Europe and the Summer of Code
Mentor Summit). At both of them, multiple folks asked me why I haven’t
been blogging more. I appreciate people’s interest in what I’m writing,
but at the moment, my day-job at Conservancy and volunteer work at FSF
has had to take absolute priority.

Based on the ebb and flow (yes, that’s the first time I’ve actually
used that phrase on my ebb.org blog 🙂 of the Free Software community
that I’ve gotten used to over the last decade and a half, I usually find
that things slow down in mid-December until mid-January. Since
Conservancy’s work is based on the needs of its Free Software projects,
I’ll likely be able to return a “normal” 50 hour work week
(instead of the 60-70 I’ve been doing lately) in December. Thus, I’ll
probably try to write some queued blog posts then to slowly push out
over the few months that follow.

Finally, I want to mention
that Conservancy
has an donation appeal
up on its website. I hope you’ll give
generously to support Conservancy’s work. On that, I’ll just briefly
mention my “hard work” again, to assure you
that donors to
Conservancy
definitely get their money’s worth when I’m on the job.
Since I’m on the topic of that, I also thank everyone who
has donated to FSF
and Conservancy over the
years. I’ve been fortunate to have worked full-time at both
organizations, and I appreciate the community that has supported all
that work over the years.

Last Four FaiF Episodes

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2011/11/11/more-faif.html

Those of you that follow my blog have probably wondered we’re I’ve
been. Quite frankly, there is just so much work going on at Conservancy
that I have almost had no time to do anything but Conservancy work, eat
and sleep. My output on this blog and
on identi.ca surely shows that.

The one thing that I’ve kept up with
is the oggcast, Free as in
Freedom
that I co-host
with Karen Sandler, and which is
produced by Dan Lynch.

Since I last made a blog post here, Karen, Dan and I released four
oggcasts. I’ll discuss them here in reverse chronological order:

In Episode 0x1C, which was released today, we published Karen’s
interview with Adam Dingle
of Yorba. IMO (which is undoubtedly
biased), this episode is an important one since it relates to the
issues of non-profit organizations in our community who waiting in the
501(c)(3) application queue. This is a detailed and specific follow-up
to the issues that Karen and I discussed
on FaiF’s Episode
0x13
.

In Episode 0x1B, Karen and I discuss in some detail about the work that
we’ve been up to. Both Karen and I are full-time Executive Directors,
and the amount of work that job takes always seems insurmountable.
Although, after we recorded the episode, I somewhat embarrassingly
remembered
the Bush/Kerry
debate where George W. Bush kept saying his job as president is hard
work
. It’s certainly annoying when a chief executive goes on
and on about how hard his job is, so I apologize if I did a little too
much of that in Episode 0x1B.

In Episode 0x1A,
Karen and I discussed in detail Steve Jobs’ death and the various news
coverage about it. The subject is a bit old news now that I write this,
but I’m glad we did that episode, since it gave me an opportunity to say
everything I wanted to stay about Steve Jobs’ life and death.

In Episode 0x19, we
played Karen’s interview
with Jos Poortvliet,
discussed the identi.ca upgrade, and Karen discussed GNOME 3.2.

My plan is to at least keep the FaiF oggcast going, and I’m
even bugging
Fontana that he and I should start an oggcast too
. Beyond that, I
can’t necessarily commit to any other activities outside of that (and my
job at Conservancy and volunteer duties at FSF). BTW, I recently
attended a few conferences (both LinxCon Europe and the Summer of Code
Mentor Summit). At both of them, multiple folks asked me why I haven’t
been blogging more. I appreciate people’s interest in what I’m writing,
but at the moment, my day-job at Conservancy and volunteer work at FSF
has had to take absolute priority.

Based on the ebb and flow (yes, that’s the first time I’ve actually
used that phrase on my ebb.org blog 🙂 of the Free Software community
that I’ve gotten used to over the last decade and a half, I usually find
that things slow down in mid-December until mid-January. Since
Conservancy’s work is based on the needs of its Free Software projects,
I’ll likely be able to return a “normal” 50 hour work week
(instead of the 60-70 I’ve been doing lately) in December. Thus, I’ll
probably try to write some queued blog posts then to slowly push out
over the few months that follow.

Finally, I want to mention
that Conservancy
has an donation appeal
up on its website. I hope you’ll give
generously to support Conservancy’s work. On that, I’ll just briefly
mention my “hard work” again, to assure you
that donors to
Conservancy
definitely get their money’s worth when I’m on the job.
Since I’m on the topic of that, I also thank everyone who
has donated to FSF
and Conservancy over the
years. I’ve been fortunate to have worked full-time at both
organizations, and I appreciate the community that has supported all
that work over the years.

Last Four FaiF Episodes

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2011/11/11/more-faif.html

Those of you that follow my blog have probably wondered we’re I’ve
been. Quite frankly, there is just so much work going on at Conservancy
that I have almost had no time to do anything but Conservancy work, eat
and sleep. My output on this blog and
on identi.ca surely shows that.

The one thing that I’ve kept up with
is the oggcast, Free as in
Freedom
that I co-host
with Karen Sandler, and which is
produced by Dan Lynch.

Since I last made a blog post here, Karen, Dan and I released four
oggcasts. I’ll discuss them here in reverse chronological order:

In Episode 0x1C, which was released today, we published Karen’s
interview with Adam Dingle
of Yorba. IMO (which is undoubtedly
biased), this episode is an important one since it relates to the
issues of non-profit organizations in our community who waiting in the
501(c)(3) application queue. This is a detailed and specific follow-up
to the issues that Karen and I discussed
on FaiF’s Episode
0x13
.

In Episode 0x1B, Karen and I discuss in some detail about the work that
we’ve been up to. Both Karen and I are full-time Executive Directors,
and the amount of work that job takes always seems insurmountable.
Although, after we recorded the episode, I somewhat embarrassingly
remembered
the Bush/Kerry
debate where George W. Bush kept saying his job as president is hard
work
. It’s certainly annoying when a chief executive goes on
and on about how hard his job is, so I apologize if I did a little too
much of that in Episode 0x1B.

In Episode 0x1A,
Karen and I discussed in detail Steve Jobs’ death and the various news
coverage about it. The subject is a bit old news now that I write this,
but I’m glad we did that episode, since it gave me an opportunity to say
everything I wanted to stay about Steve Jobs’ life and death.

In Episode 0x19, we
played Karen’s interview
with Jos Poortvliet,
discussed the identi.ca upgrade, and Karen discussed GNOME 3.2.

My plan is to at least keep the FaiF oggcast going, and I’m
even bugging
Fontana that he and I should start an oggcast too
. Beyond that, I
can’t necessarily commit to any other activities outside of that (and my
job at Conservancy and volunteer duties at FSF). BTW, I recently
attended a few conferences (both LinxCon Europe and the Summer of Code
Mentor Summit). At both of them, multiple folks asked me why I haven’t
been blogging more. I appreciate people’s interest in what I’m writing,
but at the moment, my day-job at Conservancy and volunteer work at FSF
has had to take absolute priority.

Based on the ebb and flow (yes, that’s the first time I’ve actually
used that phrase on my ebb.org blog 🙂 of the Free Software community
that I’ve gotten used to over the last decade and a half, I usually find
that things slow down in mid-December until mid-January. Since
Conservancy’s work is based on the needs of its Free Software projects,
I’ll likely be able to return a “normal” 50 hour work week
(instead of the 60-70 I’ve been doing lately) in December. Thus, I’ll
probably try to write some queued blog posts then to slowly push out
over the few months that follow.

Finally, I want to mention
that Conservancy
has an donation appeal
up on its website. I hope you’ll give
generously to support Conservancy’s work. On that, I’ll just briefly
mention my “hard work” again, to assure you
that donors to
Conservancy
definitely get their money’s worth when I’m on the job.
Since I’m on the topic of that, I also thank everyone who
has donated to FSF
and Conservancy over the
years. I’ve been fortunate to have worked full-time at both
organizations, and I appreciate the community that has supported all
that work over the years.

Last Four FaiF Episodes

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2011/11/11/more-faif.html

Those of you that follow my blog have probably wondered we’re I’ve
been. Quite frankly, there is just so much work going on at Conservancy
that I have almost had no time to do anything but Conservancy work, eat
and sleep. My output on this blog and
on identi.ca surely shows that.

The one thing that I’ve kept up with
is the oggcast, Free as in
Freedom
that I co-host
with Karen Sandler, and which is
produced by Dan Lynch.

Since I last made a blog post here, Karen, Dan and I released four
oggcasts. I’ll discuss them here in reverse chronological order:

In Episode 0x1C, which was released today, we published Karen’s
interview with Adam Dingle
of Yorba. IMO (which is undoubtedly
biased), this episode is an important one since it relates to the
issues of non-profit organizations in our community who waiting in the
501(c)(3) application queue. This is a detailed and specific follow-up
to the issues that Karen and I discussed
on FaiF’s Episode
0x13
.

In Episode 0x1B, Karen and I discuss in some detail about the work that
we’ve been up to. Both Karen and I are full-time Executive Directors,
and the amount of work that job takes always seems insurmountable.
Although, after we recorded the episode, I somewhat embarrassingly
remembered
the Bush/Kerry
debate where George W. Bush kept saying his job as president is hard
work
. It’s certainly annoying when a chief executive goes on
and on about how hard his job is, so I apologize if I did a little too
much of that in Episode 0x1B.

In Episode 0x1A,
Karen and I discussed in detail Steve Jobs’ death and the various news
coverage about it. The subject is a bit old news now that I write this,
but I’m glad we did that episode, since it gave me an opportunity to say
everything I wanted to stay about Steve Jobs’ life and death.

In Episode 0x19, we
played Karen’s interview
with Jos Poortvliet,
discussed the identi.ca upgrade, and Karen discussed GNOME 3.2.

My plan is to at least keep the FaiF oggcast going, and I’m
even bugging
Fontana that he and I should start an oggcast too
. Beyond that, I
can’t necessarily commit to any other activities outside of that (and my
job at Conservancy and volunteer duties at FSF). BTW, I recently
attended a few conferences (both LinxCon Europe and the Summer of Code
Mentor Summit). At both of them, multiple folks asked me why I haven’t
been blogging more. I appreciate people’s interest in what I’m writing,
but at the moment, my day-job at Conservancy and volunteer work at FSF
has had to take absolute priority.

Based on the ebb and flow (yes, that’s the first time I’ve actually
used that phrase on my ebb.org blog 🙂 of the Free Software community
that I’ve gotten used to over the last decade and a half, I usually find
that things slow down in mid-December until mid-January. Since
Conservancy’s work is based on the needs of its Free Software projects,
I’ll likely be able to return a “normal” 50 hour work week
(instead of the 60-70 I’ve been doing lately) in December. Thus, I’ll
probably try to write some queued blog posts then to slowly push out
over the few months that follow.

Finally, I want to mention
that Conservancy
has an donation appeal
up on its website. I hope you’ll give
generously to support Conservancy’s work. On that, I’ll just briefly
mention my “hard work” again, to assure you
that donors to
Conservancy
definitely get their money’s worth when I’m on the job.
Since I’m on the topic of that, I also thank everyone who
has donated to FSF
and Conservancy over the
years. I’ve been fortunate to have worked full-time at both
organizations, and I appreciate the community that has supported all
that work over the years.

Last Four FaiF Episodes

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2011/11/11/more-faif.html

Those of you that follow my blog have probably wondered we’re I’ve
been. Quite frankly, there is just so much work going on at Conservancy
that I have almost had no time to do anything but Conservancy work, eat
and sleep. My output on this blog and
on identi.ca surely shows that.

The one thing that I’ve kept up with
is the oggcast, Free as in
Freedom
that I co-host
with Karen Sandler, and which is
produced by Dan Lynch.

Since I last made a blog post here, Karen, Dan and I released four
oggcasts. I’ll discuss them here in reverse chronological order:

In Episode 0x1C, which was released today, we published Karen’s
interview with Adam Dingle
of Yorba. IMO (which is undoubtedly
biased), this episode is an important one since it relates to the
issues of non-profit organizations in our community who waiting in the
501(c)(3) application queue. This is a detailed and specific follow-up
to the issues that Karen and I discussed
on FaiF’s Episode
0x13
.

In Episode 0x1B, Karen and I discuss in some detail about the work that
we’ve been up to. Both Karen and I are full-time Executive Directors,
and the amount of work that job takes always seems insurmountable.
Although, after we recorded the episode, I somewhat embarrassingly
remembered
the Bush/Kerry
debate where George W. Bush kept saying his job as president is hard
work
. It’s certainly annoying when a chief executive goes on
and on about how hard his job is, so I apologize if I did a little too
much of that in Episode 0x1B.

In Episode 0x1A,
Karen and I discussed in detail Steve Jobs’ death and the various news
coverage about it. The subject is a bit old news now that I write this,
but I’m glad we did that episode, since it gave me an opportunity to say
everything I wanted to stay about Steve Jobs’ life and death.

In Episode 0x19, we
played Karen’s interview
with Jos Poortvliet,
discussed the identi.ca upgrade, and Karen discussed GNOME 3.2.

My plan is to at least keep the FaiF oggcast going, and I’m
even bugging
Fontana that he and I should start an oggcast too
. Beyond that, I
can’t necessarily commit to any other activities outside of that (and my
job at Conservancy and volunteer duties at FSF). BTW, I recently
attended a few conferences (both LinxCon Europe and the Summer of Code
Mentor Summit). At both of them, multiple folks asked me why I haven’t
been blogging more. I appreciate people’s interest in what I’m writing,
but at the moment, my day-job at Conservancy and volunteer work at FSF
has had to take absolute priority.

Based on the ebb and flow (yes, that’s the first time I’ve actually
used that phrase on my ebb.org blog 🙂 of the Free Software community
that I’ve gotten used to over the last decade and a half, I usually find
that things slow down in mid-December until mid-January. Since
Conservancy’s work is based on the needs of its Free Software projects,
I’ll likely be able to return a “normal” 50 hour work week
(instead of the 60-70 I’ve been doing lately) in December. Thus, I’ll
probably try to write some queued blog posts then to slowly push out
over the few months that follow.

Finally, I want to mention
that Conservancy
has an donation appeal
up on its website. I hope you’ll give
generously to support Conservancy’s work. On that, I’ll just briefly
mention my “hard work” again, to assure you
that donors to
Conservancy
definitely get their money’s worth when I’m on the job.
Since I’m on the topic of that, I also thank everyone who
has donated to FSF
and Conservancy over the
years. I’ve been fortunate to have worked full-time at both
organizations, and I appreciate the community that has supported all
that work over the years.

Kernel Hackers Panel

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/linuxcon-kernel-panel.html

At LinuxCon Europe/ELCE I had the chance to moderate the kernel hackers
panel with Linus Torvalds, Alan Cox, Paul McKenney and Thomas Gleixner on
stage
. I like to believe it went quite well, but check it out for yourself, as
a video recording is now available online:

For me personally I think the most notable topic covered was Control Groups,
and the clarification that they are something that is needed even though their
implementation right now is in many ways less than perfect. But in the end there is no
reasonable way around it, and much like SMP, technology that complicates things
substantially but is ultimately unavoidable.

Other videos from ELCE are online now, too.

libabc

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/libabc.html

At the Kernel Summit in Prague last week Kay Sievers and I lead a session on
developing shared userspace libraries, for kernel hackers. More and more
userspace interfaces of the kernel (for example many which deal with storage,
audio, resource management, security, file systems or a number of other
subsystems) nowadays rely on a dedicated userspace component. As people who
work primarily in the plumbing layer of the Linux OS we noticed over and over
again that these libraries written by people who usually are at home on the
kernel side of things make the same mistakes repeatedly, thus making life for
the users of the libraries unnecessarily difficult. In our session we tried to
point out a number of these things, and in particular places where the usual
kernel hacking style translates badly into userspace shared library hacking.
Our hope is that maybe a few kernel developers have a look at our list of
recommendations and consider the points we are raising.

To make things easy we have put together an example skeleton library we
dubbed libabc, whose README
file includes all our points in terse form. It’s available on kernel.org:

The git repository and the README.

This list of recommendations draws inspiration from David Zeuthen’s and
Ulrich Drepper’s well known papers on the topic of writing shared libraries. In
the README linked above we try to distill this wealth of information into a
terse list of recommendations, with a couple of additions and with a strict
focus on a kernel hacker background.

Please have a look, and even if you are not a kernel hacker there might be
something useful to know in it, especially if you work on the lower layers of
our stack.

If you have any questions or additions, just ping us, or comment below!

Prague

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/linuxcon-europe.html

If you make it to Prague the coming week for the LinuxCon/ELCE/GStreamer/Kernel Summit/… superconference, make sure not to miss:

All of that at the Clarion Hotel. See you in Prague!

Plumbers Wishlist, The Second Edition

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/plumbers-wishlist-2.html

Two weeks ago we published a Plumber’s
Wishlist for Linux
. So far, this has already created lively discussions in
the community (as reported on LWN among others), and patches for a few of the
items listed have already been posted (thanks a lot to those who worked on
this, your contributions are much appreciated!).

We
have now prepared a second version of the wish list.
It includes a number
of additions (tmpfs quota! hostname change notifications! and more!) and
updates to the previous items, including links to patches, and references to
other interesting material.

We hope to update this wishlist from time, so stay tuned!

And now, go and read the new wishlist!

Google doesn’t like my name

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/google-doesnt-like-my-name.html

Nice one, Google suspended my Google+ account because I created it under,
well, my name, which is “Lennart Poettering”, and Google+ thinks that wasn’t my
name, even though it says so in my passport, and almost every document I own
and I was never aware I had any other name. This is ricidulous. Google, give me
my name back! This is a really uncool move.

Part 2: On Passwords, Password Policies, and Teaching

Post Syndicated from David original http://devilsadvocatesecurity.blogspot.com/2011/10/part-2-on-passwords-password-policies.html

I noted in yesterday’s post that I used the answers to drive a conversation with a student employee, but didn’t provide details. I was asked what the assignment was, and thought that it might be of interest.

I provided the initial question, and my response about what drives institutional policy – essentially what I summarized here. The assignment was:

Explain how you would answer this question for a user, and for IT management, and how your policy might differ for each of these environments:

  • A large multinational corporation
  • A commercial website like Amazon, or a cloud service like Dropbox or Picasa
  • A small company or non-profit

This sort of thought exercise is one that I feel is crucial for those who are learning information security, and is similar to questions I ask my employees when we discuss why our policies are what they are.

A Big Loss

Post Syndicated from Lennart Poettering original https://0pointer.net/blog/projects/a-big-loss.html

Google
announced today that they’ll be shutting down Google Code Search in
January
. I am quite sure that this would be a massive loss for the Free
Software community. The ability to learn from other people’s code is a key
idea of Free Software. There’s simply no better way to do that than with a
source code search engine. The day Google Code Search will be shut down will
be a sad day for the Free Software community.

Of course, there are a couple of alternatives around, but they all have one
thing in common: they, uh, don’t even remotely compare to the completeness,
performance and simplicity of the Google Code Search interface, and have
serious usability issues. (For example: koders.com is really really slow, and
splits up identifiers you search for at underscores, which kinda makes it
useless for looking for almost any kind of code.)

I think it must be of genuine interest to the Free Software community to
have a capable replacement for Google Code Search, for the day it is turned
off. In fact, it probably should be something the various foundations which
promote Free Software should be looking into, like the FSF or the Linux
Foundation. There are very few better ways to get Free Software into the heads
and minds of engineers than by examples — examples consisting of real life
code they can find with a source code search engine. I believe a source code
search engine is probably among the best vehicles to promote Free Software
towards engineers. In particular if it itself was Free Software (in contrast to
Google Code Search).

Ideally, all software available on web sites like SourceForge, Freshmeat, or
github should be indexed. But there’s also a chance for distributions here:
indexing the sources of all packages a distribution like Debian or Fedora
include would be a great tool for developers. In fact, a distribution offering
this functionality might benefit from such functionality, as it attracts
developer interest in the distribution.

It’s sad that Google Code Search will be gone soon. But maybe there’s
something positive in the bad news here, and a chance to create something better,
more comprehensive, that is free, and promotes our ideals better than Google
ever could. Maybe there’s a chance here for the Open Source foundations, for
the distributions and for the communities to create a better replacement!

On Passwords and Password Expiration

Post Syndicated from David original http://devilsadvocatesecurity.blogspot.com/2011/10/on-passwords-and-password-expiration.html

One of the things that I believe is an important part of my job is to answer user questions in a way that educates them about the topic they ask about in addition to providing the answer. At times, this can be frustrating, but it also challenges me to think about why I’m providing the answer that I do. It also means that I have to review the choices I, and my organization make about policy, process, and the reasons for both.

I recently exchanged email with one of our users who questioned our password policy which requires periodic changes of passwords. The user contended that periodic password changes encourages poor password choice, that users who are forced to choose new passwords (even on a relatively infrequent basis) will choose poor passwords, and that in the end, that password changes serve no purpose.

In my institution’s case, there are a number of reasons why password changes make sense, and I believe that these are a reasonable match for most companies, colleges, and other organizations – but not necessarily for your Amazon account, or your banking password. It is critical to understand the difference between a daily use password for institutional access that provides access to things like VPN access, email, licensed software, and the rest of the keys to the kingdom, and a single use password that accesses a service or site. Thinking about your password policy in the context of institutional risk while remaining aware of how your users will react is critical.

The reasons that help drive password change for my institution, in no particular order are:

  • Password changes help to prevent attackers who have breached accounts, but who have not used them, or who are quietly using them, from having continued access.
  • Similarly, they can help prevent shared passwords from being useful for long term access.
  • They can help prevent users from using the same password in multiple locations by driving changes that don’t match the previously set passwords elsewhere.
  • They can help prevent brute forcing, although this is less common in environments where there are back-off algorithms in place. In many institutions, that central monitoring may not exist, or may not be easy to implement.
  • Password changes continue to be recommended by most best practice documents (including PCI-DSS and others). Including password expiration in your password policy can be an element in proving due diligence as an organization.

When you read the list from a user perspective, it is difficult to see a compelling reason for them to change their passwords. There isn’t a big, disaster level threat that is immediately obvious, and the “what’s in it for me” is hard to communicate. When you read it from an organizational perspective, you will likely see a set of reasons that when taken as a whole mean that a reasonable password expiration timeframe is useful at an organizational level. Here’s why:

The environment in which most of us work now has two major external threats to passwords: malware and phishing. With malware targeting browsers and browser plugins, and institutional policies that accept that users will visit at least common sites like CNN, ESPN, and other staples of our online lives, we have to acknowledge that malware compromises that gather our user’s passwords are likely.

Similarly, despite attempts we make at user education, phishing continues to seduce a portion of our user population into clicking that tempting link, or responding to the IT department that needs to know their password to ensure that their email isn’t turned off. Again, we know that passwords will be exposed.

Bulk compromises of passwords are likely to involve captured hashes, which most organizations have spent years designing infrastructure to avoid as tools like Rainbow Tables and faster cracking hardware became available. Thus, we worry more about what access to our networks, and what individual accounts, or small groups of compromised accounts can do. In the event of a large-scale breach of central authentication, the organization will require a password change from every user, typically with immediate expiration of all passwords.

In this environment, we will require our users to change their passwords when their account is compromised, but will we know to require that? We know that advanced persistent threats exist, and that some attackers are patient and will wait, gathering information and not abusing the accounts they collect. We can continue to fight those threats with periodic password changes for the accounts that provide access to our institutions.

It would, of course, be preferable to use biometrics, or tokens, or some other two factor authentication system. It is also expensive, and difficult to adapt into a diverse environment where credentials are used across a variety of systems that are glued (or duct taped, bubble gummed, and bailing wired) together in a variety of ways. For now, passwords – or preferably passphrases – remain the way to make these heterogeneous systems authenticate and interoperate.

In the end, I learned a lot from my exchange with the user. Over the next few months, I’ll be adding additional information to our awareness program reminding users that password changes that change from “Password1” to “Password2” aren’t serving a real use, we’ll add additional information about tools like Password Safe to our posters and awareness materials, and I’ll be working with our identity and access management staff to see if we can leverage their tools to prevent similar poor password practices. In addition, I’ve been using it as a learning opportunity for my staff, and as a challenge for my student employee.

I’m aware that I won’t win with every user – I’ll still have the gentleman who resets his password once a day for as many days as our password history and minimum password age will allow so he can get back to his favorite password. I’ll still have the user who changes their password to “Password1!” and claims that yes, they have used a capital and a number and a symbol, and that thus they have met the requirements for a strong password. But I also know that our population continues to grow more security aware, and that many of our users do get the point.

If you’re interested in this topic, you may enjoy this Microsoft research about users, security advice, and why they choose to ignore it, and NIST’s password guidance provides a well reasoned explanation of everything from password choice to mnemonics and password guessing.

How to handle "I want to be a security guy" with an easy assignment

Post Syndicated from David original http://devilsadvocatesecurity.blogspot.com/2011/10/how-to-handle-i-want-to-be-security-guy.html

As the manager of a security team I’m often approached by technologists who are interested in information security. Their reasons range from a long term interest in the subject to those who simply want a change of pace, or think that the grass may just be greener in infosec.

Over the years I’ve developed a simple list of things that I tell people who express an interest:

  1. Get a copy of Hacking Exposed. Anything recent will do, and a good alternative is Counterhack Reloaded.
  2. Skim the book, and read anything that catches your eye. Don’t try to read it cover to cover, unless you really find that you want to.
  3. Come back and talk to me once you’ve done that, and we’ll talk about what you found interesting.

It’s a very simple process – but I’ve found it immensely valuable. Those who are really interested, and who will put the time into the effort will buy the book, and will come back with questions and comments. A certain percentage will get the book and will realize that information security isn’t really what they want to do, or they will realize that they need or want to know more before they tackle a career in security. A final group are interested, but not enough to take the step to follow up.

Once you have an interested candidate, the conversation or conversations that you can have next are far more interesting. Hopefully, you’ve read the book yourself, as you’ll be answering questions, and often providing references to deeper resources on the topics that interest them. Favorite resources for follow-up activities include:

  • OWASP – particularly WebGoat and Multilldae
  • Investigation of vulnerability scanners like Nikto and Nessus and
  • Exploration of tools like Metasploit and the BeEF browser exploitation framework using DVL or a similar vulnerable OS
  • SANS courses like SANS 401 and 501

A whole range of options exists once you start to have the conversation – but you’re certain you’re having the conversation with someone who is interested enough to follow up, and who has helped you identify what they’ll have some passion for.

The collective thoughts of the interwebz