Jump to content
XPEnology Community

Release Candidate 7.1.1 is out


pocopico
 Share

Recommended Posts

Release 7.1.1. is out and based on some quick research of the pat files, the update should be possible. Until all aspects of the upgrade are covered, please hold your upgrades to 7.1.1 RC

 

https://www.synology.com/en-us/releaseNote/DSM?model=DS3622xs%2B#7_1

 

@fbelavenuto @jumkey@yanjun@Peter Suh @Orphée

 

 

Facts so far :

 

- The PAT file can be extracted using the same procedure. 

- The modules version are the same

- The kernel version is still the same

- File structure looks the same

 

 

Edited by pocopico
  • Like 6
  • Thanks 1
Link to comment
Share on other sites

Several people are updating ARPL to this new release. I wanted to take the opportunity to give a message for users:


Before upgrading to a new release or a new smallupdate, wait for testing information on the forum, as a new release can have a lot of changes and break your installation.
This is the reason for not leaving automatic update by default.

 

  • Like 4
Link to comment
Share on other sites

13 minutes ago, Orphée said:

This vulnerability fix list is heavy... this update will be a must.

 

It seems that there are users who skip RC and wait for the official release.
By the way, it took more than a month from the last 7.1.0-42621 RC version to the official version.
If we wait for this period, there is a risk that we may be exposed to vulnerabilities for a long time, so we are deeply concerned.
Is there any chance that this vulnerability will be corrected with 7.1.0-42661 update 5?

Link to comment
Share on other sites

4 hours ago, Peter Suh said:

DS1621+ was selected as a sample model and TCRP, jun mode, and 7.1.1 RC update were performed.
There seems to be nothing wrong with it.
The jot mode seems to work well too. Let's try it further.

 

2022-08-10-8-39-29.png

 

 

7.1.1 RC was immediately used when requesting a DSM pat file in DS3622xs+ jot mode built with m shell.
I immediately entered TC Linux and processed postupdate.
By the way, the PC shut down after a few seconds of nic response on reboot.

Edited by Peter Suh
Link to comment
Share on other sites

I personally never use RC's of any software, operating systems, nas os, mobile os, nothing. When a build hits the RC stage, its not long before the actual release comes along, and in my opinion, its better to wait for the actual release.  Plus it will be easier in the long run for users to upgrade from a current released version of DSM to another released version of DSM. My advice to all is skip the RC and wait for the official release and the magic will happen. :)

Link to comment
Share on other sites

5 hours ago, Peter Suh said:

If we wait for this period, there is a risk that we may be exposed to vulnerabilities for a long time, so we are deeply concerned.

 

Even with a real Synology, they are so far behind the industry on critical vulnerabilities that it should override any underlying urgency associated with patch timing.

 

Anyone who is serious about security and is also making DSM accessible to the Internet should be doing so via VPN, a third-party authenticated proxy, or better yet, not at all.

  • Like 3
Link to comment
Share on other sites

1 hour ago, flyride said:

 

Even with a real Synology, they are so far behind the industry on critical vulnerabilities that it should override any underlying urgency associated with patch timing.

 

Anyone who is serious about security and is also making DSM accessible to the Internet should be doing so via VPN, a third-party authenticated proxy, or better yet, not at all.

I couldn’t agree more !!! Do not expose your precious data through known ports or protocols on internet. Use VPN and only if there is no other option, open ports to your server but, never expose more than one service per system and if you do, never use standard ports if possible 

Edited by pocopico
  • Like 1
Link to comment
Share on other sites

2 minutes ago, vinhnguyen said:

I have an error with DSM 7.1.1RC DS3622xs+. Using sudo ./rploader.sh postupdate broadwellnk-7.1.0-42661 successfully. But accessing the IP address of the NAS, the system automatically shuts down.

 

Your report is exactly the same as mine. I think it will be a good reference. thank you

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

Hi @pocopico, I got stuck at upgrading my DS918+ from 7.1.0-42661 to 7.1.1-42951 RC. It's in infinite loop of Recover mode. Tried to start TCRP and do the postupdate with "./rploader.sh postupdate apollolake-7.1.0-42661". I was prompted if I wanted to use apollolake-7.1.1-42951 and I entered "y". After rebooting it got worse: visit the NAS via browser gave me "Err_connection_refused". Could you please tell me what I should do? I could reinstall DSM but couldn't SSH/Telnet to the box so no way for me to reset that. Thanks in advance!!

Link to comment
Share on other sites

17 hours ago, hiukong said:

Hi @pocopico, I got stuck at upgrading my DS918+ from 7.1.0-42661 to 7.1.1-42951 RC. It's in infinite loop of Recover mode. Tried to start TCRP and do the postupdate with "./rploader.sh postupdate apollolake-7.1.0-42661". I was prompted if I wanted to use apollolake-7.1.1-42951 and I entered "y". After rebooting it got worse: visit the NAS via browser gave me "Err_connection_refused". Could you please tell me what I should do? I could reinstall DSM but couldn't SSH/Telnet to the box so no way for me to reset that. Thanks in advance!!

 

Updates to 7.1.0-42951 RC must use pocopico's develop repo.
https://github.com/pocopico/tinycore-redpill/tree/develop

 

You should have used pocopico's main(master) repo.
https://github.com/pocopico/tinycore-redpill/tree/main

 

You can record the img file of develop back to the USB stick, but
You can convert it to the contents of the develop repo in the following way.

 

curl --location "https://github.com/pocopico/tinycore-redpill/raw/develop/rploader.sh" -O

chmod +x rploader.sh

./rploader.sh fullupgrade

Edited by Peter Suh
Link to comment
Share on other sites

12 minutes ago, Peter Suh said:

 

Updates to 7.1.0-42951 RC must use pocopico's develop repo.
https://github.com/pocopico/tinycore-redpill/tree/develop

 

You should have used pocopico's main(master) repo.
https://github.com/pocopico/tinycore-redpill/tree/main

 

You can record the img file of develop back to the USB stick, but
You can convert it to the contents of the develop repo in the following way.

 

curl --location "https://github.com/pocopico/tinycore-redpill/raw/develop/rploader.sh" -O

chmod +x rploader.sh

./rploader.sh fullupgrade

 

Appreciate the detailed instructions, Peter! Working on it now. Will share the result here soon.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...