Kernel-hardening archive mirror
 help / color / mirror / Atom feed
From: jordan@damngood.tech
To: "kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>
Subject: I'm Jordan; New Kernel Developer Here!
Date: Sun, 21 Nov 2021 00:42:43 +0000	[thread overview]
Message-ID: <fXA60ALu2hdsrGAhW_ikHp7JHeP58swPN4_-uXH-V0JkJhcKVNGAtCvqCqhNJf_MEv9HHeBS3NfBgJyvD3IV_8mmANPQRDG0BT9NfIw8fEw=@damngood.tech> (raw)

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

Hi, I'm Jordan. I'm interested in working on security hardening in Linux!

The docs said to introduce myself, so here it goes!

I'm a developer with about 10 years experience. I currently freelance in full stack, but my roots go back to an apprenticeship at OSDL. I've been doing a lot of full stack / Python work lately, so I may be a little rusty with kernel development but I'm nowhere near a noob.

I ran into another kernel developer recently at a Linux tech talk. I was told that while kerndev isn't "sexy," it's necessary and greatly desired. So I'm coming back to where the need is.

How's that for an intro? Anything else you want to know about me? I'm looking forward to meeting some of you!

Also, what are good first steps?

P.S. I did try to register for the upstream mailing list at http://vger.kernel.org/vger-lists.html#linux-hardening, but I got a long email that began with "this is not a valid command." Not sure how to register.

[-- Attachment #2: Type: text/html, Size: 1200 bytes --]

                 reply	other threads:[~2021-11-21 10:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='fXA60ALu2hdsrGAhW_ikHp7JHeP58swPN4_-uXH-V0JkJhcKVNGAtCvqCqhNJf_MEv9HHeBS3NfBgJyvD3IV_8mmANPQRDG0BT9NfIw8fEw=@damngood.tech' \
    --to=jordan@damngood.tech \
    --cc=kernel-hardening@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).