VeNoM

Try renaming /bin/umount

Try installing sancome's version and look in /proc/kallsyms for funcSYNODiskRetryReport. If is't there, he has the solution. sancome's version still uses the mount for pcidevices ? cat /proc/kallsyms | grep -i funcSYNODiskRetryReport How did you fixed the pat file to bypass the checksum ?

Also this build should work with LinuxKVM/WmWare for easier testing

The mount fix doesn't work anymore ? I will test my dsmgeneric kernel module with the new protection.

I will try to use the default kernel built by synology with modules for my VM to see if it passes the checksum. I do not have the time right now to investigate this. Anyone else ?

Apparently Synology introduced a new checksum in 4458. When loaded, the synobios creates /proc/syno_cpu_arch. Jan 1 00:00:01 syslog: util_fhost.c:1204 Serial number is 0 out of size Jan 1 00:00:02 syslaog: format start, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:02 syslog: ninstaller.c:717 Dev: sda, DiskPath: /dev/sda, Check Partitions: 1 Jan 1 00:00:02 syslog: ninstaller.c:577 failed to get upnpmodelname from [/tmpMnt1234/etc.defaults/synoinfo.conf]. Jan 1 00:00:02 syslog: ninstaller.c:584 failed to get buildnumber from [/tmpMnt1234/etc.defaults/VERSION]. Jan 1 00:00:02 syslog: ../lib

I have set up a VM for 5.0 testing and I have some issues. - funcSYNODiskRetryReport unknown symbol in synobios - the checksum for pat contents fails for some reason Kernel patch --- a/drivers/ata/libata-core.c +++ b/drivers/ata/libata-core.c @@ -7414,7 +7414,7 @@ int (*funcSYNODeepSleepEvent)(unsigned int, unsigned int) = NULL; EXPORT_SYMBOL(funcSYNODeepSleepEvent); -#ifdef MY_DEF_HERE +#if (defined(MY_DEF_HERE) || defined(XPENOLOGY)) int (*funcSYNOSendEboxRefreshEvent)(int portIndex) = NULL; EXPORT_SYMBOL(funcSYNOSendEboxRefreshEvent); #endif --- a/drivers/ata/sata_mv.c +++ b/dri

I got a new kernel working including patches + my dsmgeneric module. file arch/x86/boot/bzImage arch/x86/boot/bzImage: Linux kernel x86 boot executable bzImage, version 3.2.40 (aaa@bbb) #1 SMP Thu Mar 13 14:40:01 EET 2014, RO-rootFS, swap_dev 0x3, Normal VGA I see that rd.gz in the DS3612xs is not a gzip file. Any ideeas ? LE : lzma/cpio mv rd.gz rd.lzma lzma -d rd.lzma cpio -idv < rd

Any new security checks in 5.0 ?

Can somebody with Trantor's build give me the output of df -h ?

You should wait to see if this update is safe for Trantor's build. If it's ok, then : Go to update, click download. Then go to scheduled tasks and create a custom task : sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 mv /autoupd@te.info1 /autoupd@te.info Run this task. Then go to update and hit the update button.

DSM 4.3-3810 Update 2 available. I just updated and with my mod it seems ok.

3810 Update 1 is available. Be carefull. (2013/11/20) Compatibility and Installation DSM 4.3-3810 Update 1 can only be installed on Synology products running DSM 4.3-3810 via DSM Update. Please log in to DSM and go to Control Panel > DSM Update to install the update. Fixed Issues Fixed a system security issue. Improved the compatibility of file uploading with Internet Explorer 11 in File Station.

We can maybe block this with iptables ? No. Syno can detect this mod in the next update by simply checking /proc/mounts and just do a "umount /proc/bus/pci"

Or simply change the boot loader by adding parameters to the kernel and comment cksum, vender and hw_model. title SYNOLOGY root (hd0,1) # cksum /grub_cksum.syno # vender /vender show # hw_model kernel /zImage root=/dev/md0 ihd_num=0 netif_num=2 syno_hw_version=DS3612xs mac1=00113208d68a mac2=00113208d68b mac3=004d9469c492 mac4=004d9469c493 sn=B3J4N00001 initrd /rd.gz