Projects tagged ‘pci’

PCI utilities for many *nix systems and hopefully even Windows: lspci and setpci, for now.

coreinfo is a small informational payload for coreboot. Currently, it can display CPU information, PCI information, coreboot table information, and show an NVRAM dump.

In the Payment Card Industry (PCI), security is always a major concern. A lot of enterprise applications have application passwords hard-coded in configuration files, which are not allowed by the ... [More] Payment Card Industry Data Security Standard (PCI DSS). Smart Account Management (SAcct) is a light-weight Security Framework to ease your pain of removing the account passwords from application configuration files. The SAcct server reads in the account information from a secured soft token and acts as an account server. The SAcct client communicates with the SAcct Server over a secured channel to retrieve account passwords on behalf of the application on start-up. Problems and ChallengesTake a Spring application as an example, the following wiring file includes a database user name and a user password, To put the database user password into the configuration file is a serious security problem and it is not allowed by the Payment Card Industry Data Security Standard (PCI DSS). Some frameworks try to encrypt the passwords, but they still need to wire in the encryption password, which does not really solve the problem. We propose to store the accounts in a secured token file, which you can put into a USB drive or other secured devices, then the SAcct framework can retrieve them on behalf of the application during the application start-up phase. SAcct ArchitectureThe SAcct architecture is shown in the following diagram, The SAcct server is a standalone Java application and mainly consists of the following components: Session Manager: create a session key for each connection based on the Diffie-Hellman Key Exchange protocol. It also generates a session id and maintains the sessions in the cache. Account Manager: read account data from the account token file and service client account requests. Connector: read requests from the client and write the responses back to the client. Message encryption/decryption is handled on this layer. The SAcct client usually is one part of the business application. It derives the session key and stores the session information in a token. The SAcct client also includes a socket connector to communicate with the SAcct server. All request messages are encrypted except the session Id as shown in the system diagram. The communication flows are summarized as follows, handshake request: The client generates two big numbers, Cr as the private key, Cp as the public key, and initiates the connection by sending the public key Cp to the SAcct server. handshake response: Upon receiving the client request, the SAcct Server generates its own private key Sr and public key Sp. In the meanwhile, it derives a secret key as the session key based the client's public key Cp and its own keys. Then the SAcct server responds back to the client with its public key Sp and a random session id. account service request: The client derives the same secret key after received the server's public key Sp and starts to send a secured service request to the server using the session key. account service response: The SAcct server decrypts the request and replies back the encrypted service response with the session key. closeSession request: The client finishes its job and sends a closeSession request to the SAcct server. closeSession response: The SAcct server replies back and the client closes the socket connection. SAcct FeaturesSAcct is a Java application and suitable for Enterprise Java applications. SAcct features are highlighted as follows, Light-Weight Use Google Guice as the dependency injection framework for the SAcct Server Account information are encrypted and stored as a soft token on a carry on device Utility tools are provided to encrypt and decrypt the soft token Use the Diffie-Hellman key exchange protocol to derive the session key The communications between the SAcct Server and the SAcct Client are encrypted by the session key An One Time Password (OTP) is used to prevent session replay attack All encryptions use the Advanced Encryption Standard (AES) algorithm Spring support Many security utility classes SAcct ModulesSAcct consists of the following modules: SAcct Common: common and shared classes between the SAcct server and the SAcct client. SAcct Server: SAcct server is a standalone Java application. SAcct Client: SAcct client acts as a client stub communicate with the SAcct server. SAcct Spring: Utility classes for the Spring framework. Reference Project: will create a reference project to demonstrate how to use SAcct. Account UI: will add UI to manage account tokens. SAcct SolutionsWhat to know how SAcct solves the problems? Take a Spring application as an example. First, you need to download SAcct server, unpack it, go to the bin directory, and run ./sacct_serverThe SAcct server will read in the soft token and listen on socket port 9000 by default. The Account Provider is an abstraction of the SAcct client. In your Spring application, you can define the account provider bean as follows. The account factory bean is used to retrieve the actual account password information from the account provider. Optionally, you can provide the default/dummy password in the case that the SAcct is not available. Finally, the dataSource bean can be rewritten as For more details, please read SAcct 0.1.0 User Guide and the FAQs. Maven RepositoryThanks to Matt Senter, SAcct artfacts are in our Maven repositories now: SAcct Maven Release Repository SAcct Maven Snapshot Repository For how to use Maven with SAcct, please refer to the Maven guide in the user guide. SupportIf you have any problems, please post to our SAcct User Group, I will get back to you as quick as possible. If you are interested in contributing to SAcct, please read How to Contribute. NEWSJuly 9 2009, added SAcct Server Implementation Experience With Google Guice. July 8 2009, added SAcct 0.1.0 User Guide. July 7 2009, SAcct 0.1.0 is released, please check the release announcement. June 19 2009, SAcct became an open source project. NOTESAcct is one of the Open Source Open Mind Initiative projects. [Less]

