What do hackers need to consider about what they will leave

    behind when they die?

  1. case studies
    1. Joel "Espy" Klecker
      1. died at 21
        1. of muscular dystrophy
        2. http://www.infodrom.org/Debian/espy.html
        3. July 11th, 2000
        4. no-one online knew he suffered from the disease
      2. Debian developer
        1. maintained glibc
          1. no uploads for 4 months after death, then:
            1. > * Might aswell change the maintainer too
            2. > (So long Joel, you are missed)
        2. work on powerpc port
          1. who took over, and when?
        3. Debian 2.2 dedicated to him
          1. http://www.debian.org/News/2000/20000815
      3. www.espy.org
        1. still running in 2006
          1. probably a 2.4 kernel, according to nmap
            1. gotta be security issues there
          2. apache 1.3.26
            1. security issues here too?
          3. debian woody
            1. so unmaintained, probably
          4. 200+ day uptime, no load
        2. parents probably keeping it running, online

            I think I remember them saying they wanted to keep his machines running in tribute to him.

        3. probably no active users, no significant resources of any kind
        4. probably no admin aside from reboots
        5. someone is paying for and/or adminning DNS
          1. whois still in Joel's name
          2. paid thru 2008
          3. last change jun 2006
          4. as of 2008, is paid thru 2017, by a relative
        6. was taken offline by beginning of 2007
      4. irc client
        1. espy was online on irc for several years after he died
          1. his client would reconnect occasionally and spook me
            1. ghost in the machine
          2. kinda weird having his nick still around
          3. kinda a good reminder too
        2. last time seen on irc?
      5. conclusions
        1. Joel must have known he had limited time.
        2. If he made arrangements, he made them quietly.
        3. His contributions to software were picked up and continued.
        4. His server has held up remarkably well.
        5. But could easily be insecure and open to abuse.
        6. He probably didn't anticipate the irc client thing. Who would?
    2. Manuel Estrada Sainz (ranty)
      1. died in a car crash
        1. With fellow Debian guy Andrés García (ErConde)
        2. http://www.infodrom.org/Debian/ranty.html
        3. http://lists.debian.org/debian-devel-spanish/2004/05/msg00045.html
        4. http://lists.debian.org/debian-devel-spanish/2004/05/msg00056.html
      2. Debian developer
        1. VisualOS
          1. no longer in debian
        2. lirc, mailleds
          1. adopted quickly
        3. "Ranty is no more with us :-( please adopt his pkgs."
          1. http://lists.debian.org/debian-devel-spanish/2004/05/msg00057.html
      3. kernel hacker
        1. orinoco USB driver
          1. still used
        2. firmware loading support
          1. in wide use
    3. Christopher Matthew Rutter (cmr)
      1. died in accident
        1. March 21, 2001
        2. 19 years old!
        3. http://www.infodrom.org/Debian/cmr.html
      2. Debian developer
        1. worked on arm port
        2. buildd.debian.org
          1. "I dedicate this centralized database and web interface in memory of Chris Rutter. He was killed in a tragic car accident on March 1, 2001. Chris originally developed this web interface for Aleph One, ARM Linux consultants. -- rmurray"
    4. Fabrizio Polacco
      1. died after long illness
        1. March 28th, 2001
      2. Debian developer
        1. man-db changelog
          1. "New maintainer. Fabrizio, may the road rise up to meet you."
    5. Martin Butterweck
      1. died of leukemia
        1. July 21st, 2002
      2. Debian developer
        1. had recently joined project
        2. New-Maintainer application
          1. https://nm.debian.org/nmstatus.php?email=martin_butterweck%40gmx.de
    6. Jens Schmalzing
      1. died in a fall
        1. July 30th, 2005
      2. Debian developer
        1. powerpc porter
        2. kernel team member
          1. 2.6.12-2 release dedicated to him
        3. maintained other packages
        4. d-i contributer
    7. Leonard Zubkoff
      1. died in helicopter crash
        1. August 28, 2002
        2. http://www.puffin.com/puffin/lnz/Leonard.htm
        3. http://lwn.net/Articles/9163/
        4. http://www.dreamsongs.com/Leonard.html
        5. http://www.electricpenguin.com/filking/articles/zubkoff.html
      2. kernel developer
        1. scsi drivers
          1. mylex and flashpoint
          2. dac960
            1. still used, though the hardware grows dated
      3. www.dandelion.com
        1. server down since 2004 according to wayback
        2. dns admined by someone @puffin, probably a friend
        3. 2008: domain sold to company
      4. www.consonance.org
        1. was hosted by leonard
        2. now seems to have different hosting
      5. donations
        1. estate donated 1.2 million to the EFF in 2004
          1. http://www.eff.org/about/20040218_eff_pr.php
    8. Rob Levin
      1. died after a bicycle accident
        1. September 16th, 2006
        2. http://laughingsquid.com/2006/09/16/freenode-founder-rob-levin-aka-lilo-has-passed-away/
        3. http://www.chatmag.com/news/091606_rob_levin.html
        4. http://linux.slashdot.org/article.pl?sid=06/09/16/2152243&from=rss
      2. founder of freenode
        1. network still going, other admins
      3. www.bloggage.org
        1. parked by 2009
      4. www.spinhome.org
        1. expired and parked by September 2008
      5. irc client

          <+christel> it has also been asked why lilos client is still connected <+christel> i am sure you will all agree that at this point in time, we feel uncomfortable killing his client and find the mere idea rather morbid

        1. client disconnected later (time unknown)
      6. mourning
        1. IRC channels set up to mourn him.
        2. Memorial page: http://lilo.freenode.net/
    9. Thiemo Seufer
      1. died in a car accident
        1. December 26th, 2008
        2. http://lwn.net/Articles/313092/
      2. Debian developer
        1. d-i mips porter
        2. d-i build system developer
        3. maintained genisovh
      3. mips binutils and kernel hacker
      4. qemu mips emulation
    10. Frans Pop (fjp)
      1. died 20 August 2010
        1. details not public
      2. Debian developer
        1. debmirror
          1. https://alioth.debian.org/projects/debmirror/
        2. debtree
          1. http://collab-maint.alioth.debian.org/debtree/
        3. both packages taken over by Sep 6th
          1. changelogs: "Frans, we'll miss you."
      3. d-i team member
        1. led d-i team between joeyh and otavio
        2. remained somewhat active in d-i
      4. blog
        1. http://alioth.debian.org/~fjp/log/index.html
      5. obitiary
        1. master.debian.org:/home/debian/git/obituary.git
    11. Adrian von Bidder (avbidder, cmot)
      1. died 17 April 2011
        1. heart attack
      2. Debian developer
      3. founder of debian.ch organization
      4. blog
        1. http://blog.fortytwo.ch/
        2. final post made by wife: "Sadly, I have to make an end to this blog. Adrian - my husband -
        3. died on april 17th of a heart attack."
      5. obitiary
        1. master.debian.org:/home/debian/git/obituary.git
      6. tombstone
        1. https://lists.debian.ch/pipermail/community/2011/000675.html
    12. Aaron Swartz (aaronsw)
      1. died 11 Jan 2013
      2. left online will
        1. http://www.aaronsw.com/2002/continuity
        2. how well was it carried out? check later
      3. memorial
        1. http://www.rememberaaronsw.com/
      4. ghost
        1. http://www.newyorker.com/online/blogs/newsdesk/2013/05/strongbox-and-aaron-swartz.html
        2. Nine days after Aaron’s death, his familiar Skype avatar popped up on my
        3. computer screen. Somewhere, somebody—probably a family member—had booted up his
        4. computer. I fought the irrational urge to click on the icon and resume our
        5. conversation. Then he vanished from my screen again.
  2. server issues
    1. keep server up or take it down?
      1. how long should it stay up?
      2. how should its configuration be changed while it's still up?
        1. lock user account, obviously..
    2. who maintains it while it's up?
      1. are they an executor of the will, or do they report to the executor?
    3. how is it paid for?
    4. what should happen to email?
      1. autoresponse: "He's dead, Jim"
      2. drop it
      3. bounce it
  3. data retention
    1. what should be done with data, backups, etc
      1. what to destroy?
      2. what to discard?
      3. what needs to be preserved?
      4. how to preserve it?
      5. will future historians want any of it?
      6. what data needs to be put in the hands of its users?
      7. is there data that should be kept private for some time period?
        1. like 20 years, or 50?
    2. what about gpg keys and passphrases?
      1. if lost, that encrypted data is gone, forever
  4. copyright
    1. who should inherit copyrights
      1. heirs?
      2. FSF?
      3. individual projects?
    2. will licenses of software age well?
      1. will they stand up over time?
        1. what if GPL is broken later?
          1. are works licensed under "gpl 2 or above"?
        2. what if workarounds for the intent of the license are developed?
          1. eg, web services..
        3. other licenses ditto
        4. what about unlicensed code/data?
          1. should a general blanket license statement be made to cover it?
      2. should their term be shortened?

          If a hacker belives that copyright term is too long, should he arrange for his works to enter the public domain when he dies?

  5. traditional will
    1. who inherits what property
    2. any donations to charities?
      1. FSF
      2. EFF
      3. SPI
      4. etc
  6. passwords
    1. http://news.com.com/Taking+passwords+to+the+grave/2100-1025_3-6118314.html
    2. http://www.guardian.co.uk/technology/2009/jun/30/data-protection-internet
  7. other resources
    1. Various "email from the grave" services are being developed.
    2. Legacy Locker
    3. Away From keyboard http://www.archive.org/details/awayfromkeyboard
  8. links
    1. http://www.npr.org/templates/story/story.php?storyId=104024294
    2. http://euroquis.nl/bobulate/?p=1116