Loumeer

New Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Loumeer

  • Rank
    Newbie
  1. Beware my synology was compromised

    Thanks for the link but I would like to add on to your post. I was running version 4.2 so it seems that both DSM 4.2 and 4.3 (pre update 4) are vulnerable to this sort of attack.
  2. Hello everybody, For the past couple of days I have been noticing some wierd behavior of my xpenology install. Today I did some digging and realized there was a process call Synodns making my CPU clock at 100% constantly. I am not sure how it was done and what methods were used by apparently my synology install was compromised and "synodns" was installed. From what I can tell "synodns" is a renamed Cpu miner: "Running /usr/syno/bin/synodns --help does indeed show it is a miner. Usage: minerd [OPTIONS] Options: -a, --algo=ALGO specify the algorithm to use scrypt scrypt(1024, 1, 1) (default) sha256d SHA-256d -o, --url=URL URL of mining server (default: http://127.0.0.1:9332/) -O, --userpass=U:P username:password pair for mining server -u, --user=USERNAME username for mining server -p, --pass=PASSWORD password for mining server ... snip ... -V, --version display version information and exit -h, --help display this help text and exit" See also: http://www.reddit.com/r/synology/commen ... edsynodns/ http://forum.synology.com/enu/viewtopic ... ns#p301696 I am not the most advanced in internet security so if one of you guys could let me know what I can do to better protect myself from stuff like this in the future I would appreciate it.
  3. [SOLVED] Install on vmware ESXI

    I did this exact thing, but when I installed the vmtools, the system crashed and it ended up marking the volume as "Crashed" within Synology. I had to backup my data through a SSH session and start over. Instead what I did was create a script on the Cyberpower VM that SSH's to the Synology VM, shuts it down and then SSH's to the ESXi instance and shuts it down. The script works well, but even though it looks like I'm getting a clean shutdown, I still get a "Crashed" volume. Even if I do a clean shutdown from the GUI, my volume gets marked as "Crashed." Fortunately this time, the volume goes back to "Normal" after a couple reboots, but all my folders and settings are gone. Thankfully I've backed up the configuration and just o a restore. I had actually visited the forum today to ask this very question - does anyone else get a "Crashed" volume when they shut down their VM? May I ask which Cyberpower UPS you have? I am looking at buying one and unsure which one to pick up.
  4. [SOLVED] Install on vmware ESXI

    I know there was some discussion in the first few pages about getting IPKG installed with open-vm-tools. I was wondering if anybody has been able to get it to work and enable esxi to gracefully shutdown thier Xpenology in case of a power failure. I am putting together an ESXI server for myself and I think I have figured out what I want to do. -Cyberpower UPS set up with Business Edition (run by CentOS) to send shutdown command to ESXI -ESXI then gracefully shuts down all the VMs. The last piece of the puzzle for me to figure out is installing VM tools (or possibly open vm-tools) on the Xpenology. Last I have seen didi was working on getting open vm-tools working and said there was some work to be done. Is there an update on getting it working? I appreciate all the work many of you have put into this project to make it a reality.