lychee provide a driver and a library to help access hardware directly Project introduction: The lychee project aim to a useful tool to get the rich system hardware and firmware information ... [More] , include: PCI device view, read and write PCI device configuration space PCIe device view, read and write PCIe configuration space CMOS value read, write, backup SMBIOS table read, dump and interpret ACPI tables read, dump and interpret, DSDT table interpret to asl SPD table read dump and interpret I2C and SMBus device read, write IPMI console to communication to SP CPU instuction value read and write, like MSR TSC MTTR and CPUID LPC read and write SuperIO device control This tool can run at cross platform, include Windows 2000 Windows XP Windows Server 2003 x86, x64 Windows Vista x86, x64 Windows Server 2008 x86, x64 Linux & DOS support is only in roadmap, not exactly work now! all of other platform have not tested yet. If you have other platform need, or you have tested this software in other platform, you can write to freevanx (freevanx@gmail.com) to feed back. This tool don't support Windows 95, Windows 98 and Windows ME More detailhttp://code.google.com/p/lychee-prj/wiki/What_is_lychee_project [Less]

Ailipu Technology Co., Ltd is a high tech company specialize in security system products.

Try to maintain a RTL model with Giga PHY behavior and PCI behavior.

rockxie's code base

Open rtVision (Real-time visualization environment for image processing reconfigurable devices)Open rtVision is an open source tool developed using .Net framework. The application is an interface ... [More] between the module for the image acquisition from cameras and a coprocessing board connected with a computer using the PCI/PCIe bus. For more information about the system go to the detailed description. Software platformA simple and efficient interface is rather important for the development of complex systems. The presented work shows a software environment working as an interface between the image acquisition by the webcams or the scientific cameras and the co-processing board connected with the computer through the PCI/PCIe bus. The co-processing board has the role of extracting the visual primitives from the images: energy, orientation, phase, disparity and optical flow estimation. The computation is performed in real-time. The software obtains and post-processes the results, to be displayed and stored. Just the visualization in real-time of this huge amount of data from the board is a big challenge. It requires the use of different libraries and software packages for the optimization of the management and processing of the results such as OpenCV®, IPP® and OpenMP®. The system fulfills the most important requirements of the work involving co-processing boards: Capacity for the final verification of the results Friendly interfaces for the system configuration Display of a huge volume of data in real-time Fig. 1 The figure shows an example of use for the disparity computation of a well-known sequence in artificial vision, the Tsukuba sequence. ArchitectureThe environment is used in a specific architecture which includes: A stereo camera system. We have two different setups: A pair of USB webcams or a pair of high performance scientific cameras with Camera Link connection. We study also other interface connections such as FireWire, Ethernet... With the scientific cameras, we use a frame grabber The presented software is running in a computer with PCI/PCIe interfaces for the board connections The co-processing board. We developed the libraries for: The XircaV4 platform, developed by Seven Solutions. It includes four SSRAM (ZBT) memory banks of 2Mwords of 36 bits, 2 512 Mb DDR memory modules, and a 32MB flash memory module. Furthermore, it has a 10/100/1000Mbits Ethernet connection, a JTAG configuration interface and the PCIe 1x interface. The FPGA is a Virtex4 XCVFX100 – 10FFG1152. The RC2000 platform, developed by Celoxica® (then Agility®). It includes 6 ZBT memory banks of 1Mword of 36 bits, with a 16MB flash memory. In this case, the connection is PCI. Finally, the FPGA is a Xilinx Virtex-II XCV6000-6. Hardware layoutThe hardware co-design allows us to take advantage from the hardware processing such as the high paralellism, the low size and the low energy consumption ... But it also provides us the posibility of implementing complex algorithms easily and rapidly or to use the software as an interface with the visualization devices, or even, to validate and verify the hardware computation. With the presented tool we also developed two interface libraries for connecting the software application and the co-processing device, which are also documented. Software layoutThis work is focused on the software layout. It's the result of the need to joint the different tools used for the development of the image processing algorithms and to support to the high computing requirements for the post-processing and the visualization of the obtained results from the co-processing board. Fig. 2 The figure shows an example of the complete system working in real-time computing a road scene. With this aplication we concentrate the different tools in a platform which also integrates more functionalities. We also want to fullfil requirements such as a friendly user interface, usability, scalability, a platform optimized for image processing... The following videos show the software working with real road scenes in real-time. It is displayed the disparity and the optical flow results. Development TeamThe open-rtVision has been developed at the University of Granada (Dept. of Computer Architecture and Technology). The main developers are F. Barranco, M. Tomasi, M. Vanegas, S. Granados and J.Ralli. The research coordination was performed by E. Ros and J. Díaz. Now Open rtVision has been released as Open Source facilitated by the OSL “Oficina de Software Libre” through the advice of J.J. Merelo of the University of Granada. This means that any other development effort can be done by any other member or the research community. Currently, we are improving the project working on new functionalities for the software platform such as the automatic camera calibration, the connection with new interfaces (FireWire and Ethernet), the use of sockets... If you could help or you have doubts about how to use Open rtVision, send an email to Francisco Barranco or Eduardo Ros. AcknowledgmentThe development of the Open rtVision platform has been supported by EU project, DRIVSCO(IST-016276-2), the national project DINAM-VISION (DPI2007-61683) and the regional project of the Junta de Andalucía P06-TIC-02007. For usersOn the downloads section you can find tutorials, a video-tutorial, examples and the complete documented code. The software documentation can be generated using doxygen. [Less]

