April 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] did I caught a virus?
by C. Brouerius van Nidek 12 Apr '14

12 Apr '14

Since some 12 hours I cannot connect to google. With google download site for earth I get "404. That's an error. That's all we know." google.com shows me the message to update the outdated flashplayer. Did not know google com used a flashplayer. Searches with google as search engine are stuck and do not show anything else as the turning cursor as if to show that it is busy. Changed my search engine into ixquick and can for now at least do websearches. The choice to remind me later was easy. I choose not to install and got the question if I would save a setup.exe As web browser I use mainly Chromium. Have KDE updated with Tumbleweed and have not installed any software outside openSUSE sources.. Ran yesterday rkhunter. No problems. Where should I start looking for this problem? -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 13.1 (i586) Kernel: 3.14.0-23.gfa168d7-default KDE Development Platform: 4.12.4 21:18pm up 5:01, 3 users, load average: 1.20, 1.12, 1.18 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 20

[opensuse] SuSE 12.1 and Heartbleed Bug
by Peter Maffter 12 Apr '14

12 Apr '14

Hello, I am still running OpenSuSE 12.1 with 1.0.0k-34.20.1 openssl So I guess I won't get any update. Does compilation of a new version (described here: http://dl4oce.wordpress.com/2014/04/08/openssl-bug-heartbleed-beheben/ ) help? BR Pete -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

19 36

[opensuse] Heartbleed Testing
by Greg Freemyer 12 Apr '14

12 Apr '14

I ran away to update a virtual server I run. Remember on all your openSUSE 12.3 AND 13.1 machines: sudo zypper in -t patch openSUSE-2014-277 Use "sudo rpm -qa | grep ssl" to confirm you have the latest patched version. This is the package list from the security announcement: - openSUSE 13.1 (i586 x86_64): libopenssl-devel-1.0.1e-11.32.1 libopenssl1_0_0-1.0.1e-11.32.1 libopenssl1_0_0-debuginfo-1.0.1e-11.32.1 openssl-1.0.1e-11.32.1 openssl-debuginfo-1.0.1e-11.32.1 openssl-debugsource-1.0.1e-11.32.1 - openSUSE 13.1 (x86_64): libopenssl-devel-32bit-1.0.1e-11.32.1 libopenssl1_0_0-32bit-1.0.1e-11.32.1 libopenssl1_0_0-debuginfo-32bit-1.0.1e-11.32.1 - openSUSE 13.1 (noarch): openssl-doc-1.0.1e-11.32.1 - openSUSE 12.3 (i586 x86_64): libopenssl-devel-1.0.1e-1.44.1 libopenssl1_0_0-1.0.1e-1.44.1 libopenssl1_0_0-debuginfo-1.0.1e-1.44.1 openssl-1.0.1e-1.44.1 openssl-debuginfo-1.0.1e-1.44.1 openssl-debugsource-1.0.1e-1.44.1 - openSUSE 12.3 (x86_64): libopenssl-devel-32bit-1.0.1e-1.44.1 libopenssl1_0_0-32bit-1.0.1e-1.44.1 libopenssl1_0_0-debuginfo-32bit-1.0.1e-1.44.1 - openSUSE 12.3 (noarch): openssl-doc-1.0.1e-1.44.1 My questions below: On Thu, Apr 10, 2014 at 10:39 AM, Christopher Myers <cmyers(a)mail.millikin.edu> wrote: > Well... I applied the patches mentioned in the email I'd sent a few minutes ago to my 12.2 box, and after doing so, the heartbleed python script no longer flags it: > > user@computer:~/Desktop/heartbleed> python ssltest.py my.server > Connecting... > Sending Client Hello... > Waiting for Server Hello... > ... received message: type = 22, ver = 0302, length = 58 > ... received message: type = 22, ver = 0302, length = 1286 > ... received message: type = 22, ver = 0302, length = 525 > ... received message: type = 22, ver = 0302, length = 4 > Sending heartbeat request... > Unexpected EOF receiving record header - server closed connection > No heartbeat response received, server likely not vulnerable > > So, I'm guessing it's ok? No odd issues as of yet. It it just HTTPS connections we have to worry about. I read that SSH is safe because it doesn't use it does not use the TLS protocol that is the core of the vulnerability. For secure FTP, it uses SSH so that should be safe as well. What about POP / IMAP / SMTP? Do any of those have susceptibility to heartbleed? Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] YaST hangs on downloading repo metadata, and has to be killed.
by Carlos E. R. 11 Apr '14

