Re: Smart card manager
On Wednesday 11 April 2012 02:57:08 Novick, Jeffrey L CTR (US) wrote: First thank you for original work, that must have made you crazy and for your reply. I also found that this laptop supposedly needed a firmware upgrade, but that didn't work either. I think your problem really resides with esc, and once that is fixed the next hurdle will be getting OpenSC to recognize the card type -- which should be automatic, but we all love words like should, don't we? Anyway, firmware upgrades are (usually) a good thing regardless. Meanwhile, I have disabled selinux completely and that had no effect. I will leave it this way until this is resolved. I think this is an unnecessary step at the moment. Your reader isn't having trouble getting recognized, I think. And if it is we'll worry with verifying the problem and then writing a policy to attach to pcscd if it actually needs it (my feeling is that the necessary policy must exist, but is probably provided by another package in the TUV certificate system, not in the pcscd package where it belongs). cd lib/notifytray; make libs make[2]: Entering directory `/home/mockbuild/rpmbuild/BUILD/esc- 1.1.0/esc/src/lib/notifytray' gcc -o Linux2.6_x86_glibc_PTH_64_OPT.OBJ/notifytray.o -c -O2 -fPIC - DLINUX1_2 -Di386 -D_XOPEN_SOURCE -DLINUX2_1 -ansi -Wall -pipe -DLINUX - Dlinux -D_POSIX_SOURCE -D_BSD_SOURCE -DHAVE_STRERROR -DXP_UNIX - I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 - I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 - I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 - I/usr/include/freetype2 -I/usr/include/libpng12 -UDEBUG -DNDEBUG - D_REENTRANT -DDLL_PREFIX=\lib\ -DDLL_SUFFIX=\so\ - I../../../dist/Linux2.6_x86_glibc_PTH_64_OPT.OBJ/include - I../../../dist/public/traynotify -I../../../dist/private/traynotify - I../../../dist/public/libnotify -DHAVE_LIB_NOTIFY notifytray.c notifytray.c: In function 'notify_icon_send_tooltip_msg': notifytray.c:227: warning: assignment discards qualifiers from pointer target type notifytray.c:242: error: too few arguments to function 'notify_notification_new' On the surface that looks easy to fix, but I'll have to look and see whether or not the error is as simple as this message, or if its a deeper issue and how convoluted (or pretty) the code is. Also, I'll need to check and see if there is already a patch for this as I'm sure its discussed somewhere. Removed coolkey from Firefox, installed OpenSC and still had no luck. I did it all again with reboots in between every step, and still no good. Until we get esc rebuilt I don't think this is going to be very meaningful, as even if opensc and Firefox become buddies there won't be a bridge to the actual card until a new one is built. Under Firefox, Edit-Preferences-Encyption-Security Devices, status says Not Present with or without my cac inserted. Supports the idea that the fault is somewhere in the esc-pcscd-scr331 driver chain. The good thing here is that Firefox didn't reject opensc or coolkey -- this used to be a problem with some versions of 3.x. I won't have time to mess with it for at least a few days (maybe a week?) but bother me about it early next week and I'll give it another look. Hopefully the build can be simplified. And anyway I'm impressed that you went so far as setting up a build environment and really getting under the problem before posting to the list. If only more bug reports and help requests were submitted by such motivated people! This alone is what interests me in giving you a hand.
Re: network manager questions
2012/4/10 Bluejay Adametz blue...@fujifilm.com [...] I wonder just how much the user base overlaps between Fedora and RHEL. [...] I guess everyone who uses RHEL, SL, ... in a professional environment. Especially for upcoming releases I need to know in which direction it will move if the IT should act proactive and not reactive. Architectural decisions relay on this kind of information. Regards Thomas -- Linux ... enjoy the ride!
Re: Smart card manager
I won't have time to mess with it for at least a few days (maybe a week?) but bother me about it early next week and I'll give it another look. Hopefully the build can be simplified. All I can say and do is thank you and I'll poke around to see if I can get esc rebuilt. If I'm successful, I'll post results, otherwise, no update = no success. And anyway I'm impressed that you went so far as setting up a build environment and really getting under the problem before posting to the list. If only more bug reports and help requests were submitted by such motivated people! This alone is what interests me in giving you a hand. I'm glad you said this, I was afraid that I didn't provide enough info. If I'm asking for help, I'll do what I can to help someone help me.
Re: Smart card manager
On Wed, Apr 11, 2012 at 5:06 AM, Novick, Jeffrey L CTR (US) jeffrey.l.novick@mail.mil wrote: I won't have time to mess with it for at least a few days (maybe a week?) but bother me about it early next week and I'll give it another look. Hopefully the build can be simplified. All I can say and do is thank you and I'll poke around to see if I can get esc rebuilt. If I'm successful, I'll post results, otherwise, no update = no success. An update to esc just came out upstream: https://rhn.redhat.com/errata/RHBA-2012-0472.html The ESC utility did not start when the latest 10 series release of the XULRunner runtime environment was installed on the system. This update includes necessary changes to ensure that ESC works as expected with the latest version of XULRunner. (BZ#807264) Hopefully this provides the fix. Akemi
Re: iptables + vhost access
Not knowing the configuration of your httpd.conf file and the configuration of the local users' home directory, there is no direct answer. Therefore, my approach to your question is to give you a very basic setup, which would allow users to access files in their home's directory. You can base off of this to make it works on your machine. Before you do anything, backup your httpd.conf file. Even better, do this on a test VM. In the file httpd.conf, change these 2 directives to look like this: #UserDir disabled UserDir *public_html* this enables local users to access html files inside the the *public_html * directory. Let's say we want UserX to have access to his/her home directory: mkdir /home/UserX*/public_html* Then create an html file in the *public_html *directory, Now comes the fun part, permission and SELinux :). Permission: Make sure UserX is the owner of the *public_html* directory and all files within it (hence, recursively). chown userx:userx *public_html* Directory and files need read and execute permission chmod 755 Selinux: public_html and all files within must have one of these context types: httpd_sys_content_t or public_content_rw_t sample command: chcon -R -t httpd_sys_content_t *public_html *then make sure SELinux setting survives reboot, run command: semanage fcontext -a -t httpd_sys_content_t *public_html* verify the directory and do the same to all files inside *public_html*: ll -Z Finally, enable SELinux boolean: setsebool -P httpd_enable_homedirs on Restart Apache without interrupting the users: apachectl graceful Now access UserX' home directory: http://servername_or_ip_address/~userx/ This is just a basic configuration to give you a general idea. You will have to customize the settings and permissions according to your server's needs. good luck -Tam On Mon, Apr 9, 2012 at 8:33 PM, Terry Northren tnorth...@gmail.com wrote: Hi again, on Apache server, how do I allow users to access files in their home folders?
Re: iptables + vhost access
Tam, I followed your directions. I ran into an error when I executed the semanage command: semanage fcontext -a -t httpd_sys_content_t public_html Here is my output error: -bash: /usr/sbin/semanage: No such file or directory I went ahead and followed the rest of your tutorial. It worked!! Does this mean I will have to re-configure SELinux after every reboot? On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: Not knowing the configuration of your httpd.conf file and the configuration of the local users' home directory, there is no direct answer. Therefore, my approach to your question is to give you a very basic setup, which would allow users to access files in their home's directory. You can base off of this to make it works on your machine. Before you do anything, backup your httpd.conf file. Even better, do this on a test VM. In the file httpd.conf, change these 2 directives to look like this: #UserDir disabled UserDir *public_html* this enables local users to access html files inside the the *public_html * directory. Let's say we want UserX to have access to his/her home directory: mkdir /home/UserX*/public_html* Then create an html file in the *public_html *directory, Now comes the fun part, permission and SELinux :). Permission: Make sure UserX is the owner of the *public_html* directory and all files within it (hence, recursively). chown userx:userx *public_html* Directory and files need read and execute permission chmod 755 Selinux: public_html and all files within must have one of these context types: httpd_sys_content_t or public_content_rw_t sample command: chcon -R -t httpd_sys_content_t *public_html *then make sure SELinux setting survives reboot, run command: semanage fcontext -a -t httpd_sys_content_t *public_html* verify the directory and do the same to all files inside *public_html*: ll -Z Finally, enable SELinux boolean: setsebool -P httpd_enable_homedirs on Restart Apache without interrupting the users: apachectl graceful Now access UserX' home directory: http://servername_or_ip_address/~userx/ This is just a basic configuration to give you a general idea. You will have to customize the settings and permissions according to your server's needs. good luck -Tam On Mon, Apr 9, 2012 at 8:33 PM, Terry Northren tnorth...@gmail.com wrote: Hi again, on Apache server, how do I allow users to access files in their home folders?
Re: iptables + vhost access
On 11 April 2012 15:53, Terry Northren tnorth...@gmail.com wrote: I followed your directions. I ran into an error when I executed the semanage command: semanage fcontext -a -t httpd_sys_content_t public_html Here is my output error: -bash: /usr/sbin/semanage: No such file or directory [ajb@Duo2 ~]$ rpm -qf $(locate bin/semanage) policycoreutils-python-2.0.83-19.21.el6_2.x86_64 Ensure that you have the policycoreutils-python package installed. Alan.
Re: iptables + vhost access
That error means you do not have the prerequisite package installs. Install the package: yum -y install policycoreutils-python Since we are on the SELinux topic, I would recommend you also install: yum -y install setools-console Btw, looking back at your first post about Apache authentication and access deny and allow, how did you manage to get your Apache to work in the first place, especially configuring SELinux settings? On Wed, Apr 11, 2012 at 10:53 AM, Terry Northren tnorth...@gmail.comwrote: Tam, I followed your directions. I ran into an error when I executed the semanage command: semanage fcontext -a -t httpd_sys_content_t public_html Here is my output error: -bash: /usr/sbin/semanage: No such file or directory I went ahead and followed the rest of your tutorial. It worked!! Does this mean I will have to re-configure SELinux after every reboot? On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: Not knowing the configuration of your httpd.conf file and the configuration of the local users' home directory, there is no direct answer. Therefore, my approach to your question is to give you a very basic setup, which would allow users to access files in their home's directory. You can base off of this to make it works on your machine. Before you do anything, backup your httpd.conf file. Even better, do this on a test VM. In the file httpd.conf, change these 2 directives to look like this: #UserDir disabled UserDir *public_html* this enables local users to access html files inside the the *public_html * directory. Let's say we want UserX to have access to his/her home directory: mkdir /home/UserX*/public_html* Then create an html file in the *public_html *directory, Now comes the fun part, permission and SELinux :). Permission: Make sure UserX is the owner of the *public_html* directory and all files within it (hence, recursively). chown userx:userx *public_html* Directory and files need read and execute permission chmod 755 Selinux: public_html and all files within must have one of these context types: httpd_sys_content_t or public_content_rw_t sample command: chcon -R -t httpd_sys_content_t *public_html *then make sure SELinux setting survives reboot, run command: semanage fcontext -a -t httpd_sys_content_t *public_html* verify the directory and do the same to all files inside *public_html*: ll -Z Finally, enable SELinux boolean: setsebool -P httpd_enable_homedirs on Restart Apache without interrupting the users: apachectl graceful Now access UserX' home directory: http://servername_or_ip_address/~userx/ This is just a basic configuration to give you a general idea. You will have to customize the settings and permissions according to your server's needs. good luck -Tam On Mon, Apr 9, 2012 at 8:33 PM, Terry Northren tnorth...@gmail.com wrote: Hi again, on Apache server, how do I allow users to access files in their home folders?
Re: iptables + vhost access
Tam and Alan, thanks for the package. That solved it. Tam, what do I do with setools-console package? Our Linux Admin was working on a test Apache server. Most of the configuration was done by him, but he left the company. I am picking up the left behind. Coming from the Windows side, I am new to many aspects of Linux. Still learning my rope. The Scientific Linux community has been extremely helpful and resourceful :D. On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: That error means you do not have the prerequisite package installs. Install the package: yum -y install policycoreutils-python Since we are on the SELinux topic, I would recommend you also install: yum -y install setools-console Btw, looking back at your first post about Apache authentication and access deny and allow, how did you manage to get your Apache to work in the first place, especially configuring SELinux settings? On Wed, Apr 11, 2012 at 10:53 AM, Terry Northren tnorth...@gmail.comwrote: Tam, I followed your directions. I ran into an error when I executed the semanage command: semanage fcontext -a -t httpd_sys_content_t public_html Here is my output error: -bash: /usr/sbin/semanage: No such file or directory I went ahead and followed the rest of your tutorial. It worked!! Does this mean I will have to re-configure SELinux after every reboot? On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: Not knowing the configuration of your httpd.conf file and the configuration of the local users' home directory, there is no direct answer. Therefore, my approach to your question is to give you a very basic setup, which would allow users to access files in their home's directory. You can base off of this to make it works on your machine. Before you do anything, backup your httpd.conf file. Even better, do this on a test VM. In the file httpd.conf, change these 2 directives to look like this: #UserDir disabled UserDir *public_html* this enables local users to access html files inside the the *public_html * directory. Let's say we want UserX to have access to his/her home directory: mkdir /home/UserX*/public_html* Then create an html file in the *public_html *directory, Now comes the fun part, permission and SELinux :). Permission: Make sure UserX is the owner of the *public_html* directory and all files within it (hence, recursively). chown userx:userx *public_html* Directory and files need read and execute permission chmod 755 Selinux: public_html and all files within must have one of these context types: httpd_sys_content_t or public_content_rw_t sample command: chcon -R -t httpd_sys_content_t *public_html *then make sure SELinux setting survives reboot, run command: semanage fcontext -a -t httpd_sys_content_t *public_html* verify the directory and do the same to all files inside *public_html*: ll -Z Finally, enable SELinux boolean: setsebool -P httpd_enable_homedirs on Restart Apache without interrupting the users: apachectl graceful Now access UserX' home directory: http://servername_or_ip_address/~userx/ This is just a basic configuration to give you a general idea. You will have to customize the settings and permissions according to your server's needs. good luck -Tam On Mon, Apr 9, 2012 at 8:33 PM, Terry Northren tnorth...@gmail.com wrote: Hi again, on Apache server, how do I allow users to access files in their home folders?
Re: iptables + vhost access
We're glad to be able to help you. The package setools-console is very handy when it comes to setting the SELinux's user, role, and type for a specific file to allow specific access to a specific services. After installing setools-console, you can find out the list of SELinux context type: seinfo -t Or a list of SELinux context user: seinfo -u Or role seinfo -r You will get a long list of context types. An example I've gave you earlier was httpd_sys_content_t. Try this command: seinfo -t | grep httpd_sys Output: httpd_sys_content_t recognize that? :) httpd_sys_htaccess_t httpd_sys_ra_content_t httpd_sys_rw_content_t httpd_sys_script_t httpd_sys_script_exec_t Another example, find the SELinux context type for Samba share file. seinfo -t | grep samba Output: samba_secrets_t samba_unconfined_script_exec_t samba_net_t samba_var_t samba_net_exec_t samba_net_tmp_t samba_unconfined_net_t samba_unconfined_script_t sambagui_exec_t samba_share_t = general samba share privilege samba_initrc_exec_t sambagui_t samba_etc_t samba_log_t Lastly, to make sure your hard-work SELinux survives reboot, run: semanage fcontext -a -t context_type_goes_here_t file_name_goes_here If you assigned context user, then run: semanage fcontext -a -s context_user_goes_here_t -t context_type_goes_here_t file_name Actual example: semanage fcontext -a -s system_u -t samba_share_t /samba/sharedir And of course, you can always have the option to turn off SELinux but I would not recommend it. The only time I turned off SELinux was when I tested a service that kept spitting out permission denied or service not accessible... On Apr 3, zxq9 provided an excellent intro to SELinux. Take a look at his post. Wish you the best. -Tam On Wed, Apr 11, 2012 at 11:32 AM, Terry Northren tnorth...@gmail.comwrote: Tam and Alan, thanks for the package. That solved it. Tam, what do I do with setools-console package? Our Linux Admin was working on a test Apache server. Most of the configuration was done by him, but he left the company. I am picking up the left behind. Coming from the Windows side, I am new to many aspects of Linux. Still learning my rope. The Scientific Linux community has been extremely helpful and resourceful :D. On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: That error means you do not have the prerequisite package installs. Install the package: yum -y install policycoreutils-python Since we are on the SELinux topic, I would recommend you also install: yum -y install setools-console Btw, looking back at your first post about Apache authentication and access deny and allow, how did you manage to get your Apache to work in the first place, especially configuring SELinux settings? On Wed, Apr 11, 2012 at 10:53 AM, Terry Northren tnorth...@gmail.com wrote: Tam, I followed your directions. I ran into an error when I executed the semanage command: semanage fcontext -a -t httpd_sys_content_t public_html Here is my output error: -bash: /usr/sbin/semanage: No such file or directory I went ahead and followed the rest of your tutorial. It worked!! Does this mean I will have to re-configure SELinux after every reboot? On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: Not knowing the configuration of your httpd.conf file and the configuration of the local users' home directory, there is no direct answer. Therefore, my approach to your question is to give you a very basic setup, which would allow users to access files in their home's directory. You can base off of this to make it works on your machine. Before you do anything, backup your httpd.conf file. Even better, do this on a test VM. In the file httpd.conf, change these 2 directives to look like this: #UserDir disabled UserDir *public_html* this enables local users to access html files inside the the *public_html * directory. Let's say we want UserX to have access to his/her home directory: mkdir /home/UserX*/public_html* Then create an html file in the *public_html *directory, Now comes the fun part, permission and SELinux :). Permission: Make sure UserX is the owner of the *public_html* directory and all files within it (hence, recursively). chown userx:userx *public_html* Directory and files need read and execute permission chmod 755 Selinux: public_html and all files within must have one of these context types: httpd_sys_content_t or public_content_rw_t sample command: chcon -R -t httpd_sys_content_t *public_html *then make sure SELinux setting survives reboot, run command: semanage fcontext -a -t httpd_sys_content_t *public_html* verify the directory and do the same to all files inside *public_html*: ll -Z Finally,
Re: iptables + vhost access
Tam, very much appreciated for all the helps. On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: We're glad to be able to help you. The package setools-console is very handy when it comes to setting the SELinux's user, role, and type for a specific file to allow specific access to a specific services. After installing setools-console, you can find out the list of SELinux context type: seinfo -t Or a list of SELinux context user: seinfo -u Or role seinfo -r You will get a long list of context types. An example I've gave you earlier was httpd_sys_content_t. Try this command: seinfo -t | grep httpd_sys Output: httpd_sys_content_t recognize that? :) httpd_sys_htaccess_t httpd_sys_ra_content_t httpd_sys_rw_content_t httpd_sys_script_t httpd_sys_script_exec_t Another example, find the SELinux context type for Samba share file. seinfo -t | grep samba Output: samba_secrets_t samba_unconfined_script_exec_t samba_net_t samba_var_t samba_net_exec_t samba_net_tmp_t samba_unconfined_net_t samba_unconfined_script_t sambagui_exec_t samba_share_t = general samba share privilege samba_initrc_exec_t sambagui_t samba_etc_t samba_log_t Lastly, to make sure your hard-work SELinux survives reboot, run: semanage fcontext -a -t context_type_goes_here_t file_name_goes_here If you assigned context user, then run: semanage fcontext -a -s context_user_goes_here_t -t context_type_goes_here_t file_name Actual example: semanage fcontext -a -s system_u -t samba_share_t /samba/sharedir And of course, you can always have the option to turn off SELinux but I would not recommend it. The only time I turned off SELinux was when I tested a service that kept spitting out permission denied or service not accessible... On Apr 3, zxq9 provided an excellent intro to SELinux. Take a look at his post. Wish you the best. -Tam On Wed, Apr 11, 2012 at 11:32 AM, Terry Northren tnorth...@gmail.comwrote: Tam and Alan, thanks for the package. That solved it. Tam, what do I do with setools-console package? Our Linux Admin was working on a test Apache server. Most of the configuration was done by him, but he left the company. I am picking up the left behind. Coming from the Windows side, I am new to many aspects of Linux. Still learning my rope. The Scientific Linux community has been extremely helpful and resourceful :D. On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: That error means you do not have the prerequisite package installs. Install the package: yum -y install policycoreutils-python Since we are on the SELinux topic, I would recommend you also install: yum -y install setools-console Btw, looking back at your first post about Apache authentication and access deny and allow, how did you manage to get your Apache to work in the first place, especially configuring SELinux settings? On Wed, Apr 11, 2012 at 10:53 AM, Terry Northren tnorth...@gmail.com wrote: Tam, I followed your directions. I ran into an error when I executed the semanage command: semanage fcontext -a -t httpd_sys_content_t public_html Here is my output error: -bash: /usr/sbin/semanage: No such file or directory I went ahead and followed the rest of your tutorial. It worked!! Does this mean I will have to re-configure SELinux after every reboot? On 4/11/12, Tam Nguyen tam8gu...@gmail.com wrote: Not knowing the configuration of your httpd.conf file and the configuration of the local users' home directory, there is no direct answer. Therefore, my approach to your question is to give you a very basic setup, which would allow users to access files in their home's directory. You can base off of this to make it works on your machine. Before you do anything, backup your httpd.conf file. Even better, do this on a test VM. In the file httpd.conf, change these 2 directives to look like this: #UserDir disabled UserDir *public_html* this enables local users to access html files inside the the *public_html * directory. Let's say we want UserX to have access to his/her home directory: mkdir /home/UserX*/public_html* Then create an html file in the *public_html *directory, Now comes the fun part, permission and SELinux :). Permission: Make sure UserX is the owner of the *public_html* directory and all files within it (hence, recursively). chown userx:userx *public_html* Directory and files need read and execute permission chmod 755 Selinux: public_html and all files within must have one of these context types: httpd_sys_content_t or public_content_rw_t sample command: chcon -R -t httpd_sys_content_t *public_html *then make sure SELinux setting survives reboot, run command: semanage fcontext
Re: Smart card manager
On Wednesday 11 April 2012 22:50:23 Akemi Yagi wrote: On Wed, Apr 11, 2012 at 5:06 AM, Novick, Jeffrey L CTR (US) jeffrey.l.novick@mail.mil wrote: I won't have time to mess with it for at least a few days (maybe a week?) but bother me about it early next week and I'll give it another look. Hopefully the build can be simplified. All I can say and do is thank you and I'll poke around to see if I can get esc rebuilt. If I'm successful, I'll post results, otherwise, no update = no success. An update to esc just came out upstream: https://rhn.redhat.com/errata/RHBA-2012-0472.html The ESC utility did not start when the latest 10 series release of the XULRunner runtime environment was installed on the system. This update includes necessary changes to ensure that ESC works as expected with the latest version of XULRunner. (BZ#807264) Hopefully this provides the fix. Akemi Hey awesome! Ah, and that was just pushed today. Hopefully that does the trick. If not then at least this is one step closer to resolution. Thanks for the heads up, Akemi.
Re: Smart card manager
Thank you, still no luck. I managed to get esc-1.1.0-24.el6_2.2.src.rpm and rpmbuild --rebuild esc-1.1.0-24.el6_2.2.src.rpm yum upgrade esc-1.1.0-24.el6_2.x86_64.rpm esc now starts but does not detect my reader. I've tried with the built-in reader, a Dell usb keyboard with a reader and a stand alone usb reader. all with the same results. The only hint of what's wrong now is /var/log/messages shows: pam: gdm-smartcard[2460]: argument card_only is not supported by this module This is with the built in reader: pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: pcscdaemon.c:581:signal_trap() Preparing for suicide pcscd: readerfactory.c:1267:RFCleanupReaders() entering cleaning function pcscd: pcscdaemon.c:531:at_exit() cleaning /var/run pcscd: utils.c:123:StatSynchronize() Can't open /var/run/pcscd.events/event.2412.17011478: Bad file descriptor pcscd: utils.c:123:StatSynchronize() Can't open /var/run/pcscd.events/event.4825.16998508: Bad file descriptor pcscd: utils.c:123:StatSynchronize() Can't open /var/run/pcscd.events/event.3144.17025878: Bad file descriptor pcscd: pcscdaemon.c:506:main() pcsc-lite 1.5.2 daemon ready. pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found pcscd: winscard.c:309:SCardConnect() Reader E-Gate 0 0 Not Found This is with the usb keyboard: kernel: usb 6-1: Product: Dell Smart Card Reader Keyboard kernel: input: Dell Dell Smart Card Reader Keyboard as /devices/pci:00/:00:1d.0/usb6/6-1/6-1:1.0/input/input13 kernel: generic-usb 0003:413C:2101.0002: input,hidraw0: USB HID v1.11 Keyboard [Dell Dell Smart Card Reader Keyboard] on usb-:00:1d.0-1/input0 readerfactory.c:1024:RFInitializeReader() Attempting startup of Dell smart card reader keyboard 00 00 using /usr/lib64/pcsc/drivers/ifd- ccid.bundle/Contents/Linux/libccid.so readerfactory.c:233:RFAddReader() Dell smart card reader keyboard init failed.
Distribution Servers Downtime - 12 hours on May 1 - May 2 2012
Hello, The distribution servers rsync.scientificlinux.org, ftp.scientificlinux.org, ftp1.scientificlinux.org, and ftp2.scientificlinux.org will be going down on: Tuesday May 1, 2012 at 19:00 CDT (Chicago) While this is a few weeks away, we felt it was important to provide this notification early. Affected Machines: * rsync.scientificlinux.org * ftp.scientificlinux.org * ftp1.scientificlinux.org * ftp2.scientificlinux.org Begin Downtime: May 1, 2011 at 19:00 CDT (Chicago) The downtime is expected to last for 12 hours. End Downtime: May 2, 2012 at 07:00 CDT (Chicago) For your local time you can run date -d '2012-05-01 19:00 CDT' Thank you for your patience while we perform this maintenance. Pat Riehecky
Scientific Linux SL 5.8 RC 1 for i386/x86_64 is now available for testing
Scientific Linux SL 5.8 RC 1 for i386/x86_64 is now available for testing. _ DOWNLOAD INFO _ http://ftp.scientificlinux.org/linux/scientific/58/i386/ http://ftp.scientificlinux.org/linux/scientific/58/x86_64/ http://ftp1.scientificlinux.org/linux/scientific/58/i386/ http://ftp1.scientificlinux.org/linux/scientific/58/x86_64/ ftp://ftp.scientificlinux.org/linux/scientific/58/i386/ ftp://ftp.scientificlinux.org/linux/scientific/58/x86_64/ - ISO images are now available - iso/i386/cd SL.58.041112.CD.i386.disc1.iso SL.58.041112.CD.i386.disc2.iso SL.58.041112.CD.i386.disc3.iso SL.58.041112.CD.i386.disc4.iso SL.58.041112.CD.i386.disc5.iso SL.58.041112.CD.i386.disc6.iso SL.58.041112.CD.i386.disc7.iso SL.58.041112.CD.i386.disc8.iso SL.58.041112.CD.i386.md5sum SL.58.041112.CD.i386.SHA1SUM iso/i386/dvd SL.58.041112.DVD.i386.disc1.iso SL.58.041112.DVD.i386.disc2.iso SL.58.041112.DVD.i386.md5sum SL.58.041112.DVD.i386.SHA1SUM iso/x86_64/cd SL.58.041112.CD.x86_64.disc1.iso SL.58.041112.CD.x86_64.disc2.iso SL.58.041112.CD.x86_64.disc3.iso SL.58.041112.CD.x86_64.disc4.iso SL.58.041112.CD.x86_64.disc5.iso SL.58.041112.CD.x86_64.disc6.iso SL.58.041112.CD.x86_64.disc7.iso SL.58.041112.CD.x86_64.disc8.iso SL.58.041112.CD.x86_64.disc9.iso SL.58.041112.CD.x86_64.SHA1SUM SL.58.041112.CD.x86_64.md5sum iso/x86_64/dvd SL.58.041112.DVD.x86_64.disc1.iso SL.58.041112.DVD.x86_64.disc2.iso SL.58.041112.DVD.x86_64.SHA1SUM SL.58.041112.DVD.x86_64.md5sum _ CHANGES compared to SL 58 Beta 2 _ Changed to non-rolling release sl-release-58-4.sl.noarch.rpm sl-release-notes-5.8-1.noarch.rpm yum-conf-58-1.sl.noarch.rpm - Added ERRATA rebuilt from SRPMS compared to SL 58 Beta 2 - i386 esc-1.1.0-13.el5_8.2.i386.rpm freetype-2.2.1-31.el5_8.1.i386.rpm freetype-demos-2.2.1-31.el5_8.1.i386.rpm freetype-devel-2.2.1-31.el5_8.1.i386.rpm libsmbclient-3.0.33-3.39.el5_8.i386.rpm libsmbclient-devel-3.0.33-3.39.el5_8.i386.rpm libtiff-3.8.2-14.el5_8.i386.rpm libtiff-devel-3.8.2-14.el5_8.i386.rpm samba-3.0.33-3.39.el5_8.i386.rpm samba3x-3.5.10-0.108.el5_8.i386.rpm samba3x-client-3.5.10-0.108.el5_8.i386.rpm samba3x-common-3.5.10-0.108.el5_8.i386.rpm samba3x-doc-3.5.10-0.108.el5_8.i386.rpm samba3x-domainjoin-gui-3.5.10-0.108.el5_8.i386.rpm samba3x-swat-3.5.10-0.108.el5_8.i386.rpm samba3x-winbind-3.5.10-0.108.el5_8.i386.rpm samba3x-winbind-devel-3.5.10-0.108.el5_8.i386.rpm samba-client-3.0.33-3.39.el5_8.i386.rpm samba-common-3.0.33-3.39.el5_8.i386.rpm samba-swat-3.0.33-3.39.el5_8.i386.rpm x86_64 esc-1.1.0-13.el5_8.2.x86_64.rpm freetype-2.2.1-31.el5_8.1.i386.rpm freetype-devel-2.2.1-31.el5_8.1.x86_64.rpm libsmbclient-3.0.33-3.39.el5_8.i386.rpm libsmbclient-3.0.33-3.39.el5_8.x86_64.rpm libsmbclient-devel-3.0.33-3.39.el5_8.i386.rpm libsmbclient-devel-3.0.33-3.39.el5_8.x86_64.rpm libtiff-3.8.2-14.el5_8.i386.rpm libtiff-3.8.2-14.el5_8.x86_64.rpm libtiff-devel-3.8.2-14.el5_8.i386.rpm libtiff-devel-3.8.2-14.el5_8.x86_64.rpm samba-3.0.33-3.39.el5_8.x86_64.rpm samba3x-3.5.10-0.108.el5_8.x86_64.rpm samba3x-client-3.5.10-0.108.el5_8.x86_64.rpm samba3x-common-3.5.10-0.108.el5_8.x86_64.rpm samba3x-doc-3.5.10-0.108.el5_8.x86_64.rpm samba3x-domainjoin-gui-3.5.10-0.108.el5_8.x86_64.rpm samba3x-swat-3.5.10-0.108.el5_8.x86_64.rpm samba3x-winbind-3.5.10-0.108.el5_8.i386.rpm samba3x-winbind-3.5.10-0.108.el5_8.x86_64.rpm samba3x-winbind-devel-3.5.10-0.108.el5_8.i386.rpm samba3x-winbind-devel-3.5.10-0.108.el5_8.x86_64.rpm samba-client-3.0.33-3.39.el5_8.x86_64.rpm samba-common-3.0.33-3.39.el5_8.i386.rpm samba-common-3.0.33-3.39.el5_8.x86_64.rpm samba-swat-3.0.33-3.39.el5_8.x86_64.rpm -Connie Sieh -Pat Riehecky
Set path -
I just installed SL-6 on another computer and it's really a bother to have to enter /usr/bin/locate etc. as user bobg. How do I fix that? Bob -- http://www.qrz.com/db/W2BOD box7
Re: Set path -
On 11 April 2012 16:50, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net wrote: I just installed SL-6 on another computer and it's really a bother to have to enter /usr/bin/locate etc. as user bobg. How do I fix that? -ENOINFO A lot more information is required before anyone can attempt to answer this question. What is telling you on the new system that you have to be user bobg. Why is it a problem.. what are you trying to accomplish. -- Stephen J Smoogen. The core skill of innovators is error recovery, not failure avoidance. Randy Nelson, President of Pixar University. Years ago my mother used to say to me,... Elwood, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. —James Stewart as Elwood P. Dowd
Re: Set path -
On 04/11/2012 07:30 PM, Stephen John Smoogen wrote: On 11 April 2012 16:50, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net wrote: I just installed SL-6 on another computer and it's really a bother to have to enter /usr/bin/locate etc. as user bobg. How do I fix that? -ENOINFO A lot more information is required before anyone can attempt to answer this question. What is telling you on the new system that you have to be user bobg. Why is it a problem.. what are you trying to accomplish. Sorry, it appears to be working as expected now. I don't know why I had trouble earlier. Thank you for responding. Bob -- http://www.qrz.com/db/W2BOD box7