IntroductionSplunk Labs is a community-managed developer resource for using, programming, and extending Splunk Server. This site hosts SDKs that sit on top of Splunk Server's REST API, and sample ... [More] projects that use the SDKs to create applications and visualizations. All resources hosted on this site are supported by the community via the forums and email. What is Splunk?Splunk is a search engine for IT data. It's software that lets you search and analyze all the data your IT infrastructure generates from a single location in real time. We call this IT Search. No need for databases, connectors, custom parsers or proprietary consoles. Just your imagination and a web browser! Now you can troubleshoot IT problems and investigate security incidents in minutes, not hours or days. Monitor all your applications, servers and network devices from one place. Report on all your compliance controls in a fraction of the time. Available SDKsSplunk Server 4SDKs for version 4 have not been released yet. Splunk Server 3The following SDKs are available for download (versions 3.2-3.4): Language Notes Python Reference SDK (maintained by Splunk) .NET Microsoft .NET Java PHP Actionscript 3 Perl Javascript Getting Started Have a Splunk installation ready to use (both Free and Enterprise licenses support API access). If you are not familiar with Splunk, you can learn about and download it at www.splunk.com/product. Download one of the SDK packages listed above, depending on your language preference. Follow the sample code included in each download to get started. The Python SDK has the most complete walkthrough at PythonSdkTutorial Contributed ProjectsSee the complete list of projects Additional ResourcesHere are some additional resources that can help you get the most out of Splunk: Splunk Labs Forums Official Splunk Forums Splunk Developer Blog Splunk Developer's Guide Search language cheat sheet - search language cookbook Splunk search language reference - search language reference For all other comments or questions, contact splunk-labs@splunk.com. Interested contributors are encouraged to contact us! [Less]