ÿØÿà JFIF    ÿÛ „ ( %!1!%*+...983,7(-.- etc/pki/ca-trust/README000064400000000246152343353310010530 0ustar00This directory /etc/pki/ca-trust is used by a system of consolidated CA certificates. Please refer to the update-ca-trust(8) manual page for additional information. usr/lib64/python2.7/Tools/README000064400000003471152344012700012030 0ustar00This directory contains a number of Python programs that are useful while building or extending Python. audiopy Audiopy is a program to control the Solaris audio device, allowing you to choose both the input and output devices, and to set the output volume, that can be run either as a command-line script, or as a Tkinter application. bgen Generate complete extension modules from a description. Still under development! WARNING: bgen has been removed in 3.0. compiler Tools used to maintain the compiler package in the standard library. faqwiz FAQ Wizard. See http://www.python.org/cgi-bin/faqw.py for a live example. freeze Create a stand-alone executable from a Python program. gdb Python code to be run inside gdb, to make it easier to debug Python itself (by David Malcolm). i18n Tools for internationalization. pygettext.py parses Python source code and generates .pot files, and msgfmt.py generates a binary message catalog from a catalog in text format. pynche A Tkinter-based color editor. scripts A number of useful single-file programs, e.g. tabnanny.py by Tim Peters, which checks for inconsistent mixing of tabs and spaces, and 2to3, which converts Python 2 code to Python 3 code. unicode Tools used to generate unicode database files for Python 2.0 (by Fredrik Lundh). versioncheck A tool to automate checking whether you have the latest version of a package (by Jack Jansen). webchecker A link checker for web sites. world Script to take a list of Internet addresses and print out where in the world those addresses originate from, based on the top-level domain country code found in the address. A generic benchmark suite is maintained separately at https://github.com/python/performance etc/fonts/conf.d/README000064400000001722152344140430010501 0ustar00conf.d/README Each file in this directory is a fontconfig configuration file. Fontconfig scans this directory, loading all files of the form [0-9][0-9]*.conf. These files are normally installed in /usr/share/fontconfig/conf.avail and then symlinked here, allowing them to be easily installed and then enabled/disabled by adjusting the symlinks. The files are loaded in numeric order, the structure of the configuration has led to the following conventions in usage: Files begining with: Contain: 00 through 09 Font directories 10 through 19 system rendering defaults (AA, etc) 20 through 29 font rendering options 30 through 39 family substitution 40 through 49 generic identification, map family->generic 50 through 59 alternate config file loading 60 through 69 generic aliases, map generic->family 70 through 79 select font (adjust which fonts are available) 80 through 89 match target="scan" (modify scanned patterns) 90 through 99 font synthesis lib64/python3.8/distutils/README000064400000000362152344556050012154 0ustar00This directory contains the Distutils package. There's a full documentation available at: http://docs.python.org/distutils/ The Distutils-SIG web page is also a good starting point: http://www.python.org/sigs/distutils-sig/ $Id$ usr/lib/kbd/unimaps/README000064400000000211152344606210011214 0ustar00The correspondences given in iso0[1-9].uni are according to The Unicode Standard, Version 1.0, Vol. 1. The remaining ones are phantasy. lib64/python3.6/distutils/README000064400000000447152345135530012153 0ustar00This directory contains the Distutils package. There's a full documentation available at: http://docs.python.org/distutils/ The Distutils-SIG web page is also a good starting point: http://www.python.org/sigs/distutils-sig/ WARNING : Distutils must remain compatible with 2.3 $Id$ lib64/python2.7/distutils/README000064400000000447152345535100012150 0ustar00This directory contains the Distutils package. There's a full documentation available at: http://docs.python.org/distutils/ The Distutils-SIG web page is also a good starting point: http://www.python.org/sigs/distutils-sig/ WARNING : Distutils must remain compatible with 2.3 $Id$ etc/pki/ca-trust/extracted/java/README000064400000001326152345557620013450 0ustar00This directory /etc/pki/ca-trust/extracted/java/ contains CA certificate bundle files which are automatically created based on the information found in the /usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories. All files are in the java keystore file format. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. lib/dracut/modules.d/98ecryptfs/README000064400000004447152345571670013416 0ustar00# Directions for creating the encrypted key that will be used to mount an # eCryptfs filesystem # Create the eCryptfs key (encrypted key type) # # The encrypted key type supports two formats: the 'default' format allows # to generate a random symmetric key of the length specified, the 'ecryptfs' # format generates an authentication token for the eCryptfs filesystem, # which contains a randomly generated key. Two requirements for the latter # format is that the key description must contain exactly 16 hexadecimal # characters and that the encrypted key length must be equal to 64. $ keyctl add encrypted 1000100010001000 "new ecryptfs trusted:kmk-trusted 64" @u 782117972 # Save the encrypted key $ su -c 'keyctl pipe `keyctl search @u encrypted 1000100010001000` > /etc/keys/ecryptfs-trusted.blob' # The eCryptfs key path name can be set in one of the following ways (specified in # the order in which the variable is overwritten): 1) use the default value: -------------------------------------------------------------------------- ECRYPTFSKEY="/etc/keys/ecryptfs-trusted.blob" -------------------------------------------------------------------------- 2) create the configuration file '/etc/sysconfig/ecryptfs' and set the ECRYPTFSKEY variable; 3) specify the eCryptfs key path name in the 'ecryptfskey=' parameter of the kernel command line. # The configuration file '/etc/sysconfig/ecryptfs' is also used to specify # more options for mounting the eCryptfs filesystem: ECRYPTFSSRCDIR: existent directory in the lower root filesystem; ECRYPTFSDSTDIR: mount point directory for the eCryptfs filesystem (the directory must be created in the root filesystem before rebooting the platform); ECRYPTFS_EXTRA_MOUNT_OPTS: extra mount options for the eCryptfs filesystem (the 'ecryptfs_sig' option is automatically added by the dracut script). # Example of the configuration file: ----------- '/etc/sysconfig/ecryptfs' (with default values) ----------- ECRYPTFS_KEY="/etc/keys/ecryptfs-trusted.blob" ECRYPTFSSRCDIR="/secret" ECRYPTFSDSTDIR="${ECRYPTFSSRCDIR}" ECRYPTFS_EXTRA_MOUNT_OPTS="" ----------------------------------------------------------------------- # If the variable ECRYPTFSDSTDIR is not specified in the configuration file, # its value will be equal to that of ECRYPTFSSRCDIR. lib64/python2.7/Demo/threads/README000064400000000670152345730630012445 0ustar00This directory contains some demonstrations of the thread module. These are mostly "proof of concept" type applications: Generator.py Generator class implemented with threads. sync.py Condition variables primitives by Tim Peters. telnet.py Version of ../sockets/telnet.py using threads. Coroutine.py Coroutines using threads, by Tim Peters (22 May 94) fcmp.py Example of above, by Tim squasher.py Another example of above, also by Tim lib64/python2.7/Demo/README000064400000003640152345757040011017 0ustar00This directory contains various demonstrations of what you can do with Python. They were all written by me except where explicitly stated otherwise -- in general, demos contributed by others ends up in the ../Contrib directory, unless I think they're of utmost general importance (like Matt Conway's Tk demos). A fair number of utilities that are useful when while developing Python code can be found in the ../Tools directory -- some of these can also be considered good examples of how to write Python code. Finally, in order to save disk space and net bandwidth, not all subdirectories listed here are distributed. They are listed just in case I change my mind about them. cgi CGI examples (see also ../Tools/faqwiz/.) classes Some examples of how to use classes. comparisons A set of responses to a really old language-comparison challenge. curses A set of curses demos. embed An example of embedding Python in another application (see also pysvr). imputil Demonstration subclasses of imputil.Importer. md5test Test program for the optional md5 module. metaclasses The code from the 1.5 metaclasses paper on the web. parser Example using the parser module. pdist Old, unfinished code messing with CVS, RCS and remote files. pysvr An example of embedding Python in a threaded application. rpc A set of classes for building clients and servers for Sun RPC. scripts Some useful Python scripts that I put in my bin directory. No optional built-in modules needed. sockets Examples for the new built-in module 'socket'. threads Demos that use the 'thread' module. (Currently these only run on SGIs, but this may change in the future.) tix Demos using the Tix widget set addition to Tkinter. tkinter Demos using the Tk interface (including Matt Conway's excellent set of demos). xml Some XML demos. zlib Some demos for the zlib module (see also the standard library module gzip.py). etc/pki/ca-trust/extracted/edk2/README000064400000001066152346133540013345 0ustar00This directory /etc/pki/ca-trust/extracted/edk2/ contains a CA certificate bundle file which is automatically created based on the information found in the /usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories. The file is in the EDK2 (EFI Development Kit II) file format. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. usr/lib/dracut/modules.d/10i18n/README000064400000010504152346204260013103 0ustar00dracut i18n module ------------------ INDEX 0. Introduction 1. Hostonly vs Generic 2. Configuration 2.1. Variables 2.2. Setting up mappings 2.3. Additional settings 3. Kernel parameters ~ 0. Introduction i18n module provides internationalization for initramfs at runtime. It is intended to be generic across different GNU/Linux distributions. i18n and keyboard settings are stored in different files among distributions. To deal with it avoiding hardcoding those differences in the installation script we handle it by mappings between variables used by dracut and the ones in the system. Package maintainer is expected to create those for his/her distribution and it's appreciated to share it with us, so we can include it in source package. 1. Hostonly vs Generic If you invoke dracut with '-H' option, i18n module install script will gather variables values from your configuration files using mappings provided in "/etc/dracut.conf.d/.conf". Those variables will be put in "etc/vconsole.conf" and "etc/locale.conf" files inside initramfs image. Next it will install only declared font, keymaps and so. When building generic image (dracut without '-H' option), install script copies all content of directories: consolefonts, consoletrans, unimaps and keymaps to image. Take into account that's about 4 MiB. 2. Configuration 2.1. Variables The following variables are used by i18n install script and at initramfs runtime: KEYMAP - keyboard translation table loaded by loadkeys KEYTABLE - base name for keyboard translation table; if UNICODE is true, Unicode version will be loaded. Overrides KEYMAP. EXT_KEYMAPS - list of extra keymaps to bo loaded (sep. by space) UNICODE - boolean, indicating UTF-8 mode FONT - console font FONT_MAP - see description of '-m' parameter in setfont manual FONT_UNIMAP - see description of '-u' parameter in setfont manual The following are appended to EXT_KEYMAPS only during build time: UNIKEYMAP GRP_TOGGLE They were used in 10redhat-i18n module, but not sure of its purpose. I'm leaving it in case... The following are taken from the environment: LANG LC_ALL If UNICODE variable is not provided, script indicates if UTF-8 should be used on the basis of LANG value (if it ends with ".utf8" or similar). 2.2. Setting up mappings Mappings between variables listed in 2.1. and the ones spread around your system are set up in /etc/dracut.conf.d/.conf. You need to assign mappings to i18n_vars. Here's an example: i18n_vars="/etc/conf.d/keymaps:KEYMAP,EXTENDED_KEYMAPS-EXT_KEYMAPS /etc/conf.d/consolefont:CONSOLEFONT-FONT,CONSOLETRANSLATION-FONT_MAP /etc/rc.conf:UNICODE" First we've got name of file in host file system tree. After colon there's mapping: -. If both variables have the same name you can enter just a single, but it's important to specify it! The module will source only variables you've listed. Below there's detailed description in BNF: ::= | " " ::= ":" ::= | "," ::= "-" | We assume no whitespace are allowed between symbols. is a file holding in your system. is a variable holding value of meaning the same as . is a variable which will be set up inside initramfs. If has the same name as we can omit . Example: /etc/conf.d/keymaps:KEYMAP,extended_keymaps-EXT_KEYMAPS = /etc/conf.d/keymaps:KEYMAP,extended_keymaps-EXT_KEYMAPS = /etc/conf.d/keymaps:KEYMAP,extended_keymaps-EXT_KEYMAPS = /etc/conf.d/keymaps = KEYMAP,extended_keymaps-EXT_KEYMAPS = KEYMAP = KEYMAP = extended_keymaps-EXT_KEYMAPS = extended_keymaps = EXT_KEYMAPS 2.3. Additional settings If you encounter following error message: "Directories consolefonts, consoletrans, keymaps, unimaps not found.", you can provide path where those directories lie in your system by setting kbddir in configuration file (the same where you put mappings). 3. Kernel parameters If you create generic initramfs you can set up i18n by kernel parameters using variables listed in 2.1. (except of UNIKEYMAP and GRP_TOGGLE) The recommended minimum is: FONT and KEYMAP. lib/kbd/unimaps/README000064400000000211152346205360010406 0ustar00The correspondences given in iso0[1-9].uni are according to The Unicode Standard, Version 1.0, Vol. 1. The remaining ones are phantasy. opt/alt/liblqr-1/share/doc/alt-liblqr-1/README000064400000010054152346330440014505 0ustar00 LiquidRescale library 0.4.0 =========================== Table of contents ----------------- * Introduction + Library features * Installation + Requirements + Normal setup * Using the library * References * Copyright + Introduction -------------- The LiquidRescale (lqr) library provides a C/C++ API for performing non-uniform resizing of images by the seam-carving technique. ++ Library features The library takes images in plain array format as input and converts them to a multi-size representation. Following is a list of features: * Easy to use and fully documented API * Currently supports 8 bit to 64 bit per channel images * Support for different color models: grayscale, RGB, CMY and their variants, and even custom ones * Areas in the image can be marked for preservation or discard, or for additional seam rigidity * Once the image has been fully processed, the scaling can be done in real-time. In fact, the information can be saved and read out later without any further processing * The resizing is done with a single function which automatically performs all the necessary operations; it can also work in successive steps without wasting computational time * Possibility to tune the carving operation by letting the seams be less connected, or more rigid, or both (the rigidity can be also be modulated through a mask, to get a differnet behaviour in different areas of the image) * Can export and import the visibility map (the seams) * Other images can be attached and undergo the same carving process as the parent image * The automatic feature detection algorithm can be tuned by selecting among different energy gradient functions, and easily defining custom ones * Reports progress through a customisable interface * A signalling system permits to cleanly handle errors * Portable to all major OS's + Installation -------------- ++ Dependencies The lqr library depends on the glib-2.0 libraries ++ Normal setup The build package uses autotools and libtool, so the installation commands on Unix systems are simply ./configure && make && sudo make install The last step requires administrative privileges. (Note: the default installation path is /usr since version 0.4) If you want to also install the man pages for the library functions, add the option `--enable-install-man' in the call to ./configure. If you want to disable legacy macro names which do not begin with LQR_ then add the option `--diable-legacy-macros' See the INSTALL file for a full description. + Using the library for development ------------------------------------- In order to use the library functions and structures from a C or C++ program, you have to add this include line in your program: #include At compile time, you can take advantage of pkg-config to set the proper flags. In the `examples' directory you can find a basic example program, `liquidrescale-basic', and a full-featured demo program, `liquidrescale', together with a simple Makefile. Both programs are fully commented. The "basic" version demonstrates how to use the strictly-needed library functions, while the full version uses almost all of the API methods provided. The Makefile shows how to set the compilation flags. See the README file in that directory for more information. The complete manual and reference for the library, together with some additional notes, can be found in the `docs' directory in docbook format. The reference is also provided in man page format. The makefile in that directory (hopefully) generates the manual in html format, using xsltproc; then you'll find the index named after `liblqr_manual_index.html'. See the README file in that directory for further information. + References ------------ The library implements the algorithm described in the paper "Seam Carving for Content-Aware Image Resizing" by Shai Avidan and Ariel Shamir, which can be found at http://www.faculty.idc.ac.il/arik/imret.pdf + Copyright ----------- Copyright (C) 2007-2009 Carlo Baldassi usr/lib64/python2.7/Demo/cgi/README000064400000000665152346401100012356 0ustar00CGI Examples ------------ Here are some example CGI programs. For a larger example, see ../../Tools/faqwiz/. cgi0.sh -- A shell script to test your server is configured for CGI cgi1.py -- A Python script to test your server is configured for CGI cgi2.py -- A Python script showing how to parse a form cgi3.py -- A Python script for driving an arbitrary CGI application wiki.py -- Sample CGI application: a minimal Wiki implementation lib64/python2.7/lib-tk/test/README000064400000001066152346421460012267 0ustar00Writing new tests ================= Precaution ---------- New tests should always use only one Tk window at once, like all the current tests do. This means that you have to destroy the current window before creating another one, and clean up after the test. The motivation behind this is that some tests may depend on having its window focused while it is running to work properly, and it may be hard to force focus on your window across platforms (right now only test_traversal at test_ttk.test_widgets.NotebookTest depends on this). usr/lib64/python2.7/Demo/rpc/README000064400000002355152347171300012405 0ustar00This is a Python interface to Sun RPC, designed and implemented mostly by reading the Internet RFCs about the subject. *** NOTE: xdr.py has evolved into the standard module xdrlib.py *** There are two library modules, xdr.py and rpc.py, and several example clients: mountclient.py, nfsclient.py, and rnusersclient.py, implementing the NFS Mount protocol, (part of) the NFS protocol, and the "rnusers" protocol (used by rusers(1)), respectively. The latter demonstrates the use of broadcast via the Port mapper's CALLIT procedure. There is also a way to create servers in Python. To test the nfs client, run it from the shell with something like this: python -c 'import nfsclient; nfsclient.test()' [hostname [filesystemname]] When called without a filesystemname, it lists the filesystems at the host; default host is the local machine. Other clients are tested similarly. For hostname, use e.g. wuarchive.wustl.edu or gatekeeper.dec.com (two hosts that are known to export NFS filesystems with little restrictions). There are now two different RPC compilers: 1) Wim Lewis rpcgen.py found on http://www.omnigroup.com/~wiml/soft/stale-index.html#python. 2) Peter Åstrands rpcgen.py, which is part of "pynfs" (http://www.cendio.se/~peter/pynfs/). usr/lib64/python2.7/Demo/README000064400000003640152347203630011621 0ustar00This directory contains various demonstrations of what you can do with Python. They were all written by me except where explicitly stated otherwise -- in general, demos contributed by others ends up in the ../Contrib directory, unless I think they're of utmost general importance (like Matt Conway's Tk demos). A fair number of utilities that are useful when while developing Python code can be found in the ../Tools directory -- some of these can also be considered good examples of how to write Python code. Finally, in order to save disk space and net bandwidth, not all subdirectories listed here are distributed. They are listed just in case I change my mind about them. cgi CGI examples (see also ../Tools/faqwiz/.) classes Some examples of how to use classes. comparisons A set of responses to a really old language-comparison challenge. curses A set of curses demos. embed An example of embedding Python in another application (see also pysvr). imputil Demonstration subclasses of imputil.Importer. md5test Test program for the optional md5 module. metaclasses The code from the 1.5 metaclasses paper on the web. parser Example using the parser module. pdist Old, unfinished code messing with CVS, RCS and remote files. pysvr An example of embedding Python in a threaded application. rpc A set of classes for building clients and servers for Sun RPC. scripts Some useful Python scripts that I put in my bin directory. No optional built-in modules needed. sockets Examples for the new built-in module 'socket'. threads Demos that use the 'thread' module. (Currently these only run on SGIs, but this may change in the future.) tix Demos using the Tix widget set addition to Tkinter. tkinter Demos using the Tk interface (including Matt Conway's excellent set of demos). xml Some XML demos. zlib Some demos for the zlib module (see also the standard library module gzip.py). usr/lib/firewalld/ipsets/README000064400000000035152347206300012263 0ustar00Location for built-in ipsets lib64/libdnf/plugins/README000064400000000302152347222270011264 0ustar00 This directory holds plugins for the libdnf library. Any files in this directory which have the ".so" extension will be processed as libdnf plugins. Files are processed in alphabetical order. lib64/python2.7/Demo/scripts/README000064400000001761152347743240012507 0ustar00This directory contains a collection of executable Python scripts. See also the Tools/scripts directory! beer.py Print the classic 'bottles of beer' list eqfix.py Fix .py files to use the correct equality test operator fact.py Factorize numbers find-uname.py Search for Unicode characters using regexps from.py Summarize mailbox lpwatch.py Watch BSD line printer queues makedir.py Like mkdir -p markov.py Markov chain simulation of words or characters mboxconvert.py Convert MH or MMDF mailboxes to unix mailbox format morse.py Produce morse code (audible or on AIFF file) newslist.py List all newsgroups on a NNTP server as HTML pages pi.py Print all digits of pi -- given enough time and memory pp.py Emulate some Perl command line options primes.py Print prime numbers queens.py Dijkstra's solution to Wirth's "N Queens problem" script.py Equivalent to BSD script(1) -- by Steen Lumholt unbirthday.py Print unbirthday count update.py Update a bunch of files according to a script. usr/share/bison/README000064400000003741152350174050010460 0ustar00-*- outline -*- This directory contains data needed by Bison. * Skeletons Bison skeletons: the general shapes of the different parser kinds, that are specialized for specific grammars by the bison program. Currently, the supported skeletons are: - yacc.c It used to be named bison.simple: it corresponds to C Yacc compatible LALR(1) parsers. - lalr1.cc Produces a C++ parser class. - lalr1.java Produces a Java parser class. - glr.c A Generalized LR C parser based on Bison's LALR(1) tables. - glr.cc A Generalized LR C++ parser. Actually a C++ wrapper around glr.c. These skeletons are the only ones supported by the Bison team. Because the interface between skeletons and the bison program is not finished, *we are not bound to it*. In particular, Bison is not mature enough for us to consider that "foreign skeletons" are supported. * m4sugar This directory contains M4sugar, sort of an extended library for M4, which is used by Bison to instantiate the skeletons. * xslt This directory contains XSLT programs that transform Bison's XML output into various formats. - bison.xsl A library of routines used by the other XSLT programs. - xml2dot.xsl Conversion into GraphViz's dot format. - xml2text.xsl Conversion into text. - xml2xhtml.xsl Conversion into XHTML. ----- Copyright (C) 2002, 2008-2015 Free Software Foundation, Inc. This file is part of GNU Bison. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . etc/pki/ca-trust/extracted/pem/README000064400000001602152351503130013265 0ustar00This directory /etc/pki/ca-trust/extracted/pem/ contains CA certificate bundle files which are automatically created based on the information found in the /usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories. All files are in the BEGIN/END CERTIFICATE file format, as described in the x509(1) manual page. Distrust information cannot be represented in this file format, and distrusted certificates are missing from these files. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. etc/pki/ca-trust/extracted/openssl/README000064400000001423152351725000014172 0ustar00This directory /etc/pki/ca-trust/extracted/openssl/ contains CA certificate bundle files which are automatically created based on the information found in the /usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories. All files are in the BEGIN/END TRUSTED CERTIFICATE file format, as described in the x509(1) manual page. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. lib/dracut/modules.d/91crypt-gpg/README000064400000005043152352351570013446 0ustar00# Directions for changing a system from password-based gpg keyfile # to smartcard-based gpg keyfile # Be sure that you meet the following requirements: # 1. GnuPG >= 2.1 installed with # * Smartcard support enabled (scdaemon must be built) # * Direct CCID access built into scdaemon # 2. A password-based gpg keyfile ${KEYFILE} (e.g. "keyfile.gpg"): # That is, a file containing the slot key for LUKS, which # has been encrypted symmetrically with GnuPG using # a password. # 3. Your public OpenPGP identity ${RECIPIENT} (e.g. "3A696356") # 4. An OpenPGP smartcard holding the decryption key associated # with your public identity # 5. A CCID smartcard reader # Notes: Requirement 4. and 5. can of course be one device, e.g. # a USB token with an integrated OpenPGP smartcard # Make a backup of your keyfile (assuming it lies on the boot partition) $ cp /boot/${KEYFILE} /safe/place/keyfile.bak.gpg # Change your keyfile from purely password-based to both # password-based and key-based (you can then decrypt the keyfile # with either method). As an example aes256 is chosen, the cipher # is not important to this guide, but do note that your kernel # must support it at boot time (be it built into the kernel image # or loaded as a module from the initramfs). $ cat /safe/place/keyfile.bak.gpg | gpg -d | gpg --encrypt --recipient ${RECIPIENT} --cipher-algo aes256 --armor -c > /safe/place/keyfile_sc.gpg # Verify that you can decrypt your new keyfile both with the password # and your smartcard. # (with smartcard inserted, you should be prompted for your PIN, unless # you already did so and have not yet timed out) $ gpg -d /safe/place/keyfile_sc.gpg # (with smartcard disconnected, you should be prompted for your password) $ gpg -d /safe/place/keyfile_sc.gpg # After verification, replace your old keyfile with your new one $ su -c 'cp /safe/place/keyfile_sc.gpg /boot/${KEYFILE}' # Export your public key to where crypt-gpg can find it $ gpg --armor --export-options export-minimal --export ${RECIPIENT} > /safe/place/crypt-public-key.gpg $ su -c 'cp /safe/place/crypt-public-key.gpg /etc/dracut.conf.d/crypt-public-key.gpg' # Rebuild your initramfs as usual # When booting with any of the requirements not met, crypt-gpg will default to password-based keyfile unlocking. # If all requirements are met and smartcard support is not disabled by setting the kernel option "rd.luks.smartcard=0" # crypt-gpg will try find and use a connected OpenPGP smartcard by prompting you for the PIN and then # unlocking the gpg keyfile with the smartcard. usr/share/libtool/README000064400000001265152357740340011021 0ustar00This is GNU libltdl, a system independent dlopen wrapper for GNU libtool. It supports the following dlopen interfaces: * dlopen (POSIX) * shl_load (HP-UX) * LoadLibrary (Win16 and Win32) * load_add_on (BeOS) * GNU DLD (emulates dynamic linking for static libraries) * dyld (darwin/Mac OS X) * libtool's dlpreopen -- Copyright (C) 1999, 2003, 2011-2015 Free Software Foundation, Inc. Written by Thomas Tanner, 1999 This file is part of GNU Libtool. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. lib64/python2.7/Tools/README000064400000003471152360746050011231 0ustar00This directory contains a number of Python programs that are useful while building or extending Python. audiopy Audiopy is a program to control the Solaris audio device, allowing you to choose both the input and output devices, and to set the output volume, that can be run either as a command-line script, or as a Tkinter application. bgen Generate complete extension modules from a description. Still under development! WARNING: bgen has been removed in 3.0. compiler Tools used to maintain the compiler package in the standard library. faqwiz FAQ Wizard. See http://www.python.org/cgi-bin/faqw.py for a live example. freeze Create a stand-alone executable from a Python program. gdb Python code to be run inside gdb, to make it easier to debug Python itself (by David Malcolm). i18n Tools for internationalization. pygettext.py parses Python source code and generates .pot files, and msgfmt.py generates a binary message catalog from a catalog in text format. pynche A Tkinter-based color editor. scripts A number of useful single-file programs, e.g. tabnanny.py by Tim Peters, which checks for inconsistent mixing of tabs and spaces, and 2to3, which converts Python 2 code to Python 3 code. unicode Tools used to generate unicode database files for Python 2.0 (by Fredrik Lundh). versioncheck A tool to automate checking whether you have the latest version of a package (by Jack Jansen). webchecker A link checker for web sites. world Script to take a list of Internet addresses and print out where in the world those addresses originate from, based on the top-level domain country code found in the address. A generic benchmark suite is maintained separately at https://github.com/python/performance usr/lib64/python2.7/site-packages/pynche/README000064400000036650152361041160014744 0ustar00Pynche - The PYthonically Natural Color and Hue Editor Contact: Barry A. Warsaw Email: bwarsaw@python.org Version: 1.3 Introduction Pynche is a color editor based largely on a similar program that I originally wrote back in 1987 for the Sunview window system. That editor was called ICE, the Interactive Color Editor. I'd always wanted to port this program to X but didn't feel like hacking X and C code to do it. Fast forward many years, to where Python + Tkinter provides such a nice programming environment, with enough power, that I finally buckled down and re-implemented it. I changed the name because these days, too many other systems have the acronym `ICE'. Pynche should work with any variant of Python after 1.5.2 (e.g. 2.0.1 and 2.1.1), using Tk 8.0.x. It's been tested on Solaris 2.6, Windows NT 4, and various Linux distros. You'll want to be sure to have at least Tk 8.0.3 for Windows. Also, Pynche is very colormap intensive, so it doesn't work very well on 8-bit graphics cards; 24bit+ graphics cards are so cheap these days, I'll probably never "fix" that. Pynche must find a text database of colors names in order to provide `nearest' color matching. Pynche is distributed with an rgb.txt file from the X11R6.4 distribution for this reason, along with other "Web related" database (see below). You can use a different file with the -d option. The file xlicense.txt contains the license only for rgb.txt and both files are in the X/ subdirectory. Pynche is pronounced: Pin'-chee Running Standalone On Unix, start it by running the `pynche' script. On Windows, run pynche.pyw to inhibit the console window. When run from the command line, the following options are recognized: --database file -d file Alternate location of the color database file. Without this option, the first valid file found will be used (see below). --initfile file -i file Alternate location of the persistent initialization file. See the section on Persistency below. --ignore -X Ignore the persistent initialization file when starting up. Pynche will still write the current option settings to the persistent init file when it quits. --help -h Print the help message. initialcolor a Tk color name or #rrggbb color spec to be used as the initially selected color. This overrides any color saved in the persistent init file. Since `#' needs to be escaped in many shells, it is optional in the spec (e.g. #45dd1f is the same as 45dd1f). Running as a Modal Dialog Pynche can be run as a modal dialog, inside another application, say as a general color chooser. In fact, Grail 0.6 uses Pynche and a future version of IDLE may as well. Pynche supports the API implemented by the Tkinter standard tkColorChooser module, with a few changes as described below. By importing pyColorChooser from the Pynche package, you can run pyColorChooser.askcolor() which will popup Pynche as a modal dialog, and return the selected color. There are some UI differences when running as a modal vs. standalone. When running as a modal, there is no "Quit" menu item under the "File" menu. Instead there are "Okay" and "Cancel" buttons. When "Okay" is hit, askcolor() returns the tuple ((r, g, b), "name") where r, g, and b are red, green, and blue color values respectively (in the range 0 to 255). "name" will be a color name from the color database if there is an exact match, otherwise it will be an X11 color spec of the form "#rrggbb". Note that this is different than tkColorChooser, which doesn't know anything about color names. askcolor() supports the following optional keyword arguments: color the color to set as the initial selected color master[*] the master window to use as the parent of the modal dialog. Without this argument, pyColorChooser will create its own Tkinter.Tk instance as the master. This may not be what you want. databasefile similar to the --database option, the value must be a file name initfile[*] similar to the --initfile option, the value must be a file name ignore[*] similar to the --ignore flag, the value is a boolean wantspec When this is true, the "name" field in the return tuple will always be a color spec of the form "#rrggbb". It will not return a color name even if there is a match; this is so pyColorChooser can exactly match the API of tkColorChooser. [*] these arguments must be specified the first time askcolor() is used and cannot be changed on subsequent calls. The Colorstrip Window The top part of the main Pynche window contains the "variation strips". Each strip contains a number of "color chips". The strips always indicate the currently selected color by a highlight rectangle around the selected color chip, with an arrow pointing to the chip. Each arrow has an associated number giving you the color value along the variation's axis. Each variation strip shows you the colors that are reachable from the selected color by varying just one axis of the color solid. For example, when the selected color is (in Red/Green/Blue notation) 127/127/127, the Red Variations strip shows you every color in the range 0/127/127 to 255/127/127. Similarly for the green and blue axes. You can select any color by clicking on its chip. This will update the highlight rectangle and the arrow, as well as other displays in Pynche. Click on "Update while dragging" if you want Pynche to update the selected color while you drag along any variation strip (this will be a bit slower). Click on "Hexadecimal" to display the arrow numbers in hex. There are also two shortcut buttons in this window, which auto-select Black (0/0/0) and White (255/255/255). The Proof Window In the lower left corner of the main window you see two larger color chips. The Selected chip shows you a larger version of the color selected in the variation strips, along with its X11 color specification. The Nearest chip shows you the closest color in the X11 database to the selected color, giving its X11 color specification, and below that, its X11 color name. When the Selected chip color exactly matches the Nearest chip color, you will see the color name appear below the color specification for the Selected chip. Clicking on the Nearest color chip selects that color. Color distance is calculated in the 3D space of the RGB color solid and if more than one color name is the same distance from the selected color, the first one found will be chosen. Note that there may be more than one X11 color name for the same RGB value. In that case, the first one found in the text database is designated the "primary" name, and this is shown under the Nearest chip. The other names are "aliases" and they are visible in the Color List Window (see below). Both the color specifications and color names are selectable for copying and pasting into another window. The Type-in Window At the lower right of the main window are three entry fields. Here you can type numeric values for any of the three color axes. Legal values are between 0 and 255, and these fields do not allow you to enter illegal values. You must hit Enter or Tab to select the new color. Click on "Update while typing" if you want Pynche to select the color on every keystroke (well, every one that produces a legal value!) Click on "Hexadecimal" to display and enter color values in hex. Other Views There are three secondary windows which are not displayed by default. You can bring these up via the "View" menu on the main Pynche window. The Text Window The "Text Window" allows you to see what effects various colors have on the standard Tk text widget elements. In the upper part of the window is a plain Tk text widget and here you can edit the text, select a region of text, etc. Below this is a button "Track color changes". When this is turned on, any colors selected in the other windows will change the text widget element specified in the radio buttons below. When this is turned off, text widget elements are not affected by color selection. You can choose which element gets changed by color selection by clicking on one of the radio buttons in the bottom part of this window. Text foreground and background affect the text in the upper part of the window. Selection foreground and background affect the colors of the primary selection which is what you see when you click the middle button (depending on window system) and drag it through some text. The Insertion is the insertion cursor in the text window, where new text will be inserted as you type. The insertion cursor only has a background. The Color List Window The "Color List" window shows every named color in the color name database (this window may take a while to come up). In the upper part of the window you see a scrolling list of all the color names in the database, in alphabetical order. Click on any color to select it. In the bottom part of the window is displayed any aliases for the selected color (those color names that have the same RGB value, but were found later in the text database). For example, find the color "Black" and you'll see that its aliases are "gray0" and "grey0". If the color has no aliases you'll see "" here. If you just want to see if a color has an alias, and do not want to select a color when you click on it, turn off "Update on Click". Note that the color list is always updated when a color is selected from the main window. There's no way to turn this feature off. If the selected color has no matching color name you'll see "" in the Aliases window. The Details Window The "Details" window gives you more control over color selection than just clicking on a color chip in the main window. The row of buttons along the top apply the specified increment and decrement amounts to the selected color. These delta amounts are applied to the variation strips specified by the check boxes labeled "Move Sliders". Thus if just Red and Green are selected, hitting -10 will subtract 10 from the color value along the red and green variation only. Note the message under the checkboxes; this indicates the primary color level being changed when more than one slider is tied together. For example, if Red and Green are selected, you will be changing the Yellow level of the selected color. The "At Boundary" behavior determines what happens when any color variation hits either the lower or upper boundaries (0 or 255) as a result of clicking on the top row buttons: Stop When the increment or decrement would send any of the tied variations out of bounds, the entire delta is discarded. Wrap Around When the increment or decrement would send any of the tied variations out of bounds, the out of bounds value is wrapped around to the other side. Thus if red were at 238 and +25 were clicked, red would have the value 7. Preserve Distance When the increment or decrement would send any of the tied variations out of bounds, all tied variations are wrapped as one, so as to preserve the distance between them. Thus if green and blue were tied, and green was at 238 while blue was at 223, and +25 were clicked, green would be at 15 and blue would be at 0. Squash When the increment or decrement would send any of the tied variations out of bounds, the out of bounds variation is set to the ceiling of 255 or floor of 0, as appropriate. In this way, all tied variations are squashed to one edge or the other. The top row buttons have the following keyboard accelerators: -25 == Shift Left Arrow -10 == Control Left Arrow -1 == Left Arrow +1 == Right Arrow +10 == Control Right Arrow +25 == Shift Right Arrow Keyboard Accelerators Alt-w in any secondary window dismisses the window. In the main window it exits Pynche (except when running as a modal). Alt-q in any window exits Pynche (except when running as a modal). Persistency Pynche remembers various settings of options and colors between invocations, storing these values in a `persistent initialization file'. The actual location of this file is specified by the --initfile option (see above), and defaults to ~/.pynche. When Pynche exits, it saves these values in the init file, and re-reads them when it starts up. There is no locking on this file, so if you run multiple instances of Pynche at a time, you may clobber the init file. The actual options stored include - the currently selected color - all settings of checkbox and radio button options in all windows - the contents of the text window, the current text selection and insertion point, and all current text widget element color settings. - the name of the color database file (but not its contents) You can inhibit Pynche from reading the init file by supplying the --ignore option on the command line. However, you cannot suppress the storing of the settings in the init file on Pynche exit. If you really want to do this, use /dev/null as the init file, using --initfile. Color Name Database Files Pynche uses a color name database file to calculate the nearest color to the selected color, and to display in the Color List view. Several files are distributed with Pynche, described below. By default, the X11 color name database file is selected. Other files: html40colors.txt -- the HTML 4.0 guaranteed color names websafe.txt -- the 216 "Web-safe" colors that Netscape and MSIE guarantee will not be dithered. These are specified in #rrggbb format for both values and names webcolors.txt -- The 140 color names that Tim Peters and his sister say NS and MSIE both understand (with some controversy over AliceBlue). namedcolors.txt -- an alternative set of Netscape colors. You can switch between files by choosing "Load palette..." from the "File" menu. This brings up a standard Tk file dialog. Choose the file you want and then click "Ok". If Pynche understands the format in this file, it will load the database and update the appropriate windows. If not, it will bring up an error dialog. To Do Here's a brief list of things I want to do (some mythical day): - Better support for resizing the top level windows - More output views, e.g. color solids - Have the notion of a `last color selected'; this may require a new output view - Support setting the font in the text view - Support distutils setup.py for installation I'm open to suggestions! Local Variables: indent-tabs-mode: nil End: etc/pki/ca-trust/extracted/README000064400000001060152361324230012505 0ustar00This directory /etc/pki/ca-trust/extracted/ contains CA certificate bundle files which are automatically created. If your application isn't able to load the PKCS#11 module p11-kit-trust.so, then you can use these files in your application to load a list of global root CA certificates. Please never manually edit the files stored in this directory, because your changes will be lost and the files automatically overwritten, each time the update-ca-trust command gets executed. Please refer to the update-ca-trust(8) manual page for additional information. usr/lib64/python2.7/Demo/parser/README000064400000002006152361416150013107 0ustar00These files are from the large example of using the `parser' module. Refer to the Python Library Reference for more information. It also contains examples for the AST parser. Files: ------ FILES -- list of files associated with the parser module. README -- this file. docstring.py -- sample source file containing only a module docstring. example.py -- module that uses the `parser' module to extract information from the parse tree of Python source code. simple.py -- sample source containing a "short form" definition. source.py -- sample source code used to demonstrate ability to handle nested constructs easily using the functions and classes in example.py. test_parser.py program to put the parser module through its paces. test_unparse.py tests for the unparse module unparse.py AST (2.7) based example to recreate source code from an AST. Enjoy!