From: Diyab <diyab@diyab.net>
To: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: glibc
Date: Fri, 28 Nov 2003 00:36:06 -0500 [thread overview]
Message-ID: <3FC6DEC6.7020501@diyab.net> (raw)
Is there any specific way to check for AT_SECURE functionality in glibc?
Timothy,
--
I put instant coffee in a microwave and almost went back in time.
-- Steven Wright
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2003-11-28 5:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 5:36 Diyab [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 22:03 glibc Siders, Keith
2001-08-15 21:37 glibc Siders, Keith
2001-08-15 21:31 glibc Siders, Keith
2001-08-15 21:38 ` glibc Ilya Volynets
[not found] <no.id>
2001-08-15 20:58 ` glibc Alan Cox
2001-08-15 20:58 ` glibc Alan Cox
2001-08-16 8:50 ` glibc Brian Murphy
2001-08-16 14:04 ` glibc Alan Cox
2001-08-16 14:04 ` glibc Alan Cox
2001-08-16 16:14 ` glibc Ralf Baechle
2001-08-16 19:09 ` glibc Martin Michlmayr
2001-08-16 20:05 ` glibc James Simmons
2001-08-16 20:10 ` glibc Soeren Laursen
2001-08-16 16:04 ` glibc H . J . Lu
2001-08-16 17:00 ` glibc Brian Murphy
2001-08-16 21:15 ` glibc H . J . Lu
2001-08-15 20:45 glibc Steven Liu
2001-08-15 20:45 ` glibc Steven Liu
2001-08-15 21:05 ` glibc Pete Popov
[not found] <20001122213444.3E1B037CA7@carmen.fc.hp.com>
2000-11-23 0:18 ` glibc Alan Modra
1999-10-20 15:53 Incorrect optimization on PowerPC due to volatile keyword (gcc-2.95.1 official) Franz Sirl
[not found] ` <Pine.LNX.4.10.9910201050310.9073-100000@darkmane.w-link.ne t>
1999-10-20 18:07 ` glibc Franz Sirl
1999-10-20 18:13 ` glibc Sean Chitwood
[not found] <Pine.LNX.4.10.9910111344060.1730-100000@darkmane.w-link.ne t>
1999-10-12 10:50 ` glibc Franz Sirl
1999-10-11 20:47 glibc Sean Chitwood
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=3FC6DEC6.7020501@diyab.net \
--to=diyab@diyab.net \
--cc=selinux@tycho.nsa.gov \
/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.