11 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 +++······················ 2014-04-11 21:46:28 <1> Telcontar(3305) [zypp++] MediaMultiCurl.cc(doGetFileCopy):1319 dest: /var/adm/mount/AP_0xiYzbce/repodata/repomd.xml 2014-04-11 21:46:28 <1> Telcontar(3305) [zypp++] MediaMultiCurl.cc(doGetFileCopy):1320 temp: /var/adm/mount/AP_0xiYzbce/repodata/repomd.xml.new.zypp.YY 2014-04-11 21:46:28 <1> Telcontar(3305) [zypp++] MediaCurl.cc(doGetFileCopyFile):1379 /repodata/repomd.xml 2014-04-11 21:46:28 <1> Telcontar(3305) [zypp++] MediaCurl.cc(doGetFileCopyFile):1389 URL: http://opensuse-guide.org/repo/13.1/repodata/repomd.xml 2014-04-11 21:46:28 <1> Telcontar(3305) [Ruby] modules/PackageCallbacks.rb:2028 Downloading http://opensuse-guide.org/repo/13.1/repodata/repomd.xml to 2014-04-11 21:46:28 <1> Telcontar(3305) [Ruby] modules/Progress.rb:622 Resetting the subprogressbar... ······················++- And it sits there for ever. No network activity. Clicking "Skip autorefresh" does nothing. I have to click on the X of the window to kill it. Then the log shows this: +++······················ 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/tmp/TmpDir.cEbPAr 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.cEbPAr{d 0700 0/0} 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/tmp/zypp.6lHmry 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.6lHmry{d 0700 0/0} 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] ZYppFactory.cc(_openLockFile):166 Open lockfile /var/run/zypp.pid 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] ZYppFactory.cc(~ZYppGlobalLock):115 Cleanned lock file. (3305) 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] ZYppFactory.cc(_closeLockFile):184 Close lockfile /var/run/zypp.pid 2014-04-11 21:51:52 <1> Telcontar(3305) [Pkg] PkgFunctions.cc(~PkgFunctions):148 Releasing the repo manager... 2014-04-11 21:51:52 <1> Telcontar(3305) [Pkg] PkgFunctions.cc(~PkgFunctions):155 Releasing the zypp pointer... 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] RpmDb.cc(closeDatabase):734 Calling closeDatabase: RpmDb[V4(X--)V3(-B-): '(/)/var/lib/rpm'] 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] librpmDb.cc(blockAccess):328 Block access 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] RpmDb.cc(closeDatabase):765 closeDatabase: RpmDb[NO_INIT] 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] TargetImpl.cc(~TargetImpl):815 Targets closed 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] RpmDb.cc(~RpmDb):268 ~RpmDb() 2014-04-11 21:51:52 <1> Telcontar(3305) [zypp] RpmDb.cc(~RpmDb):271 ~RpmDb() end 2014-04-11 21:51:52 <1> Telcontar(3305) [Pkg] PkgFunctions.cc(~PkgFunctions):157 Zypp pointer released ······················++- Yet the process remains running: +++······················ root 3282 0.0 0.0 11968 1736 pts/1 S 21:45 0:00 | \_ /bin/bash /sbin/yast2 --qt sw_single root 3305 1.3 2.7 910632 227832 pts/1 Sl 21:45 0:05 | | \_ /usr/lib/YaST2/bin/y2base sw_single qt ······················++- and I have to kill it: +++······················ Telcontar:~ # kill 3305 YaST got signal 15 at YCP file /usr/share/YaST2/modules/Progress.rb:664 Telcontar:~ # /sbin/yast2: line 375: 3305 Terminated $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Invalid snapshot ''. [4]+ Exit 143 yast2 --qt sw_single Telcontar:~ # ······················++- and I get a "/var/log/YaST2/signal" signal file. +++······················ === 2014-04-11 21:53:47 +0200 === YaST got signal 15 at YCP file /usr/share/YaST2/modules/Progress.rb:664 Liberating suppressed debugging messages: End of suppressed debugging messages Backtrace: (use c++filt to demangle) /usr/lib64/liby2.so.4(_Z20signal_log_backtracev+0x18)[0x7fb79444c358] /usr/lib64/liby2.so.4(_Z14signal_handleri+0x14f)[0x7fb79444c54f] /lib64/libc.so.6(+0x358d0)[0x7fb7927998d0] /lib64/libc.so.6(__poll+0x2d)[0x7fb792842b3d] /usr/lib64/libcurl.so.4(+0x3bc09)[0x7fb78fb78c09] /usr/lib64/libcurl.so.4(curl_multi_wait+0x270)[0x7fb78fb73190] /usr/lib64/libcurl.so.4(curl_easy_perform+0xdf)[0x7fb78fb6c3cf] /usr/lib64/libzypp.so.1306(_ZNK4zypp5media9MediaCurl17doGetFileCopyFileERKNS_10filesystem8PathnameES5_P8_IO_FILERNS_8callback10SendReportINS0_22Downloa /usr/lib64/libzypp.so.1306(_ZNK4zypp5media14MediaMultiCurl13doGetFileCopyERKNS_10filesystem8PathnameES5_RNS_8callback10SendReportINS0_22DownloadProgres /usr/lib64/libzypp.so.1306(_ZNK4zypp5media9MediaCurl11getFileCopyERKNS_10filesystem8PathnameES5_+0x79)[0x7fb7902a7a79] /usr/lib64/libzypp.so.1306(_ZNK4zypp5media9MediaCurl7getFileERKNS_10filesystem8PathnameE+0xe1)[0x7fb79029b061] /usr/lib64/libzypp.so.1306(_ZNK4zypp5media12MediaHandler11provideFileENS_10filesystem8PathnameE+0x2d)[0x7fb79027b72d] /usr/lib64/libzypp.so.1306(_ZNK4zypp5media11MediaAccess11provideFileERKNS_10filesystem8PathnameE+0x33)[0x7fb790274673] /usr/lib64/libzypp.so.1306(_ZNK4zypp5media12MediaManager11provideFileEjRKNS_10filesystem8PathnameE+0x5e)[0x7fb7902c3aee] /usr/lib64/libzypp.so.1306(+0x277fb0)[0x7fb7903f3fb0] /usr/lib64/libzypp.so.1306(_ZN4zypp14MediaSetAccess7provideEN5boost8functionIFvjRKNS_10filesystem8PathnameEEEERKNS_15OnMediaLocationENS_4base5FlagsINS0 /usr/lib64/libzypp.so.1306(_ZN4zypp14MediaSetAccess11provideFileERKNS_10filesystem8PathnameEjNS_4base5FlagsINS0_17ProvideFileOptionEEE+0xf4)[0x7fb7903f /usr/lib64/libzypp.so.1306(_ZN4zypp4repo3yum10Downloader6statusERNS_14MediaSetAccessE+0x9e)[0x7fb79031132e] /usr/lib64/libzypp.so.1306(_ZN4zypp11RepoManager4Impl24checkIfToRefreshMetadataERKNS_8RepoInfoERKNS_3UrlENS0_24RawMetadataRefreshPolicyE+0x7f2)[0x7fb79 /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN12PkgFunctions14SourceLoadImplER11PkgProgress+0x6e9)[0x7fb790926a89] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN12PkgFunctions22SourceStartManagerImplERK10YCPBooleanR11PkgProgress+0x12a)[0x7fb7909296ca] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN12PkgFunctions18SourceStartManagerERK10YCPBoolean+0x1e7)[0x7fb790929a47] /usr/lib64/YaST2/plugin/libpy2Pkg.so.2(_ZN13Y2PkgFunction12evaluateCallEv+0xb30e)[0x7fb79095302e] /usr/lib64/ruby/vendor_ruby/2.0.0/x86_64-linux/yastx.so(+0xa1f2)[0x7fb790fe61f2] /usr/lib64/libruby2.0.so.2.0(+0x1635a4)[0x7fb791c965a4] /usr/lib64/libruby2.0.so.2.0(+0x1700c6)[0x7fb791ca30c6] /usr/lib64/libruby2.0.so.2.0(+0x166a15)[0x7fb791c99a15] /usr/lib64/libruby2.0.so.2.0(+0x16b857)[0x7fb791c9e857] /usr/lib64/libruby2.0.so.2.0(+0x16bdd0)[0x7fb791c9edd0] /usr/lib64/libruby2.0.so.2.0(+0x16c0cc)[0x7fb791c9f0cc] /usr/lib64/libruby2.0.so.2.0(+0x1635a4)[0x7fb791c965a4] /usr/lib64/libruby2.0.so.2.0(+0x1700c6)[0x7fb791ca30c6] /usr/lib64/libruby2.0.so.2.0(+0x166a8c)[0x7fb791c99a8c] /usr/lib64/libruby2.0.so.2.0(+0x16b857)[0x7fb791c9e857] /usr/lib64/libruby2.0.so.2.0(+0x16c36c)[0x7fb791c9f36c] /usr/lib64/libruby2.0.so.2.0(+0x16d6be)[0x7fb791ca06be] /usr/lib64/libruby2.0.so.2.0(rb_funcall+0xd1)[0x7fb791ca0ca1] /usr/lib64/YaST2/plugin/libpy2lang_ruby.so(_ZN5YRuby10callClientERKSs+0x1e5)[0x7fb791fa1565] /usr/lib64/YaST2/plugin/libpy2lang_ruby.so(_ZN21Y2RubyClientComponent12doActualWorkERK7YCPListP11Y2Component+0x184)[0x7fb791f9f2d4] /usr/lib64/liby2.so.4(main+0xf59)[0x7fb794446d59] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fb792785be5] /usr/lib/YaST2/bin/y2base[0x4006f9] ······················++- I had to disable autorefresh of that repo. But even if a repo fails to download something, it should not hang yast for ever. Is a bug report wanted? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNISfAACgkQtTMYHG2NR9U+yACeO+HN38KwzstglWKqgwe5XDtH QCkAoIrbXvzfjH0aFN3N/5nSfRXBfEW8 =3fug -----END PGP SIGNATURE-----

