Re: Fedora 20 + stunnel crashing
Fixed by adding "fips = no" to the stunnel config file. I don't remember what version was of stunnel I had before but apparently 4.56 enables it by default. On Sun, Jan 5, 2014 at 5:01 PM, slamp slamp wrote: > Hello All, > > Anyone able to use stunnel successfully in Fedora 20? It has been working > for me for awhile prior to upgrading. > > Stunnel starts up fine, but as soon as it is used, it crashes but no > indication as to why. > > I really only use stunnel to interface my sendmail with my ISP, if there > is a simple way of doing this with sendmail, I'll remove stunnel. > > I believe I am using a simple config: > > $ cat /etc/stunnel/stunnel.conf > ; Some performance tunings > socket = l:TCP_NODELAY=1 > socket = r:TCP_NODELAY=1 > > ; Some debugging stuff useful for troubleshooting > debug = 7 > output = /var/log/stunnel.log > > ; Use it for client mode > client = yes > verify = 0 > > ; Service-level configuration > > [pseudo-ssmtp] > accept = relay-domain:2525 > connect = smtp.verizon.net:465 > > > -- > logs: > > 2014.01.05 15:51:42 LOG7[613:3071158144]: Clients allowed=500 > 2014.01.05 15:51:42 LOG5[613:3071158144]: stunnel 4.56 on > i686-redhat-linux-gnu platform > 2014.01.05 15:51:42 LOG5[613:3071158144]: Compiled/running with OpenSSL > 1.0.1e-fips 11 Feb 2013 > 2014.01.05 15:51:42 LOG5[613:3071158144]: Threading:PTHREAD > Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS Auth:LIBWRAP > 2014.01.05 15:51:42 LOG5[613:3071158144]: Reading configuration from file > /etc/stunnel/stunnel.conf > 2014.01.05 15:51:42 LOG5[613:3071158144]: FIPS mode is enabled > 2014.01.05 15:51:42 LOG7[613:3071158144]: Compression not enabled > 2014.01.05 15:51:42 LOG7[613:3071158144]: Snagged 64 random bytes from > /dev/urandom > 2014.01.05 15:51:42 LOG7[613:3071158144]: PRNG seeded successfully > 2014.01.05 15:51:42 LOG6[613:3071158144]: Initializing service > [pseudo-ssmtp] > 2014.01.05 15:51:43 LOG7[613:3071158144]: SSL options set: 0x0004 > 2014.01.05 15:51:43 LOG5[613:3071158144]: Configuration successful > 2014.01.05 15:51:43 LOG7[613:3071158144]: Service [pseudo-ssmtp] (FD=12) > bound to 127.0.0.1:2525 > 2014.01.05 15:51:43 LOG7[737:3071158144]: Created pid file > /var/run/stunnel.pid > 2014.01.05 16:21:57 LOG7[737:3071158144]: Service [pseudo-ssmtp] accepted > (FD=3) from 127.0.0.1:34007 > 2014.01.05 16:21:57 LOG7[737:3078183744]: Service [pseudo-ssmtp] started > 2014.01.05 16:21:57 LOG7[737:3078183744]: Waiting for a libwrap process > 2014.01.05 16:21:57 LOG7[737:3078183744]: Acquired libwrap process #0 > 2014.01.05 16:21:57 LOG7[737:3078183744]: Releasing libwrap process #0 > 2014.01.05 16:21:57 LOG7[737:3078183744]: Released libwrap process #0 > 2014.01.05 16:21:57 LOG7[737:3078183744]: Service [pseudo-ssmtp] permitted > by libwrap from 127.0.0.1:34007 > 2014.01.05 16:21:57 LOG5[737:3078183744]: Service [pseudo-ssmtp] accepted > connection from 127.0.0.1:34007 > 2014.01.05 16:21:57 LOG6[737:3078183744]: connect_blocking: connecting > 206.46.232.100:465 > 2014.01.05 16:21:57 LOG7[737:3078183744]: connect_blocking: s_poll_wait > 206.46.232.100:465: waiting 10 seconds > 2014.01.05 16:21:57 LOG5[737:3078183744]: connect_blocking: connected > 206.46.232.100:465 > 2014.01.05 16:21:57 LOG5[737:3078183744]: Service [pseudo-ssmtp] connected > remote server from 172.16.133.25:56457 > 2014.01.05 16:21:57 LOG7[737:3078183744]: Remote socket (FD=14) initialized > 2014.01.05 16:21:57 LOG7[737:3078183744]: SNI: sending servername: > smtp.verizon.net > 2014.01.05 16:21:57 LOG7[737:3078183744]: SSL state (connect): > before/connect initialization > 2014.01.05 16:21:57 LOG7[737:3078183744]: SSL state (connect): SSLv3 write > client hello A > 2014.01.05 16:21:57 LOG7[737:3078183744]: SSL state (connect): SSLv3 read > server hello A > 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate > verification: depth=3, /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, > Inc./CN=GTE CyberTrust Global Root > 2014.01.05 16:21:57 LOG6[737:3078183744]: CERT: Verification not enabled > 2014.01.05 16:21:57 LOG5[737:3078183744]: Certificate accepted: depth=3, > /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust > Global Root > 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate > verification: depth=3, /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, > Inc./CN=GTE CyberTrust Global Root > 2014.01.05 16:21:57 LOG6[737:3078183744]: CERT: Verification not enabled > 2014.01.05 16:21:57 LOG5[737:3078183744]: Certificate accepted: depth=3, > /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust > Global Root > 2014.01.05 16:21:57 LOG7[737:3078183744]
Fedora 20 + stunnel crashing
Hello All, Anyone able to use stunnel successfully in Fedora 20? It has been working for me for awhile prior to upgrading. Stunnel starts up fine, but as soon as it is used, it crashes but no indication as to why. I really only use stunnel to interface my sendmail with my ISP, if there is a simple way of doing this with sendmail, I'll remove stunnel. I believe I am using a simple config: $ cat /etc/stunnel/stunnel.conf ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = /var/log/stunnel.log ; Use it for client mode client = yes verify = 0 ; Service-level configuration [pseudo-ssmtp] accept = relay-domain:2525 connect = smtp.verizon.net:465 -- logs: 2014.01.05 15:51:42 LOG7[613:3071158144]: Clients allowed=500 2014.01.05 15:51:42 LOG5[613:3071158144]: stunnel 4.56 on i686-redhat-linux-gnu platform 2014.01.05 15:51:42 LOG5[613:3071158144]: Compiled/running with OpenSSL 1.0.1e-fips 11 Feb 2013 2014.01.05 15:51:42 LOG5[613:3071158144]: Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS Auth:LIBWRAP 2014.01.05 15:51:42 LOG5[613:3071158144]: Reading configuration from file /etc/stunnel/stunnel.conf 2014.01.05 15:51:42 LOG5[613:3071158144]: FIPS mode is enabled 2014.01.05 15:51:42 LOG7[613:3071158144]: Compression not enabled 2014.01.05 15:51:42 LOG7[613:3071158144]: Snagged 64 random bytes from /dev/urandom 2014.01.05 15:51:42 LOG7[613:3071158144]: PRNG seeded successfully 2014.01.05 15:51:42 LOG6[613:3071158144]: Initializing service [pseudo-ssmtp] 2014.01.05 15:51:43 LOG7[613:3071158144]: SSL options set: 0x0004 2014.01.05 15:51:43 LOG5[613:3071158144]: Configuration successful 2014.01.05 15:51:43 LOG7[613:3071158144]: Service [pseudo-ssmtp] (FD=12) bound to 127.0.0.1:2525 2014.01.05 15:51:43 LOG7[737:3071158144]: Created pid file /var/run/stunnel.pid 2014.01.05 16:21:57 LOG7[737:3071158144]: Service [pseudo-ssmtp] accepted (FD=3) from 127.0.0.1:34007 2014.01.05 16:21:57 LOG7[737:3078183744]: Service [pseudo-ssmtp] started 2014.01.05 16:21:57 LOG7[737:3078183744]: Waiting for a libwrap process 2014.01.05 16:21:57 LOG7[737:3078183744]: Acquired libwrap process #0 2014.01.05 16:21:57 LOG7[737:3078183744]: Releasing libwrap process #0 2014.01.05 16:21:57 LOG7[737:3078183744]: Released libwrap process #0 2014.01.05 16:21:57 LOG7[737:3078183744]: Service [pseudo-ssmtp] permitted by libwrap from 127.0.0.1:34007 2014.01.05 16:21:57 LOG5[737:3078183744]: Service [pseudo-ssmtp] accepted connection from 127.0.0.1:34007 2014.01.05 16:21:57 LOG6[737:3078183744]: connect_blocking: connecting 206.46.232.100:465 2014.01.05 16:21:57 LOG7[737:3078183744]: connect_blocking: s_poll_wait 206.46.232.100:465: waiting 10 seconds 2014.01.05 16:21:57 LOG5[737:3078183744]: connect_blocking: connected 206.46.232.100:465 2014.01.05 16:21:57 LOG5[737:3078183744]: Service [pseudo-ssmtp] connected remote server from 172.16.133.25:56457 2014.01.05 16:21:57 LOG7[737:3078183744]: Remote socket (FD=14) initialized 2014.01.05 16:21:57 LOG7[737:3078183744]: SNI: sending servername: smtp.verizon.net 2014.01.05 16:21:57 LOG7[737:3078183744]: SSL state (connect): before/connect initialization 2014.01.05 16:21:57 LOG7[737:3078183744]: SSL state (connect): SSLv3 write client hello A 2014.01.05 16:21:57 LOG7[737:3078183744]: SSL state (connect): SSLv3 read server hello A 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate verification: depth=3, /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust Global Root 2014.01.05 16:21:57 LOG6[737:3078183744]: CERT: Verification not enabled 2014.01.05 16:21:57 LOG5[737:3078183744]: Certificate accepted: depth=3, /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust Global Root 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate verification: depth=3, /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust Global Root 2014.01.05 16:21:57 LOG6[737:3078183744]: CERT: Verification not enabled 2014.01.05 16:21:57 LOG5[737:3078183744]: Certificate accepted: depth=3, /C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust Global Root 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate verification: depth=2, /C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root 2014.01.05 16:21:57 LOG6[737:3078183744]: CERT: Verification not enabled 2014.01.05 16:21:57 LOG5[737:3078183744]: Certificate accepted: depth=2, /C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate verification: depth=1, /O=Cybertrust Inc/CN=Cybertrust Public SureServer SV CA 2014.01.05 16:21:57 LOG6[737:3078183744]: CERT: Verification not enabled 2014.01.05 16:21:57 LOG5[737:3078183744]: Certificate accepted: depth=1, /O=Cybertrust Inc/CN=Cybertrust Public SureServer SV CA 2014.01.05 16:21:57 LOG7[737:3078183744]: Starting certificate verif
Fedora 18 latest kernel 3.8.1 no f2fs support
Apparently you are allowed to install f2fs-tools but the kernel itself does not have f2fs support. Am I correct or am I missing something? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F15 preupgrade seems not to work with /boot on RAID
On Fri, May 27, 2011 at 11:12 AM, George Avrunin wrote: > On Tue, 24 May 2011 22:12:39 -0400, Matthew Saltzman > wrote: > >> All packages downloaded, but preupgrade reported an error on the console >> I ran it from regarding the fact that /boot was on a software RAID >> device. The GUI, on the other hand, appeared to finish normally and >> reported that the installation would start on reboot. It didn't. >> >> So is there a reason preupgrade can't work with /boot on RAID when the >> original (F12, IIRC, upgraded to F14) installation did? And why doesn't >> the GUI detect the error and fail? >> > > I'm seeing the same problem--GUI doesn't complain, but doesn't work and > preupgrade-cli complains. Any suggestions? > > George > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > i downloaded the dvd, booted to it, and followed the upgrade procedure there. worked fine, i didn't install grub on my boot device though since it is already there. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: About start system without X in Fedora 15
On Tue, May 17, 2011 at 7:49 AM, JB wrote: > Manuel Trujillo (TooManySecrets toomany.net> writes: > >> >> Hi. >> >> Before systemd, you could start a system without the X putting a "3" >> at end of kernel line in grub. How I can make the same in Fedora 15? I >> tried the same but not work (I think it is for the new systemd start >> system). >> >> Please, excuse me my bad english. >> >> Regards. >> > > https://fedoraproject.org/wiki/Systemd#Boot_Kernel_Command_Line > > JB > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > how do i switch to the multi-user.target when X fails to start? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: udev rules + adb insufficient permission
On Sat, Jan 22, 2011 at 5:16 PM, Tom Horsley wrote:
> On Sat, 22 Jan 2011 17:01:00 -0500
> slamp slamp wrote:
>
>> did anything change on how udev creates devices for usb's?
>> specifically debugging device for adb?
>
> I thought they had been eradicating all the google android
> patches in the kernel and wot not because google won't
> wiggle the rubber chicken three times the exact way the
> kernel developers want them to. Perhaps it fell victim
> to that?
>
> P.S. Where do you find info on android development on
> fedora? I've been considering if I want to start dabbling
> in it, but 99% of the info is for windows and (barf) eclipse.
> --
i am no developer. i really only use adb to push tweaks to my Droid. i
do not have one site i go to for info, i just search google and the
forums (droidforums.net).
for those curious and also having the issue i had, here's the udev rule.
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct} =="41db",
MODE="0666"
The idVendor and the idProduct is seen when running lsusb:
$ lsusb
Bus 002 Device 003: ID 22b8:41db Motorola PCS Motorola Droid (USB Debug)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
udev rules + adb insufficient permission
did anything change on how udev creates devices for usb's? specifically debugging device for adb? i dont know when this changed but all of the sudden i did not have permission to my adb device. i had to create a udev rule to specify the proper permission. i am running fedora 14 x86 with all the latest updates. i checked my yum log and did not see anything pertaining to udev. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Blank box on KDE desktop
On Sun, Dec 5, 2010 at 6:41 PM, Manuel Escudero wrote: > > > 2010/12/5 slamp slamp >> >> I am running Fedora 14 with KDE. For some reason there is a blank box >> on my desktop. It is not a widget because I cannot remove it. It seems >> to only happen with the effects turned on for KDE. Anyone know what >> this is? >> >> -- >> users mailing list >> users@lists.fedoraproject.org >> To unsubscribe or change subscription options: >> https://admin.fedoraproject.org/mailman/listinfo/users >> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >> > > To solve this (and keep your Effects turned on) in Desktop Effects>Advanced > Disable the > functionality comprobation, change to Xrender instead of OpenGL and in > general use: "Instant" > instead of normal for the animation speed. > > -- > <-Manuel Escudero-> > Linux User #509052 > @GWave: jmlev...@googlewave.com > @Blogger: http://www.blogxenode.tk/ (Xenode Systems Blog) > PGP/GnuPG: DAE3 82E9 D68E 7AE4 ED31 1F8F 4AF4 D00C 50E7 ABC6 > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > changing from opengl to xrender disables the effects i like (blur, desktop cube animation, wobble windows). thank you for your input.. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Blank box on KDE desktop
I am running Fedora 14 with KDE. For some reason there is a blank box on my desktop. It is not a widget because I cannot remove it. It seems to only happen with the effects turned on for KDE. Anyone know what this is? <>-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora 13 + nvidia + kde
On Sat, May 29, 2010 at 12:05 PM, Matthew Saltzman wrote: > On Sat, 2010-05-29 at 11:06 -0400, slamp slamp wrote: >> On Wed, May 26, 2010 at 11:01 PM, slamp slamp wrote: >> > I had a problem logging into KDE after an upgrade from Fedora 12. I >> > have akmod-nvidia installed. To fix the login issue I had to remove >> > /usr/lib/libGL.so.1 as I was seeing ksmserver: symbol lookup error: >> > /usr/lib/libGL.so.1 in my xessions log file. >> > >> > anyone know a better fix? the nvidia driver provides its own >> > libGL.so.1. not sure how to get KDE to use that instead of the one >> > provided by mesa-libgl. >> > >> >> Are there anyone experiencing this? when i try to remove >> mesa-libGL-7.8.1-6.fc13.i686 a ton of other packages i need will also >> get removed. > > The rpmfusion RPMs for the nVidia proprietary driver handle this issue > seamlessly. > funny thing is i am using the rpmfusion nvidia drivers. # uname -r 2.6.33.4-95.fc13.i686.PAE # rpm -qa |grep nvidia nvidia-settings-1.0-4.fc13.i686 kmod-nvidia-2.6.33.4-95.fc13.i686-195.36.24-1.fc13.6.i686 nvidia-xconfig-1.0-2.fc13.i686 kmod-nvidia-2.6.33.4-95.fc13.i686.PAE-195.36.24-1.fc13.6.i686 xorg-x11-drv-nvidia-libs-195.36.24-1.fc13.i686 xorg-x11-drv-nvidia-195.36.24-1.fc13.i686 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora 13 + nvidia + kde
On Wed, May 26, 2010 at 11:01 PM, slamp slamp wrote: > I had a problem logging into KDE after an upgrade from Fedora 12. I > have akmod-nvidia installed. To fix the login issue I had to remove > /usr/lib/libGL.so.1 as I was seeing ksmserver: symbol lookup error: > /usr/lib/libGL.so.1 in my xessions log file. > > anyone know a better fix? the nvidia driver provides its own > libGL.so.1. not sure how to get KDE to use that instead of the one > provided by mesa-libgl. > Are there anyone experiencing this? when i try to remove mesa-libGL-7.8.1-6.fc13.i686 a ton of other packages i need will also get removed. For the moment I linked this problematic file to the one nvidia provides. # ls -l /usr/lib/libGL.so* lrwxrwxrwx 1 root root 10 May 26 21:56 /usr/lib/libGL.so -> libGL.so.1 lrwxrwxrwx 1 root root 26 May 29 11:01 /usr/lib/libGL.so.1 -> /usr/lib/nvidia/libGL.so.1 -rwxr-xr-x. 1 root root 495448 Apr 30 20:39 /usr/lib/libGL.so.1.2 -rwxr-xr-x 1 root root 705700 Sep 17 2008 /usr/lib/libGL.so.177.67 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Fedora 13 + nvidia + kde
I had a problem logging into KDE after an upgrade from Fedora 12. I have akmod-nvidia installed. To fix the login issue I had to remove /usr/lib/libGL.so.1 as I was seeing ksmserver: symbol lookup error: /usr/lib/libGL.so.1 in my xessions log file. anyone know a better fix? the nvidia driver provides its own libGL.so.1. not sure how to get KDE to use that instead of the one provided by mesa-libgl. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Will Firefox 3.6 be pushed?
works fine for me using rawhide. On Sun, Jan 31, 2010 at 1:00 PM, john wendel wrote: > On 01/31/2010 07:54 AM, Mail Lists wrote: >> On 01/31/2010 04:14 AM, Kevin Kofler wrote: >> >>> A less dangerous solution is to use Remi Collet's repository at >>> http://blog.famillecollet.com/ . Remi actually builds the current Firefox >>> for F12, so you don't end up with a dependency mess. >> >> >> Or perhaps just download it direct from mozilla.org ( assuming theirs >> is a static build) >> >>> But a word of warning about Firefox 3.6: don't upgrade to 3.6 (no matter >>> how) if you use the OpenJDK plugin, as it has not been ported yet. >> >> > > Has anyone been successful with the Mozilla version of Firefox 3.6? I > tried it, but found it unusable on my F11 box. > > Regards, > > John > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
