mackevin11

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mackevin11

  • Rank
    Newbie
  1. DSM 5.0-4458 Update 2 works perfectly here! First used trantor, now using gnoBoot, works pretty nice actually:D
  2. When I do ip.adr.ess.ss:port (replaced by my ip/port ofcourse) I got: Uh-oh, something went wrong: tls: oversized record received with length 20291 And without the portnr: dial tcp ip.adr.ess.ss:443: i/o timeout
  3. Yes, but popular 'good' sites, like YouTube, Facebook, Apple, ect are not affected. I was planning to do an upgrade to DSM5.1 and this doesn't stop me from doing that. Now I use an http connection which isn't encrypted at all, no problems so far. I think there will maybe be an update soon (DSM5.2 or so?) which will probably fix the 'bug'.
  4. Hi guys, My HDD doesn't want to sleep anymore. I tried a lot of things (removing packages, change configurations, change settings) nothing worked. Even with the internet cable unplugged it won't sleep anymore. I want to reset the OS, in other words, reinstall the software but without losing data. I searched the internet, but I can only find that I've to press the reset-button on my Synology NAS. Ofcourse I don't have a reset-button on my custom-build XPEnology NAS. How can I reset it then?
  5. Ohw, sorry then... But can you tell me if 3810 v4 is safe to use now, or does it have the same bug? I get 3-5 different people that are trying to connect via SSH every day... The log tells me 'login fail' so at least they fail, but I'm still worried about it...
  6. A week ago, I was running DSM4.3-3810 v1 but then I got that stupid 'lolz' virus (similar to the PWNED virus). I've successfully removed it and have updated my DS to DSM4.3-3810 v4. The security fix is only available in 4.3-3827, or not? Is there already a trantor 4.3-3827 version for my XPEnology NAS?
  7. I finally succeed to update to 4.3-3810 v4. Is this version safe or do I need to update to 4.3-3827? I do not want that virus again on my NAS! What I did (for other people having issues, its already described in parts in this thread, but again:) - Download the DSM 4.3-3810 v4 package from Trantor (see first post). - Unzip it (Mac: Stuffit Expander, Windows: WinRAR) - Make a directory on volume 1, called 'public' (as described) You can do this with SSH or in the GUI SSH: mkdir /volume1/public GUI: >ControlCenter >SharedFolders >Create (name it public, give at least th
  8. Successfully stopped all process called lolzm, lolzb, synolog (killall lolzm lolzb synolog) Successfully deleted S99p.sh (main script that start 'lolzm' 'lolzb' and 'synolog' when booting) Successfully located and deleted the /lolz folder and its contents. Successfully deleted /opt/bin (where some modified versions of ls kill top ps where located) Successfully deleted /etc/ld.so.preload Successfully moved /usr/syno/synoman/webman/modules/ControlPanel/modules/upgrade2.cgi Successfully moved /usr/syno/synoman/webman/modules/ResourceMonitor/rsrcmonitor3.cgi Successfully moved /usr/syno/sy
  9. Successfully stopped all process called lolzm, lolzb, synolog (killall lolzm lolzb synolog) Successfully deleted S99p.sh (main script that start 'lolzm' 'lolzb' and 'synolog' when booting) Successfully located and deleted the /lolz folder and its contents. Successfully deleted /opt/bin (where some modified versions of ls kill top ps where located) Successfully deleted /etc/ld.so.preload Successfully moved /usr/syno/synoman/webman/modules/ControlPanel/modules/upgrade2.cgi Successfully moved /usr/syno/synoman/webman/modules/ResourceMonitor/rsrcmonitor3.cgi Successfully moved /usr/syno/sy
  10. @cquote I can not find the lolz folder. It seems like there is no lolz folder. Appelboom> ls / bin etc.defaults lib64 opt sbin tmp var.defaults volumeUSB1 dev initrd lost+found proc scripts usr volume1 etc lib mnt root sys var volume2 Appelboom> ls -lha /proc/11073 | grep exe lrwxrwxrwx 1 root root 0 Feb 18 12:03 exe -> /lolz/lolzm Appelboom> ls -lha /proc/11073/exe/ ls: cannot access /proc/11073/exe/: Not a directory Appelboom> whereis lolzm -ash: whereis: not found The process is coming from a folder th
  11. @cquote I can not find the lolz folder. It seems like there is no lolz folder. Appelboom> ls / bin etc.defaults lib64 opt sbin tmp var.defaults volumeUSB1 dev initrd lost+found proc scripts usr volume1 etc lib mnt root sys var volume2 Appelboom> ls -lha /proc/11073 | grep exe lrwxrwxrwx 1 root root 0 Feb 18 12:03 exe -> /lolz/lolzm Appelboom> ls -lha /proc/11073/exe/ ls: cannot access /proc/11073/exe/: Not a directory Appelboom> whereis lolzm -ash: whereis: not found The process is coming from a folder th
  12. I'm also infected by the virus. I've got the problem that when it slowed down, I thought about restarting the NAS. Now, when I want to login by web (port 5000, 5001), I can't... 'System is starting services, please wait.'. After 8 hours still the same message. I've read threads on the internet about it, it seems to be a mining-virus. It is not the 'PWNED' virus, but, similar, the 'lolz' virus. Got three different processes (or maybe even more); synolog, lolzm, lolzb I've tried to trace & delete the virus, but I can't even trace it:( Appelboom> pidof lolzm 11073 11072 1
  13. I'm also infected by the virus. I've got the problem that when it slowed down, I thought about restarting the NAS. Now, when I want to login by web (port 5000, 5001), I can't... 'System is starting services, please wait.'. After 8 hours still the same message. I've read threads on the internet about it, it seems to be a mining-virus. It is not the 'PWNED' virus, but, similar, the 'lolz' virus. Got three different processes (or maybe even more); synolog, lolzm, lolzb I've tried to trace & delete the virus, but I can't even trace it:( Appelboom> pidof lolzm 11073 11072 1