1 0

[opensuse] KDE SC 4.13 availability for openSUSE
by Raymond Wooninck 11 Apr '14

11 Apr '14

Dear openSUSE KDE users, As you might know, KDE Upstream is planning to release the new 4.13 release around Wednesday 16 April. The openSUSE KDE Community team is planning to have the openSUSE KDE packages ready by that time, however the update will not become directly available for all users. As promised with the release of the KDE:Current repository, major updates will first be tested for a period of 1 to 2 weeks before they will become available in the KDE:Current repository. This is not to pester the users, but to ensure that nothing is forgotten, no sudden major bug, etc. When you are using the KDE:Current repository then upgrades should go smooth to ensure the best experience. As that the new 4.13 release already had quite some testing by openSUSE users brave enough to use the KDE:Distro:Factory, I am pretty sure that the KDE:Current repository will have the KDE SC 4.13 release available around Saturday 26 April. This would give us time enough to prepare the packages (and ensuring a smooth upgrade) as well to test the 4.13 release itself by a number of people for major regressions. I am sure that all of you are anxious to try out the new KDE SC 4.13 release, but I guess one week more wouldn't make that much difference if we can prevent. My assumptions are that those that couldn't wait already switched to KDE:Distro:Factory and are testing now the 4.13 RC. As that I am not subscribed to the openSUSE mailinglist, I would like to ask you to copy me directly on your replies. Thank you Regards Raymond openSUSE KDE Community team member -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] software.opensuse.org - bitcoin
by Andrew English 11 Apr '14

