# Yunohost 11.1 spooky testing
**URL:** https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802
**Category:** Announcements
**Created:** [October 23, 2022, 6:43pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802 "2022-10-23T18:43:30Z")
**Posts on this page:** 20
**Page:** 6
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 3, 2022, 7:23pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/101 "2022-12-03T19:23:26Z")
Hmf can you confirm that the postfix conf is up to date with `yunohost tools regen-conf postfix --dry-run --with-diff`
---
### Author:  [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 7:30pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/102 "2022-12-03T19:30:26Z")
> [@Aleks](#):
>
> `yunohost tools regen-conf postfix --dry-run --with-diff`
The first thing I did was a `yunohost tools regen-conf --force`, then I rebooted the server.
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 3, 2022, 8:47pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/103 "2022-12-03T20:47:37Z")
Hmyeah after investigating I see why this is happening : the legacy admin user is not really member of the all\_users group and therefore doesnt have the “mail.mail” permission, yet it is still supposed to receive the mails sent to root@ (and other aliases) … but postfix complains that the user is unknown
I recommend the following solution:
- ultimately the advice is to get rid of the legacy `admin` user, which implicitly fixes the issue
- if you really do want to keep the `admin` user, it’s probably better to delete it and recreate it, just to make sure it’s really a regular user (the one we recreate during the 11.1 migration is only meant to be a tmp user just to allow people to still login using their “old” admin credentials to minimize confusion …)
- if neither of these satisfy you, you can also run `yunohost user permission add mail.main admins`, which will re-add the mail permission to the legacy `admin`, and then postfix will be happy about it
---
### Author:  [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 10:10pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/104 "2022-12-03T22:10:17Z")
Deleting the user `admin` solves the problem (according to my mind we shouldn’t have a superuser called `admin` for security reasons).
I just saw that :
```auto
# yunohost user list
users:
admin:
fullname: Admin
mail: admin_legacy
mailbox-quota: 0
username: admin
```
Shouldn’t the mail be like `admin@mydomain.tld`?
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 3, 2022, 10:12pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/105 "2022-12-03T22:12:46Z")
> [@Kit](#):
>
> Shouldn’t the mail be like `admin@mydomain.tld`?
Nope because that alias is meant to be an alias for the admins@ group (mainly for backward compatibility and typo stuff)
> [@Kit](#):
>
> according to my mind we shouldn’t have a superuser called `admin` for security reasons
Would be glad to hear your detailed opinion on that … Naively my answer is “root already exists, why would having an additional ‘admin’ be better for security?”
---
### Author:  [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 10:26pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/106 "2022-12-03T22:26:49Z")
Mmmmmmkay for the alias.
More naively©, why having a superuser called `admin` (which is probably the most tested user by attackers after `root`) when we can choose any user to be the admin (and iirc, for each app installed we choose a user to be the app admin, why not the same for the whole system after yunohost installation ?).
I suppose the choice of automatically create the user `admin` was made to avoid using `root` ?
Sorry if the question is stupid (or worse, already answered).
---
### Author:  [@arnauld](https://forum.yunohost.org/u/arnauld)
#### Post date: [December 3, 2022, 10:27pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/107 "2022-12-03T22:27:10Z")
Hum I am on 11.1.0.2 (testing), what to do to go back to stable? 😀
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 3, 2022, 10:38pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/108 "2022-12-03T22:38:14Z")
> [@Kit](#):
>
> More naively©, why having a superuser called `admin` (which is probably the most tested user by attackers after `root`) when we can choose any user to be the admin (and iirc, for each app installed we choose a user to be the app admin, why not the same for the whole system after yunohost installation ?).
>
> I suppose the choice of automatically create the user `admin` was made to avoid using `root` ?
Ah I misread your initial message and missed the “shouldn’t”, I though you meant we should /o. But yeah what you’re saying is pretty much the reason we’re doing this migration, new installs of YunoHost won’t have any “admin” at all, instead the very first user should be in the admins group, and other users created can be added to the admins group
I think historically `admin` was created because some sort of LDAP admin user was needed (but then we realize we could manipulate the LDAP db using the unix root). Though historically the “admins” group did existed, I think the intention was to somehow allow people to be added to that admins group, but was never implemented until now (80% of the worktime ends up being caught in “how do you handle the transition from existing installs”)
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 3, 2022, 10:40pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/109 "2022-12-03T22:40:36Z")
> [@arnauld](#):
>
> Hum I am on 11.1.0.2 (testing), what to do to go back to stable? 😀
You do not, because there is no way to rollback the changes introduced in 11.1. The recommendation is to upgrade to 11.1.1 (testing) to fix the aliases issues and other bugs existing in 11.1.0, and 11.1.x will ultimately become stable at some point. (At least 11.1.1 is “more stable” than 11.1.0)
---
### Author:  [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 10:46pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/110 "2022-12-03T22:46:14Z")
11.1.1. **2** according to the last apticron 😜
To go back to stable, maybe remove the “testing” `/etc/apt/sources.list.d/yunohost.list` after the update ?
---
### Author:  [@xabi](https://forum.yunohost.org/u/xabi)
#### Post date: [December 3, 2022, 11:05pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/111 "2022-12-03T23:05:17Z")
Just a quick question before I remove the user `admin`:
- when I ssh using user@server + `sudo su` = I enter my user password. Success!
- when I ssh using user@server + `su` = I need to enter the root password, user password get me Authentication failure.
Is this the expected behaviour?
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 3, 2022, 11:11pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/112 "2022-12-03T23:11:38Z")
Yes, `sudo` asks for the user password, `su` asks for the root password
---
### Author:  [@arnauld](https://forum.yunohost.org/u/arnauld)
#### Post date: [December 3, 2022, 11:33pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/113 "2022-12-03T23:33:00Z")
Thank you, it worked.
---
### Author:  [@xeu100](https://forum.yunohost.org/u/xeu100)
#### Post date: [December 4, 2022, 7:35pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/114 "2022-12-04T19:35:05Z")
> [@Aleks](#):
>
> - admins/ldap: re-allow members of the admins group to edit ldap db (4f5cc166)
I’m still unable to use my account to modify LDAP on the version this was included in.
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 4, 2022, 7:53pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/115 "2022-12-04T19:53:57Z")
Can you elaborate on what tool exactly you’re using and what you’re trying …
---
### Author:  [@xeu100](https://forum.yunohost.org/u/xeu100)
#### Post date: [December 4, 2022, 10:04pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/116 "2022-12-04T22:04:41Z")
I’m using Apache Directory Studio and am using “uid=username,ou=users,dc=yunohost,dc=org” to authenticate.
---
### Author:  [@lclaude](https://forum.yunohost.org/u/lclaude)
#### Post date: [December 5, 2022, 12:44am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/117 "2022-12-05T00:44:58Z")
Hello,
On a domain with a let’s encrypt certificat there is no possibility to go back to a self signed one.
---
### Author:  [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [December 5, 2022, 5:30pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/118 "2022-12-05T17:30:13Z")
> [@lclaude](#):
>
> On a domain with a let’s encrypt certificat there is no possibility to go back to a self signed one.
Yes … do you really need this feature …
---
### Author:  [@lclaude](https://forum.yunohost.org/u/lclaude)
#### Post date: [December 5, 2022, 8:15pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/119 "2022-12-05T20:15:58Z")
No, you’re right I don’t need it.
But I can’t have the box “Ignore diagnosis checks” in state ON/YES. There is nothing to validate this state and it didn’t ‘remember’ it.
---
### Author:  [@YB2022](https://forum.yunohost.org/u/YB2022)
#### Post date: [December 6, 2022, 6:21am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/120 "2022-12-06T06:21:53Z")
Great! Can someone tell me when 11.1 will be stable (estimated)?
[Previous page](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802.md?page=5)
[Next page](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802.md?page=7)