From: hotjobs <hotjobs@secureallinc.com>
To: netdev@oss.sgi.com, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Linux TCP/IP Stack Developer
Date: Fri, 10 Oct 2003 15:55:09 -0700 [thread overview]
Message-ID: <1065826508.1612.27.camel@localhost.localdomain> (raw)
CA-Staff/Senior Engineer: Linux TCP/IP Stack Development
SecureAll Inc., headquartered in the Silicon Valley, California, is a
well-funded start-up in the Enterprise Information Security domain.
It is well recognized that enterprises are on the average 6 months
behind on applying security patches. During this period, despite
employing firewalls and intrusion detection systems, enterprises
are vulnerable to exploits leveraging the un-patched weaknesses.
It is also acknowledged that patch management is an imperfect science
and does not take away the risk of applying patches without adequate
testing. SecureAll offers a solution that is truly radical and solves
the above problems in an elegant fashion. The foundation of the company
is based on a patented breakthrough technology that takes network-based
enterprise security to the next level.
We are currently looking to fill one full-time regular positions in our
San Jose, CA facility requiring extensive experience with TCP/IP
protocol stack development.
Staff/Senior-Engineer: TCP/IP Protocol Stack Development
* 5-10 years of experience in the design, implementation, and
ongoing development of TCP/IP protocol stack. At least 1 year
recent development experience with Linux TCP/IP protocol stack.
* Extensive Kernel Software development and debugging experience
preferably in Linux environment.
* Good Understanding of memory management, SMP, clustering issues is a
plus.
* Experience with the hardening of kernel and various protocol stacks
for security is a plus.
* Experience with design and architecture of mid- to large-sized
software projects.
To Apply for this job, please send a word/text resume to
hotjobs@secureallinc.com with the position title in the subject line.
next reply other threads:[~2003-10-10 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 22:55 hotjobs [this message]
2003-10-11 17:58 ` Linux TCP/IP Stack Developer David S. Miller
2003-10-11 17:58 ` David S. Miller
2003-10-11 20:25 ` Job Announcements (was Linux TCP/IP Stack Developer) Stephen Satchell
2003-10-11 20:35 ` David S. Miller
2003-10-11 22:12 ` jdow
2003-10-11 22:11 ` David S. Miller
2003-10-11 21:29 ` Willy TARREAU
2003-10-11 22:16 ` Stephen Satchell
2003-10-11 23:39 ` Mark Mielke
2003-10-12 11:03 ` Jamie Lokier
2003-10-12 14:59 ` Stephen Satchell
2003-10-13 1:47 ` Adam Sulmicki
2003-10-13 1:58 ` Adam Sulmicki
2003-10-14 9:23 ` Jamie Lokier
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=1065826508.1612.27.camel@localhost.localdomain \
--to=hotjobs@secureallinc.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.