11 Apr '14

How do I get my openSUSE machine on there under the openSUSE 13.1 contributing? Second I had a look at the source for bitcoind/bitcoin-qt 0.9.1 (they found an SSL bug in 0.9.0) but it doesn't exchange how to compile it. It looks like it assume you already know how to make bitcoind and bitcoin-qt for your OS. :o( Take care, Andrew "Do not dwell in the past, do not dream of the future, concentrate the mind on the present moment." -Buddha -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Fwd: Heartbleed Bug
by Greg Freemyer 10 Apr '14

10 Apr '14

On Thu, Apr 10, 2014 at 11:57 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > > > On Thu, Apr 10, 2014 at 11:14 AM, Lew Wolfgang <wolfgang(a)sweet-haven.com> wrote: >> >> On 04/10/2014 07:36 AM, jdd wrote: >>> >>> Le 10/04/2014 16:31, Lew Wolfgang a écrit : >>> >>>> What can those users running openSuSE 12.2 do to fix the problem >>>> short of upgrading to 13.1? >>> >>> >>> let them run. I have servers running 12.1 because I never has time to update them. Of course nothing that have any value >>> >>> I had some years ago a 2010 server running debian 3.0, with very old hardware and a config nobody could uderstand why it worked... I replaced it when the hardware failed >>> >>> as far as I can see, the traffic of any of these servers is so low I don't thing they are compromised :-( - but I may be wrong >>> >> >> But my understanding is (hope I'm wrong!) that both servers and clients >> are affected. If you have a vulnerable SSL library on your home desktop >> and you happen to visit a compromised web server, that web server can >> exfiltrate all your RAM-resident data without your knowledge. >> >> I think that openSuSE 12.1 is okay and was never vulnerable. 12.2 and >> up are vulnerable. >> >> Regards, >> Lew > > > Lew, > > I hope your wrong. I've only read about server side issues so far. That is bad enough. > > Greg Shit, you're not wrong. http://www.theregister.co.uk/2014/04/10/many_clientside_vulns_in_heartbleed… At least for openSUSE users the policy is that openSSL never be hardlinked to an app. Thus patching the library and restarting any apps using it will address the vulnerability. But it means the historical window of opportunity was huge. And for anyone that runs windows, they often hardlink in the openSSL library instead of using a shared DLL. That means that every application will need to be checked and upgraded if needed in windows. Can I crawl back in a hole now? Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Bootnet Windigo in light + How to give away passwords
by Dsant 10 Apr '14

