Jump to content
XPEnology Community

shackwove

Member
 View Profile  See their activity

  • Posts

    25

  • Joined

  • Last visited

 Content Type 

Posts posted by shackwove

    Guide to update 4.3-3827-beta7 to Update 6 andHeartbleed fix

    in Legacy (Outdated) Tutorials

    Posted

    We have another update!

     

    Copy and paste the release:

    Version : 4.3-3827 Update 7

     

    (2014/09/10)

    Fixed Issues

     

    Fixed a vulnerability that could allow servers to accept unauthorized access.

     

    Tested and working perfect with this update! :grin:

     

    I'm on Update 2. Do i have to follow the same procedure as the first post to update from Update 2 to Update 7? Or can i just do it the normal way?

    Guide to update 4.3-3827-beta7 to Update 6 andHeartbleed fix

    in Legacy (Outdated) Tutorials

    Posted

    Yes everything is working here :

     

    
fileshanker> pwd
/root
fileshanker> ls -la
drwxr-xr-x    5 root     root          4096 May  7 23:59 .
drwxr-xr-x   24 root     root          4096 May  3 13:47 ..
-rw-------    1 root     root            16 May  7 23:59 .esd_auth
drwx------    2 root     root          4096 May  2 19:42 .gnupg
-rw-r--r--    1 root     root           366 Feb 14 12:08 .profile
drwx------    2 root     root          4096 May  8 00:43 .pulse
-rw-------    1 root     root           256 May  7 23:59 .pulse-cookie
drwxr-xr-x    2 root     root          4096 May  2 19:15 pci
-rw-r--r--    1 root     root        249507 Feb 22 11:45 syno-i686-bootstrap_1.2-7_i686.xsh
fileshanker> openssl version
WARNING: can't open config file: /usr/syno/ssl/openssl.cnf
OpenSSL 1.0.1g-fips 7 Apr 2014

     

    The dpkg_upgrade.log :

     

    2014/05/02 16:40:28      ===========[-x /volume1//@smallupd@te_deb/smallupdate_4.3-3827-s2_all.deb /smallUpd@teTempFolder]=====
2014/05/02 16:42:16      ===========[-i /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ]===========
Authenticating /smallupd@te/iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb ...
passed
Selecting previously unselected package iptables-1.4.2-bromolow-bin.
(Reading database ... 0 files and directories currently installed.)
Unpacking iptables-1.4.2-bromolow-bin (from .../iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb) ...
Setting up iptables-1.4.2-bromolow-bin (1.4.2-3827-s1) ...
2014/05/02 16:42:17      ===========[-i /smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s1_all.deb ]===========
Authenticating /smallupd@te/libsynosdk-bromolow-bin_4.3-3827-s1_all.deb ...
passed

etc etc

     

    A quick google search leads me to believe that this is a permissions issue. Maybe try to run the update as admin? Also did you run the commands as root?

     

    Also, these are strange to me :

     

    gpg: keyblock resource `/var/services/homes/root/.gnupg/secring.gpg': No such file or directory

     

    because i don't have these directories either. I don't have User Homes enabled though, maybe you do and it's causing issues? Control Panel > Users > User Home

     

    p.s tu peux aussi ouvrir un thread dans la section FR du forum, même si ton anglais n'est pas mauvais à mon avis.

    Brute force ssh attacks

    in Archives

    Posted

    For an added layer you can forward a port in your router to your SSH port on DSM.

     

    Your router's config would look like this :

     

    External port : 35775

    Internal port : 22

     

    now you only have to connect to it using ssh -p 35775 user@ip

     

    You can also disable the ability to ssh as root, this is common practice to any ssh box, you can then login as say "admin" and then switch to root if you have to. DSM is particular tho and we have to change something first or we won't be able to switch user afterwards.

     

    1. Login as ssh root@dsm
2. Change permissions on /bin/su with chmod a+s /bin/su
3. Try it, login with ssh admin@dsm
4. Type su
5. Enter password and type whoami  < this should return "root"
6. Disable root login in /etc/ssh/sshd_config 
as root user do vi /etc/ssh/sshd_config
locate the line that says #PermitRootLogin yes
Press insert and edit it so it looks like "PermitRootLogin no"
Press escape and type ":wq" and press enter
7. In the web GUI, Control Panel > Terminal > Disable SSH and apply > Enable SSH and apply
8. Try to connect as root, it shouldn't let you anymore, so connect as admin

     

    That's it, nobody can longer connect to your DSM as root but you still have root capabilities!

     

     

     

     

     

    Place your cursor over this line

    Migration DSM 5.0-4458 rien dans file Station

    in Archives

    Posted

    Bonjour à tous

     

    J'ai sauté le pas je suis passé de la version 4.3 à la version gnoboot DSM 5.0-4458 et depuis dans File Station je ne vois pas plus mes fichiers.

    Le volume existe mais rien dans file station

    Je n'ai fait aucune mise à jour, j'ai juste suivi le tuto comme toute le monde,

     

    Pour Information en telnet je vois bien le volume avec mes fichiers

     

    Merci de votre aide

     

    Panneau de configuration > Dossier Partagé

     

    Tu devrais voir tout tes dossiers, il suffit de redonner les droits à ton compte

    Chose which DSM version to boot?

    in Archives

    Posted

    Kind of solved.

     

    I installed Trantor's 4.3 beta7 + update 2 on volume1. Did a clean installation over 5.0 4458.

     

    With 4.3 running great i then plugged in the 2 4TB drives (now that's where it would boot to the DSM installation that was present on the 4tb volume when i tried gnoboot) but with Trantor's it booted onto my recently installed 4.3!

     

    Upon booting, DSM immediately recognized volume2 and mounted the share i had created on it.

     

    8wSYbJZ.png

     

    Clicked on repair and i was done.

     

    xlXOHIA.png

     

    This is exactly how i wanted it to behave so i'm pretty happy about that :razz: Too bad i won't be using 5.0 but that's fine.

    Synology Download Station for Chrome

    in Archives

    Posted

    I like the download button it adds under youtube videos :smile:

     

    I got the button but my download fails?

     

    its accepted, any ideas?

     

    I remember it didn't work everytime so you might want to try again.

     

    First try, asking me to install python :

     

    FLolDnP.png

     

    After installing python all is working! :

     

    i4SGfYi.png

    Installer le DSM sur la clé USB [résolu]

    in Archives

    Posted

    Je trouve que c'est le plus gros désavantage d'utiliser DSM, j'aimerais avoir plus de contrôle sur la gestion de l'installation :evil: Par exemple ça serait bien de pouvoir simplement ajouter des disques qui contiennent déjà du data sans devoir formater. Ou de simplement ajouter des disques et les formater en ext4 ou ntfs pour pouvoir les déplacer facilement d'une machine à une autre.

    repasser en 4.3

    in Archives

    Posted

    Le probleme c'est que je je ne peut plus faire les updates en 4.3, il veut me passer en dsm5, éxiste il un fichier .pat déja en derniere version de 4.3 de disponible ?

     

    Même en choisissant "Les mise à jours importantes seulement" comme dans ce screen? J'ai aussi passé de 5.0 à 4.3 il n'y a pas 3 heures et j'ai pu updater à Update 2 :eek:

     

    CkYUmy7.png

     

     

    As-tu fais clean installation ou as tu migré?

    Drivers requests for DSM 5.2

    in DSM 5.2 and earlier (Legacy)

    Posted

    Just dropping by to let you know that i just installed beta7 easily over gnoboot's 5.0 4458. I had the option to migrate but i didn't since i wanted a fresh start. Chose clean installation and everything couldn't have gone more smoothly! On first boot all my shares were mounted and readily accessible. Thanks for the work, i really do appreciate it.

    Chose which DSM version to boot?

    in Archives

    Posted

    Hey all

     

    In order for you to better understand my setup let me do a quick recap.

     

    1. Been running XPenology Trantor's 4.1 for over a year with the main volume being 3x 1TB in SHR (raid 5).

    2. I recently added 2x 4TB drives, created a disk group with the two drives and then a volume (volume2 - SHR raid 1).

    3. Wanting to upgrade to DSM 5.0 i first backed up what i wanted to keep from volume1 onto volume2.

    4. Unplugged the 2 4TB drives (My thinking was to set aside the data in case the update goes wrong, i had been waiting to get these drives specifically to upgrade!)

    5. Installed DSM 5.0 using gnoboot.

    6. I wasn't able to "Migrate" during the install but the data/shares on my volume1 are still intact and accessible. 5.0 working great!

     

    Here's where it gets interesting :grin:

     

    7. Plugged the 2x 4TB back in.

    8. With the 2x 4TB plugged in, still using the same gnoboot usb key, it nows boot into my OLD 4.1 install!

    9. Wondering what happened to the 5.0 install i unplugged the 4TBs again and what do you know the 5.0 install works just fine.

     

    So i can effectively boot one or the other now but is there a way to control on which disk or volume to boot on? I'm assuming the bootable kernel looks for the most recent version on the disks and boot that one? I was hoping to keep the data on both volumes for a while in case something goes wrong with this 5.0 install.

     

    I think next time i want to do something like this i'll just add a disk but initialize it and then mount and copy to it using ssh, what do you think?

    XPEnology DS3612xs DSM 4.1 build 2668++ (repack v1.3a)

    in DSM 5.2 and earlier (Legacy)

    Posted

    I'm running DS3612xs DSM 4.1 build 2668++ (more hardware) on a Pentium-D with 1gb of DDR2 and it's working great, no performance issues whatsoever.

     

    However the OS becomes unresponsive from time to time, the PC doesn't shutdown but i'm unable to perform any actions such as using the web client, pinging the PC or detecting it via synology assistant. The only solution i've found when this happens is to hard shut down the PC with the power button which i really want to avoid.

     

    So yeah, there it is, not sure if it's a network error (cutting the communication between the nas and router) or a software issue. I don't even know where to start to troubleshoot the issue.

     

    Admin edit: Moved to viewtopic.php?f=2&t=937

×
×
  • Create New...