remove pinning.. apt-get update, then install libssl by dpkg. not libssl-dev.. first libssl1.0.0_1.0.1t-1+deb8u8_amd64.deb then the matching libssl-dev..
Posts by Tom-i
-
-
No problem. I know that package pinning is great but often breaks after a while cause of changed dependencies, updated dependencies, missing dependencies.. and so on
Take your time to sort out. But i think i will not be the only one with problem in this case..
Thanks for holding hand and taking time.. -
Yes Sure Debian Jessie.
What i can say that imscp reconfiguration worked some weeks ago, So there seems to have something changed with the package dependencies.
I know that you did not change but something changed so it broke. -
I only installed the mailman plugin. This set a strange package pinning and sources.list (mix of jessie and stretch) which of course installed some not matching packages. Thats it. I myself surely did not anything strange in that direction.
But no Problem. I got it. Works again and everything is cool again. Keep on.
-
Thank you.
Got it sorted out. First i had to manual downgrade to libssl-1.0.0, then remove perl-modules and nearly all perl stuff.. mysql-server.. etc
Then i was able to run installer without errors.
Strange situation and for a "normal" user "the end".
I am experiencedwith those things but such a situation should not happen with just a "plugin" that was activated.
-
Package Installation fails with this error:
Code- ...php5.6-curl is already the newest version.php5.6-fpm is already the newest version.php5.6-gd is already the newest version.php5.6-gmp is already the newest version.php5.6-imap is already the newest version.php5.6-intl is already the newest version.php5.6-json is already the newest version.php5.6-mbstring is already the newest version.php5.6-mcrypt is already the newest version.php5.6-mysql is already the newest version.php5.6-opcache is already the newest version.php5.6-pspell is already the newest version.php5.6-xml is already the newest version.php5.6-zip is already the newest version.nginx-full is already the newest version.Some packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help to resolve the situation:The following packages have unmet dependencies: libssl-dev : Depends: libssl1.0.0 (= 1.0.1t-1+deb8u8) but 1.0.2l-1~bpo8+1 is to be installedE: Unable to correct problems, you have held broken packages.[ERROR] autoinstaller::Functions::build: An error occurred while performing build steps
Installed libssl-dev from backports but i think the package pinning depends on the version from stable as i have seen in a commit on github..After that i removed /etc/apt/preferences.de/mailman..
Then i had to install cpan integer..
Than it failed with this error:
Display MoreCode- locales-all is already the newest version (2.24-11+deb9u3).
- libcrypt-blowfish-perl is already the newest version (2.14-1+b4).
- libcrypt-eksblowfish-perl is already the newest version (0.009-2+b2).
- libcrypt-rijndael-perl is already the newest version (1.13-1+b2).
- libdate-simple-perl is already the newest version (3.0300-1+b3).
- libdatetime-perl is already the newest version (2:1.42-1).
- libdbd-mysql-perl is already the newest version (4.041-2).
- libdbi-perl is already the newest version (1.636-1+b1).
- libjson-perl is already the newest version (2.90-1).
- libnet-dns-perl is already the newest version (1.07-1).
- libnet-libidn-perl is already the newest version (0.12.ds-2+b3).
- libunix-mknod-perl is already the newest version (0.04-1+b5).
- libxml-parser-perl is already the newest version (2.44-2+b1).
- libxml-simple-perl is already the newest version (2.22-1).
- tar is already the newest version (1.29b-1.1).
- libperl5.24 is already the newest version (5.24.1-3+deb9u3).
- libperl5.24 set to manually installed.
- perl is already the newest version (5.24.1-3+deb9u3).
- Some packages could not be installed. This may mean that you have
- requested an impossible situation or if you are using the unstable
- distribution that some required packages have not yet been created
- or been moved out of Incoming.
- The following information may help to resolve the situation:
- The following packages have unmet dependencies:
- bind9 : Depends: bind9utils (= 1:9.10.3.dfsg.P4-12.3+deb9u4) but 1:9.9.5.dfsg-9+deb8u15 is to be installed
- devscripts : Depends: python3:any (>= 3.3.2-2~)
- libssl-dev : Depends: libssl1.0.0 (= 1.0.1t-1+deb8u8) but 1.0.2l-1~bpo8+1 is to be installed
- E: Unable to correct problems, you have held broken packages.
- [ERROR] autoinstaller::Functions::build: An error occurred while performing build steps
-
Ok i understand. From can be spoofed.
Problem solved. Thanks for your time.
-
Oh ich habe es gerade gefunden. Ich habe bisher immer nur nach clientdomain.de geschaut. Es ist mir aber gerade aufgefallen das vu2019 garnicht zu clientdomain.de gehört... sondern zu clientdomain2.de ... Somit einem anderen User, welcher natürlich auch auf den ersten Blick direkt infiziert scheint.
@Nuxwin : I have overlooked that vu2019 does not belong to clientdomain.de . clientdomain.de is vu2021.. The sender is constructed as [email protected].. But vu2019 is clientdomain2.de, another client. There seems to be a check missing if the user belongs to the domain.. Could you check this?
-
Ich habe jetzt chmod 000 auf den htdocs Ordner gesetzt. Die mailq selektiv bereinigt. Leider gehts munter weiter.
Manuell habe ich die Php Files des Wordpress des Kunden geprüft. Keinerlei Infektionen feststellbar.
-
@Nuxwin yes it seems there is a mail with severeal cc generated.this domain is a wordpress. client says he installed all updates. beside those POST Requests which appear not in the same time as the mails are send i have not seen any activity in this moment. It appears after some sekonds/minutes. I also rebootet the machine already to kill anything that could be loaded to ram. I will investigate it further today.
@biologist Ich denke auch das die da irgendwas in den Ram/SHM laden was dann getriggert wird. Ich bin da eigentlich relativ fit. Aber die Header sagen leider nicht viel mehr aus als der Log. Definitiv nicht direkt aus Php.