10 Apr '14

Eset has plublished a very detailed paper on the Bootnet Windigo : it try every simple root password and infect Linux server : http://www.welivesecurity.com/2014/03/18/operation-windigo-the-vivisection-… Read it, very clever ! • Totally silent if tcpdump detected (« promiscuous mode ») • The same if “support” “webmaster” or “webmin” found • Use file names stating with space (!) or dot • Send stolen passwords using DNS request (!) • gmail, yahoo… mailboxes tests before real spamming • Malware « regions » : US Canada UK ect… / rest of the world ( depending if SMTP port is generally blocked) So my question is : which hardware tool can we use for double authentication compatible with OpenSUSE ? Should be : cheap, light. USB. Open (no closed dongle black-box). Compatible with every password forms (web sites, KDE lock, even console "init 3" login...) -- : ` _..-=-=-=-.._.--. Dsant, from Lyon, France `-._ ___,..-'" -~~` __') forum(a)votreservice.com jgs `'"---'"`>>"'~~"~"~~>>'` =====================```========```======== -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Nimbus fonts in openSUSE 12.2
by Istvan Gabor 10 Apr '14

10 Apr '14

Hello: I used to have Nimbus fonts in earlier openSUSE versions. In Libreoffice (oS 12.2) font selector these fonts (Nimbus Roman No9 L, Nimbus Sans L) are missing. Package "ghostscript-fonts-std - Basic Fonts for Ghostscript" is installed and supply URW-Nimbus fonts in /usr/share/ghostscript/fonts. Are these font not the same required for Libreoffice? How could I get these fonts for LO? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

Re: [opensuse] Curl errors using Yast and zypper
by ianseeks 10 Apr '14

10 Apr '14

On Wednesday 09 Apr 2014 23:20:18 Freek de Kruijf wrote: > Op woensdag 9 april 2014 13:55:48 schreef ianseeks: > > Hi > > > > Does anyone know where i can search for a reason for the following errors > > in zypper and yast? If its a bug, do you know where i should post it i.e. > > zypper, yast, curl? > > The repos that fail are random and selecting retry cures the issue. It > > happens in Yast as well when i select to install/update software except > > this time i correctly get pop-up dialogs saying it failed. > > I never (or very very rarely) had this issue before Opensuse 12 and i've > > had in every release since up and including opensuse 13.1 > > > > thanks > > > > regards > > > > Ian > > Do you have, by any chance, an IPv6 network you connect to? Its disabled on my system and the router is also using IPv4 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0