linux operating commands and unix operating commands

US Congress PCI hearings

03-31-2009

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

US Congress PCI hearings

What could be worse: a vague and hastily thrown together mashup of security protections masquerading as a security framework or standard, or having the government get into the act? Now you don't have to choose: you can have the worst of both worlds! Follow the US Congress hearings on PCI! Or, follow the commentary into the hearings on Twitter (which is fairly random and noisy, but probably makes just as much sense).

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Hardware

Could USB ever take over PCI

Internally speaking, for your motherboard bus. Would it be possible for a usb standard to be used in place of the PCI or PCIe bus that is now nearly standard on all PC's? If not, why wouldn't this work?

2. Slackware

converting mouse to pci

Need to free up a usb port for webcam. What does xorg.conf look like in order to work if I move mouse to PCI port via a converter plug?

3. Solaris

available PCI slots on v440

How do I find any available PCI slots on a v440? When I run prtconf, I get the following output? But I am not able to make out whether all the PCI slots are used. ================================= IO Devices ================================= Bus Freq Brd Type MHz Slot ...

4. Solaris

Pci Id

How do I get the PCI ID for my Realtek adapter? It's a Solaris x86 installation.

LEARN ABOUT HPUX

close_secdef

secdef(3)						     Library Functions Manual							 secdef(3)

NAME

       secdef: open_secdef(), close_secdef(), get_secdef_str(), get_secdef_int() - security defaults configuration file routines

SYNOPSIS

DESCRIPTION

       opens the security configuration file This function must be called prior to calling or

       closes the security configuration file.

       and return the value of the specified parameter defined in the security configuration file.  See the security(4) manpage.

       Programs using these routines must be compiled with

APPLICATION USAGE

       In  a multithreaded application, these interfaces are thread-safe, but not async-cancel-safe.  A cancellation point may occur when a thread
       is executing any of these interfaces.

RETURN VALUE

       returns a value of if the open completed successfully.  Otherwise, it returns and leaves unchanged from the call.  and return  the  follow-
       ing:

	      The value of the specified parameter was successfully returned.
	      The entry was not found, or the security configuration file was not opened.
	      The format of the entry was incorrect.

EXAMPLES

       This example obtains the "path" from the parameter.

FILES

       Security defaults configuration file.

SEE ALSO

       security(4).

																	 secdef(3)