synology升級失敗"此檔案可能已損毀"

 Synology的firmware太舊，管理程式也太舊，要在管理介面上用自動更新。

但卻一直顯示這個是最新版了，所以就手動去下載最新的版本來用手動更新。

結果下載好的檔案透過管理介面上傳後卻一直顯示此檔案可能已損毀。

試了幾個比較新的版本都如此。

然後查了一下才發現原本的版本太舊(6.2)，沒辦法直接7，要先下載6.3手動更新，更新完成後，自動更新的功能也恢復正常，就利用自動更新在升到最新版就行了。

Failed Synology upgrade: "This file may be corrupted"

The firmware on the Synology device is too outdated, as well as the management software. To perform an update, the automatic update option is selected within the management interface.

However, the system keeps showing that the current version is the latest, so the decision is made to manually download the latest version and perform a manual update.

After downloading the file, it is uploaded through the management interface, but an error message stating that the file may be corrupted keeps appearing.

Several newer versions are attempted, but the issue persists.

Upon further investigation, it is discovered that the original version (6.2) is too outdated to directly upgrade to version 7. It is necessary to first download version 6.3 and perform a manual update. After completing the update, the automatic update functionality is restored, allowing for an upgrade to the latest version using the automatic update feature.

OPENVAS(GVM)進行弱點掃描會造成網域帳號被鎖住

在使用 OPENVAS對內部電腦進行弱點掃描，發現一個問題，就是會造成一些AD帳號因輸入太多次錯號密碼被鎖住。

個人猜測是在做掃描時，可能會隨便找一些帳號做登入測試，剛好有人的帳號就是一樣的，所以就被鎖了。

帳號被鎖，可以參考下列這個網站的教學，來查是哪一台設備在在做登入驗證的行為。

https://evotec.xyz/active-directory-how-to-track-down-why-and-where-the-user-account-was-locked-out/

OPENVAS(GVM) Vulnerability Scanning Causing Domain Account Lockouts

During the use of OPENVAS for vulnerability scanning on internal computers, I encountered an issue where it resulted in some AD accounts getting locked due to multiple incorrect password attempts. My personal speculation is that during the scanning process, the tool may attempt to log in using random accounts, and if there happens to be a match with a valid account, it leads to the account being locked.

To determine the source of the account lockouts, you can refer to the tutorial provided on the following website. It explains how to track down the device responsible for the login authentication attempts:

https://evotec.xyz/active-directory-how-to-track-down-why-and-where-the-user-account-was-locked-out/

centos 8 yum 更新失敗 - 同步倉庫 'AppStream' 快取失敗，忽略這個 (Failed to synchronize cache for repo)

新架了一台Centos 8的主機，要用yum先做一些元件更新時，都會跳出同步baseos/appstream/extract 快取失敗的問題。

查了一下，原來是centos8的repo路徑有變，但設定檔裡的路徑還是舊的，所以要改掉。

設定檔的路徑在/etc/yum.repos.d/，裡面有很多xxx.repo檔，檔案裡都有一個baseurl=httpxxxxxxxxxxxxxxxxxxxxxx的路徑，要改掉。

大部分國外的網站都說是把原本的mirror.centos.org改到vault.centos.org，大陸那邊的網站則是說改到http://mirrors.cloud.aliyuncs.com。

後來研究了很久，自己是改到https://mirrors.aliyun.com/centos/8-stream/xxxxxxx，這個網站可以直接用瀏覽器連上，後面的xxxx是要看你的錯誤訊息，看你是哪個快取找不到，就去網站上找到相對應的路徑，貼到設定檔上，就行了。

如果出現下列訊息，也會有可能是提供的網站已不存在，所以會有403的錯誤碼。

搞了兩天才弄好，分享給大家看一下，另外就是防火牆要注意，因為後來發現設定沒錯，但還是連不上，是因為自己的防火牆有擋一些東西，所以如果設定改好還失敗，可以查檢一下防火牆。

CentOS 8 Yum Update Failure - Failed to Synchronize Cache for 'AppStream' Repository

I encountered an issue with my newly deployed CentOS 8 server where I couldn't perform component updates using Yum. Every time I tried, I received an error indicating the failure to synchronize the baseos/appstream/extract cache.

After investigating, I discovered that the repository paths for CentOS 8 had changed, but the configuration files still contained the old paths, requiring modification. The configuration files are located in /etc/yum.repos.d/ and contain multiple xxx.repo files. Within each file, there is a baseurl=httpxxxxxxxxxxxxxxxxxxxxxx path that needs to be updated.

Most foreign websites suggested replacing the original mirror.centos.org with vault.centos.org, while some Chinese websites recommended using http://mirrors.cloud.aliyuncs.com. After extensive research, I found that modifying it to https://mirrors.aliyun.com/centos/8-stream/xxxxxxx worked for me. This website can be accessed directly through a browser, and the xxxxxx part depends on the error message you receive. Look for the corresponding path on the website and paste it into the configuration file.

If you encounter the following message, it's possible that the provided website no longer exists, resulting in a 403 error code.

After spending two days troubleshooting, I wanted to share this solution. Additionally, be mindful of your firewall settings. In my case, even though my configuration was correct, I still couldn't establish a connection. It turned out that my firewall was blocking certain elements. So, if you've made the necessary configuration changes but are still experiencing issues, check your firewall settings.