June 2009 - openSUSE Security - openSUSE Mailing Lists

Re: [opensuse-security] Signature verification failed for file 'repomd.xml' from repository 'openSUSE-11.1-Update'
by Thomas R. Jones 05 Oct '09

05 Oct '09

Data corruption failure during transfer? Works on my system. thomas@bodhisattva:~/Desktop> sudo zypper refresh root's password: Repository 'openSUSE BuildService - GNOME:Community' is up to date. Repository 'openSUSE-11.1-Non-Oss' is up to date. Repository 'openSUSE-11.1-Oss' is up to date. Retrieving repository 'openSUSE-11.1-Update' metadata [done] Building repository 'openSUSE-11.1-Update' cache [done] Retrieving repository 'Packman Repository' metadata [done] Building repository 'Packman Repository' cache [done] Repository 'VideoLan Repository' is up to date. Repository 'thomasrjones' is up to date. All repositories have been refreshed. thomas@bodhisattva:~/Desktop> On Wed, 2009-04-01 at 17:41 +0200, Michael Ströder wrote: > HI! > > What's up with this? > > -------------------- snip -------------------- > # zypper refresh > Repository 'openSUSE-11.1-Non-Oss' is up to date. > Signature verification failed for file 'repomd.xml' from repository > 'openSUSE-11.1-Update'. > Warning: This might be caused by a malicious change in the file! > Continuing might be risky. Continue anyway? [yes/NO]: > -------------------- snip -------------------- > > Ciao, Michael. -- To unsubscribe, e-mail: opensuse-security+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-security+help(a)opensuse.org

5 6

Re: [opensuse-security] SSH access refused for legitimate user under heavy load
by Pieter Van Gorp 08 Jun '09

08 Jun '09

Dear Bujdosó, thanks for your reply. > _If_ you think that the firewall is responsible for the timeouts you might > take a look at your /var/log/firewall In the firewall log, I have no entries for the machine from which the connections were initiated (and refused to). How should I interpret this observation? > Then you can look at > /etc/sysconfig/SuSEfirewall2 > config file in the "FW_SERVICES_ACCEPT_EXT" section. The hitcount/blockseconds identifiers do not occur in this file... Should I investigate other paths than the firewall? Any clues? Thanks a lot for your advice, Pieter -- To unsubscribe, e-mail: opensuse-security+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-security+help(a)opensuse.org

3 6

Re: [opensuse-security] SSH access refused for legitimate user under heavy load
by Pieter Van Gorp 06 Jun '09

06 Jun '09

Thanks Joost, I'll play around with those options. Especially the "-timeout" approach is simple to tryout. Further suggestions about the cause of the problem are still welcome of course. Thanks again, Pieter On Sat, Jun 6, 2009 at 3:03 PM, Joost van der Lugt<jvdl(a)sendmail.com> wrote: > You may want to check: > > - timeout setting in the client > - running ssh with higher priority on the server > - and/or use *less* ssh commands when the load is high > > Pieter Van Gorp wrote: >> Dear Bujdosó, >> thanks for your reply. >> >> >>> _If_ you think that the firewall is responsible for the timeouts you might >>> take a look at your /var/log/firewall >>> >> In the firewall log, I have no entries for the machine from which the >> connections were initiated (and refused to). How should I interpret >> this observation? >> >> >>> Then you can look at >>> /etc/sysconfig/SuSEfirewall2 >>> config file in the "FW_SERVICES_ACCEPT_EXT" section. >>> >> The hitcount/blockseconds identifiers do not occur in this file... >> >> Should I investigate other paths than the firewall? Any clues? >> >> Thanks a lot for your advice, >> Pieter >> > > -- To unsubscribe, e-mail: opensuse-security+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-security+help(a)opensuse.org

1 0

[opensuse-security] SSH access refused for legitimate user under heavy load
by Pieter Van Gorp 06 Jun '09

06 Jun '09

Hi all, I use SSH forced commands and key authentication to execute remote commands from a web application on a computation server. I use this approach on ubuntu 8.10, Fedora and Suse linux enterprise server 10. The SSH commands are sent based on a cron job that executes the remote commands each minute. The amount of SSH commands sent depends on the requests that the web application had written to a database. Most of the time, the cron job executes *no* commands. However, under heavy load, it can execute to 7 SSH commands each minute. It turns out that on Suse, the SSH server (or firewall, or ...) already refuses access when about three SSH commands need to be sent. The error message sent to CRON is as follows: > ssh: connect to host <themachinedns> port 22: Connection timed out (I have omitted the domain name of the actual machine here). I guess this indicates on Suse the Firewall (iptables?) blocks connections, right? Can you please help me figure out how to overcome this problem? Please note that I have not configured iptables before... Kind regards and thanks in advance, Pieter -- To unsubscribe, e-mail: opensuse-security+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-security+help(a)opensuse.org

1 0