From aaf94dae5ca8ff9c8a00fd30f6b8b33283964fc9 Mon Sep 17 00:00:00 2001
From: Recolic <git@me.recolic.net>
Date: Mon, 21 Apr 2025 17:38:27 +0000
Subject: [PATCH] Update README.md

---
 README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index d3bdee4..8c59ced 100644
--- a/README.md
+++ b/README.md
@@ -33,7 +33,7 @@ For other organizations, follow official guide from your org. Ubuntu should be o
 2. Follow ubuntu guide above to setup password policy file & disk encryption, or any requirements from your org.
 3. Copy the `/etc/os-release` file from ubuntu.
 4. If `lsb_release` is present in your system, uninstall or destroy it.
-5. [none-gnome user only] Install `seahorse` and make sure you have a default keyring **with password**.
+5. [none-gnome user only] Install `seahorse` and make sure you have a default keyring **with password**. ([why?](https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/103))
 6. Run `intune-portal` to enroll your machine.
 
 > For disk encryption settings, theoretically, dm-crypt (with or without LUKS) + LVM for root partition should be enough.
@@ -42,6 +42,8 @@ For other organizations, follow official guide from your org. Ubuntu should be o
 
 > **This is not recommended, as certificate expires in 1 month & requires frequent manual maintenance.**
 
+<details><summary>See Details</summary>
+
 Copy the following files from enrolled Level-2 machine to unenrolled Level-1 machine: 
 
 ```
@@ -59,7 +61,9 @@ Then, run `seahorse` to double-confirm your "login" keyring is unlocked and non-
 
 > You may change the password but DO NOT remove the password protection! There is a known bug <https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/103>
 
-You are all set! 
+You are all set!
+
+</details>
 
 ## FAQ and debug
 
-- 
GitLab