[00:45:47]
<OnEnemy> Not sure if you can see it from your new account but Ill send it again just in case: https://paste.yunohost.org/amowatazet
[00:45:49]
<DJ Chase (fae/faer)> thanks
[00:45:52]
<DJ Chase (fae/faer)> there's nothing in the log about it :/
[00:45:54]
<DJ Chase (fae/faer)> can you send a screenshot of synapse-web right before you log in?
[00:47:39]
<OnEnemy> Like the login page? I use a self hosted Element instance for Web and FluffyChat for android.
[00:47:47]
<DJ Chase (fae/faer)> the login page of synapse admin, sorry
[00:50:02]
<OnEnemy> oh its fine, i was about to ask
[00:50:10]
<OnEnemy> ok
[00:50:16]
<OnEnemy> https://aria.im/_bifrost/v1/media/download/ARd3-7tXVDwoOogXxshc0m5S22VQdbfznOH_kVKWPMYPfCUH9MuQU_MSXY0ZPqTgkH61e3Sj5eEUmqN1nHjHBVxCedA5Jc_wAHRhbGtzaWNrLnBwLnVhL0VjVktYc0V3WXJTSm92Z3NkaHBqcGVmQQ
[00:50:24]
<OnEnemy> I have it setup to use only my domain
[00:50:32]
<DJ Chase (fae/faer)> press "sign in with sso" instead
[00:50:40]
<OnEnemy> https://aria.im/_bifrost/v1/media/download/AUZ6vAgCNuI5EmaJpIImMFm1IVAXz4-G0CCvowCaQDdtXT-aEOVEfWb3-MxJqPBGNJIVAsmqBak80M6c64ws-e5CedA5K5lgAHRhbGtzaWNrLnBwLnVhL0hlZHZLeVFjbFlOVnpBRHVYRE1Ua0ViTA
[00:50:43]
<DJ Chase (fae/faer)> continue
[00:51:14]
<OnEnemy> https://aria.im/_bifrost/v1/media/download/AbF0CxkpEpqO2vZFuAe2lI6j-OxAvOHCJIbgJd6-0Ykh3t7KuvXrC3BmkU7NLosB5OY-tU5w6mgzELlcMfNz6HVCedA5M9rwAHRhbGtzaWNrLnBwLnVhL3hYcGtzcmx1THVLbFBCWVdEUFJpSXBpbw
[00:51:17]
<OnEnemy> and i cant see anything in any of the tabs
[00:51:18]
<DJ Chase (fae/faer)> and that's the same error you get when you sign in without sso?
[00:51:20]
<OnEnemy> yep
[00:51:27]
<DJ Chase (fae/faer)> so i have mine set up to work with any domain. if you try that instead does it work?
[00:52:10]
<OnEnemy> ok let me try
[00:52:12]
<DJ Chase (fae/faer)> (that shouldn't be a security risk or anything because it's just a front end)
[01:05:44]
<OnEnemy> Nope. Both regular and SSO dont work
[01:05:48]
<DJ Chase (fae/faer)> same error?
[01:05:55]
<OnEnemy> Yep
[01:05:58]
<DJ Chase (fae/faer)> when you ran the commands, what was the argumetn for the command that was something like `create_admin_user.sh`?
[01:10:01]
<OnEnemy> Yea I copied the command and I just filled in username and domain
[01:10:01]
<DJ Chase (fae/faer)> and it was @onenemy:talksick.pp.ua?
[01:10:01]
<DJ Chase (fae/faer)> and you ran it as root?
[01:10:02]
<OnEnemy> I had to input a password
[01:10:02]
<OnEnemy> Yes and yes
[01:10:02]
<DJ Chase (fae/faer)> a root password you mean?
[01:10:02]
<OnEnemy> Yes
[01:10:03]
<DJ Chase (fae/faer)> oh wait
[01:10:03]
<DJ Chase (fae/faer)> i have no idea then
[01:11:48]
<OnEnemy> Yep
[01:11:48]
<DJ Chase (fae/faer)> okay so it's not a synaps-admin thing
[01:11:48]
<DJ Chase (fae/faer)> does it give the same error when you try using https://u9.tel/synapse-admin
[01:13:23]
<OnEnemy> Nope
[01:13:23]
<OnEnemy> My server is borked
[01:13:24]
<OnEnemy> Somehow
[01:13:24]
<DJ Chase (fae/faer)> there is another way to set an admin give me a moment
[01:22:57]
<OnEnemy> thats using ssh right?
[01:22:57]
<DJ Chase (fae/faer)> [Admin API - Synapse](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) ([archive](https://web.archive.org/web/*/https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html))
[01:22:57]
<DJ Chase (fae/faer)> yeah
[01:22:57]
<OnEnemy> Idk if ill be able to do the DB one since ive never messed with db before but I guess I could try the second one
[01:22:58]
<OnEnemy> and i put in my ip, not the domain?
[01:24:28]
<DJ Chase (fae/faer)> no specifically http://127.0.0.1:8080/
[01:29:37]
<OnEnemy> ok
[01:29:37]
<OnEnemy> something about an error code and that im not a server admin
[01:29:38]
<OnEnemy> i guess ill just give up then. As long as im federated and i can chat with people, i guess it dosnt matter. Thanks for trying to help tho. I really appreciate it.
[01:29:38]
<DJ Chase (fae/faer)> so try the database method then
[01:29:41]
<DJ Chase (fae/faer)> because you're definitely not an admin right now
[01:40:16]
<OnEnemy> Is that also SSH?
[01:40:16]
<OnEnemy> cuz idk how to access the db
[01:40:17]
<DJ Chase (fae/faer)> you ran the first set of commands via ssh right?
[01:40:18]
<OnEnemy> "Making an Admin API request" is what i ran as SSH
[01:40:22]
<DJ Chase (fae/faer)> when i first gave you a list of commands to run at the very start, you did that over ssh right?
[01:40:23]
<DJ Chase (fae/faer)> ok
[01:40:23]
<DJ Chase (fae/faer)> no worries you're good
[01:40:23]
<OnEnemy> Oh yes
[01:40:23]
<OnEnemy> sorry im so lost rn. Thanks for taking the time
[01:40:24]
<DJ Chase (fae/faer)> so whenever you need to run commands on the server it's going to be over ssh
[01:40:24]
<DJ Chase (fae/faer)> yeah ssh is how you run commands on your server
[01:40:25]
<DJ Chase (fae/faer)> let me see if i can find the path to the db for you
[01:42:15]
<DJ Chase (fae/faer)> okay so in the file `/etc/matrix-synapse/homeserver.yaml`, find the following lines at tell me what they say:
```
database:
name: <something>
```
[01:46:57]
<DJ Chase (fae/faer)> great
[01:46:57]
<OnEnemy> ok
[01:46:57]
<OnEnemy> found it
[01:46:57]
<OnEnemy> name: psycopg2
[01:46:57]
<DJ Chase (fae/faer)> what does it say?
[01:46:58]
<OnEnemy> ok
[01:46:58]
<DJ Chase (fae/faer)> so to edit the database, you want to make sure you're signed in as the synapse user. to do that, run `sudo yunohost app shell synapse`
[01:46:59]
<DJ Chase (fae/faer)> so i'm also going to teach you how to process docs like the one i sent you so that you can do it yourself next time :)
[01:46:59]
<DJ Chase (fae/faer)> great
[01:46:59]
<DJ Chase (fae/faer)> so here is the link i sent: [Admin API - Synapse](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) ([archive](https://web.archive.org/web/*/https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html))
[01:47:00]
<DJ Chase (fae/faer)> the first paragraph that actually tells us something is this:
> Check your database settings in the configuration file, connect to the correct database using either `psql [database name]` (if using PostgreSQL) or `sqlite3 path/to/your/database.db` (if using SQLite) and elevate the user `@foo:bar.com` to administrator.
[01:48:52]
<OnEnemy> command not found?
[01:48:52]
<DJ Chase (fae/faer)> if you remember from the file i had you look at, our database is postgresql, not sqlite, so we're going to use the first command, `psqL psycopg2`
[01:48:52]
<DJ Chase (fae/faer)> okay exit out of the synapse shell and try as root?
[01:48:52]
<DJ Chase (fae/faer)> (hi katie)
[01:50:45]
<OnEnemy> same.
[01:50:45]
<Katie (KittyKatt) [she/they]> (hi)
[01:50:45]
<OnEnemy> psqL isnt found
[01:50:46]
<Katie (KittyKatt) [she/they]> Doing database level edits to the synapse DB?
[01:50:46]
<OnEnemy> oh wait
[01:50:46]
<DJ Chase (fae/faer)> yeah 🙃
[01:50:46]
<OnEnemy> maybe my cd is wrong
[01:50:47]
<DJ Chase (fae/faer)> that's the other way the docs suggest
[01:50:47]
<DJ Chase (fae/faer)> they can't create an admin user
[01:50:47]
<Katie (KittyKatt) [she/they]> That's...not good.
[01:50:48]
<DJ Chase (fae/faer)> oops they had a typo
[01:50:48]
<OnEnemy> :(
[01:50:49]
<DJ Chase (fae/faer)> go back to the app shell
[01:57:38]
<DJ Chase (fae/faer)> and then the command is all lowercase
[01:57:38]
<OnEnemy> oh no
[01:57:39]
<DJ Chase (fae/faer)> k hang on
[01:57:39]
<OnEnemy> ok and now i need to input password
[01:57:40]
<DJ Chase (fae/faer)> so it's
```
database:
name: psycopg2
#txn_limit: 10000
args:
user: synapse
password: <password>
database: synapse
```
[01:57:40]
<DJ Chase (fae/faer)> the password's in the same spot of the file as the database name
[01:57:40]
<OnEnemy> is it encrypted? it shows a "password" but its invalid
[01:57:41]
<OnEnemy> let me see if i can grab the error
[01:57:41]
<OnEnemy> yea
[01:57:41]
<DJ Chase (fae/faer)> so if you copy that password that's the one you need to input
[01:57:42]
<OnEnemy> Password for user synapse:
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: database "psycopg2" does not exist
[01:57:43]
<DJ Chase (fae/faer)> try `synapse` as the database?
[01:57:43]
<DJ Chase (fae/faer)> hmm
[01:57:44]
<DJ Chase (fae/faer)> great
[01:57:44]
<DJ Chase (fae/faer)> so if you check the docs again, you'll see that it just gives us the sql command we need to run:
```sql
UPDATE users SET admin = 1 WHERE name = '@foo:bar.com';
```
[01:57:44]
<OnEnemy> im in
[01:57:45]
<DJ Chase (fae/faer)> in this case set the name to `@onenemy:talksick.pp.ua`
[01:57:45]
<DJ Chase (fae/faer)> (*hacking noises*)
[01:57:46]
<DJ Chase (fae/faer)> lol
[01:57:46]
<OnEnemy> and my connection crashed. lmao
[01:57:46]
<OnEnemy> Update 1 was returned
[02:00:04]
<DJ Chase (fae/faer)> does it work now though?
[02:00:04]
<DJ Chase (fae/faer)> that's *probably* not good
[02:00:06]
<OnEnemy> ill check brb
[02:00:06]
<OnEnemy> *sigh* nope
[02:00:06]
<DJ Chase (fae/faer)> yay!
[02:00:07]
<DJ Chase (fae/faer)> i love when things inexplicably don't work 🙃
[02:03:26]
<Katie (KittyKatt) [she/they]> If it's using SSO for synadmin, is Yunohost deploying and using Matrix Authentication Service alongside Synapse, using Synapse built-in (going to be deprecated at some point) OIDC config, or using local database users?
[02:03:26]
<OnEnemy> It errors out
[02:03:26]
<Katie (KittyKatt) [she/they]> Because I believe the methods for how admin is defined differ between those situations.
[02:03:26]
<OnEnemy> Also I can't create any other users on my Yunohost
[02:03:26]
<OnEnemy> It's using my Yunohost user. Unfortunately I have no idea what any of those are.
[02:03:27]
<DJ Chase (fae/faer)> when you installed synapse, did you set it to login with username a password or with yunohost portal?
[02:03:49]
<DJ Chase (fae/faer)> oooh
[02:03:49]
<OnEnemy> I think with username and password
[02:03:49]
<OnEnemy> Iirc
[02:04:33]
<DJ Chase (fae/faer)> okay so when you log in to synapse-admin, you're logging in as @onenemy:talksick.pp.ua with your matrix password, right?
[02:05:05]
<DJ Chase (fae/faer)> mhm
[02:05:05]
<OnEnemy> Yes
[02:05:46]
<DJ Chase (fae/faer)> can you try logging in to a matrix client, but instead of entering your username and password try "continue with sso" (or something similar) instead?
[02:06:28]
<OnEnemy> ok brb
[02:10:05]
<OnEnemy> Or use another device
[02:10:05]
<OnEnemy> Press can't confirm?
[02:10:05]
<OnEnemy> So it's asking to confirm identity
[02:10:05]
<OnEnemy> It would use fluffy chat
[02:10:06]
<OnEnemy> Taking a picture of my screen
[02:10:06]
<DJ Chase (fae/faer)> screenshot?
[02:10:07]
<OnEnemy> Disregard the sticker, came with the laptop
[02:10:07]
<DJ Chase (fae/faer)> yeah use another device
[02:10:07]
<OnEnemy> https://aria.im/_bifrost/v1/media/download/Aa5U4xBzawQGXbpf5srmFqyD8YRdOiXNl9Efc-OQ-934vZqeetPCjSLvDaxsV0z4Jc-2WiJbnVIQFppSvBy2ZU5CedA9t1wgAHRhbGtzaWNrLnBwLnVhL1Vva0piUXZqUmR3RkpacWdrQ3RnU3RwRA
[02:10:08]
<DJ Chase (fae/faer)> the pacman one is fun
[02:14:26]
<OnEnemy> Ok so im "verified" but i still have a "Verify this session" as a popup on the top lefthand side
[02:14:26]
<DJ Chase (fae/faer)> ok now try logging in to synapse-admin with sso
[02:14:27]
<Katie (KittyKatt) [she/they]> Happen to have that psql session still open?
[02:14:27]
<OnEnemy> ok
[02:14:27]
<OnEnemy> Crashed
[02:14:27]
<OnEnemy> usually goes into a loop of verify and verify this session so im forced to clear the session and reverify
[02:14:28]
*DJ Chase (fae/faer) wishes fae had a superwoman emoji
[02:14:28]
<OnEnemy> Still error
[02:14:29]
<Katie (KittyKatt) [she/they]> To validate that your user actually got set with it.
[02:14:29]
<Katie (KittyKatt) [she/they]> Sad. I was gonna have you run:
```
SELECT name FROM users WHERE admin = 1;
```
[02:14:30]
<DJ Chase (fae/faer)> can you reopen the psql session and try that?
[02:16:27]
<OnEnemy> Oh boy this is gonna be fun
[02:16:27]
<Katie (KittyKatt) [she/they]> And also to see if accidentally there's another admin account lying around.
[02:16:28]
<OnEnemy> Ok wasn't that bad, I'm in
[02:16:28]
<OnEnemy> https://aria.im/_bifrost/v1/media/download/AbTQSUTl0LQINxZ3PWEcE2sHo4274ihxMLNOVxJ1S0BctJeR0nDvg4zt_n5QP-0zPhKJ6Pcbgb6gO4le6uySvh5CedA-FHfwAHRhbGtzaWNrLnBwLnVhL0xmTEtZVVdDUHFva3ZTR0pxWGRqbkFKZg
[02:16:28]
<OnEnemy> Thank God JuiceSSH saves commands between sessions
[02:16:29]
<Katie (KittyKatt) [she/they]> The command I sent shouldn't expose any password hashes, only a list "accounts (@username:domain) that have the `admin` field set to `1`"
[02:16:29]
<DJ Chase (fae/faer)> (bash does that too)
[08:15:28]
<Katie (KittyKatt) [she/they]> Neato, well at least that's verification.
[08:15:33]
<OnEnemy> Lmao I logged into Synapse Admin on my phone and it works. Lmao thanks everyone for helping.
[08:15:33]
<Katie (KittyKatt) [she/they]> Perhaps cache.
[08:15:33]
<OnEnemy> Probably
[08:15:33]
<pie4_by_yuno> Hi, salut,
a classical error today...
*Votre IP ou domaine 151.80.60.78 est sur liste noire sur Spamhaus ZEN*
* Il semble que la raison mentionne « open resolver ».
Cela signifie généralement que votre serveur n'utilise pas son DNS local, mais un DNS public et ouvert.
Vérifiez le contenu de /etc/resolv.conf, il devrait contenir nameserver 127.0.0.1.
Comme ce fichier est généralement généré automatiquement, ne le modifiez pas manuellement. Vérifiez vos paramètres DHCP ou vos paramètres VPN si vous en utilisez un, ou si vous avez utilisé une image Debian créée, par exemple, par un fournisseur de VPS, recherchez une configuration cloudinit.
N'hésitez pas à vous rendre sur les canaux d'assistance YunoHost pour obtenir de l'aide sur ce problème.
La raison exacte de la liste noire est : "Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:305:2100::9bce/"
Après avoir identifié la raison pour laquelle vous êtes répertorié sur cette liste et l'avoir corrigée, n'hésitez pas à demander le retrait de votre IP ou de votre domaine sur https://www.spamhaus.org/zen/*
would someone be available and willing to give me a hand ?
[08:19:58]
<pie4_by_yuno> admin@p...:~$ more /etc/resolv.conf
nameserver 127.0.0.1
[08:28:12]
<@err404:matrix.numericore.com> En quoi ça pose un problème d'être ''open resolver'' ?
[08:34:25]
<pti-jean> Cela provoque ce genre d'erreur:
> [ERROR] Your IP or domain 80.xx.xx.xx is blacklisted on Spamhaus ZEN
> - The blacklist reason is: "Error: open resolver; https://check.spamhaus.org/returnc/pub/2400:cb00:987:1024::ac40:b306/"
> - After identifying why you are listed and fixing it, feel free to ask for your IP or domain to be removed on https://www.spamhaus.org/zen/
[08:36:23]
<@err404:matrix.numericore.com> Ah oui, ça permet une attaque par amplification, en falsifiant l'adresse d'origine.
Il faut donc activer la vérification de l'ip source et désactiver la récursivité.
[08:38:27]
<@err404:matrix.numericore.com> Ah oui, ça permet une attaque par amplification, en falsifiant l'adresse d'origine.
Il faut donc activer la vérification de l'ip source et désactiver la récursivité.
Mais la récursivité on en a besoin pour un serveur dns perso, donc il faut le rendre privé (pas ouvert sur Internet)
[08:40:30]
<@err404:matrix.numericore.com> Oui, j'ai bien compris que spamhaus n'aimait pas, mais je n'avait pas compris pourquoi 😃
[09:04:25]
<pie4_by_yuno> j'imagine que ce n'est pas une configuration sur mon yunohost, mais en amont dans la zone dns de mon serveur (ovh)?
[09:11:18]
<Kim Minh> pie4_by_yuno: c'est un VPS OVH ? Alors c'est sans doute à cause de leur IPv6.
[09:18:22]
<pie4_by_yuno> tu peux détailler ?
[09:23:23]
<Kim Minh> https://forum.yunohost.org/t/blocked-using-zen-spamhaus-org-error-open-resolver/40948/34
[09:26:26]
<Kim Minh> De ce que j'ai réussi à décortiquer le fin mot de l'histoire c'est que OVH fourni des adresses IPv6 en /128 alors que la bonne pratique c'est de les fournir en /64. Le résultat c'est que pleins de VPS différents ont une adresse IPv6 dans le même /64 et du coup considérés comme un seul serveur par Spamhaus.
[09:27:13]
<Kim Minh> Du coups Spamhaus pense, à tort, que toutes ces adresses appartiennent en réalité à un résolveur public.
[09:38:17]
<pie4_by_yuno> compris. est-ce qu'une solution ça peut être de ne pas utiliser leur configuratino IPv6, et me contenter de l'IPV4 ? -question de novice en chaussette, désolé.
[09:41:29]
<Kim Minh> Oui, une solution serait de supprimer les adresses IPv6 dans le fichier /etc/dnsmasq.d/spamhaus. Je pense que je vais finir par faire ça. Mais ça ne me plait pas de débrancher peu à peu IPv6. C'est aller dans la mauvaise direction.
[09:44:38]
<pie4_by_yuno> sur le thread que tu as mis en lien, la solution choisie par edlm10 a été d'utiliserleur Data Query Service (DQS)...
[09:45:35]
<Kim Minh> Oui, c'est une alternative sérieuse, mais elle nécessite de s'enregistrer auprès de Spamhaus.
[09:47:27]
<pie4_by_yuno> ce qui te déplait?
[09:49:43]
<Kim Minh> Un peu, oui. Je n'apprécie jamais d'être pisté.
[09:50:44]
<Kim Minh> Mais c'est sans doute la solution la plus raisonnable :-(
[09:51:42]
<Kim Minh> J'aurai bien voulu obtenir une IPv6 en /64 d'OVH, mais ça ne semble pas disponible pour les VPS.
[09:52:30]
<pie4_by_yuno> merci...
[10:10:19]
<Kim Minh> De rien.
[15:14:15]
<DJ Chase (fae/faer)> is there a way to detect this and stop the a service before it consumes literally 100% of disk space?
[15:14:15]
<DJ Chase (fae/faer)> https://aria.im/_bifrost/v1/media/download/AV47pTwqJshenUSKi0pQDaIq9JqetCrVvtglel_mnZzXsIyJ6e8HgvzPzQDHvQBfoHI2Fx1D4uS2rFXwErKIV25CedBqlc3gAHU5LnRlbC9RQk9od0ZyWU5RTEFlRnhlT1ZHVmhXaHU
[15:27:15]
<Aleks (he/him/il/lui)> I suppose the ideal thing is understanding exactly what files in /var/tmp(?) are doing this
[16:02:56]
<DJ Chase (fae/faer)> `postgresql@15-main.service` stopped, which caused syapse to spew python tracebacks
[16:02:56]
<DJ Chase (fae/faer)> logfiles
[16:02:56]
<DJ Chase (fae/faer)> (`/var/log`)
[18:33:41]
<Yaeghs> Hello there ! Je viens par ici car je suis un peu perdu. J'ai paumé mes mots de passe admin et root sur mon instancey unohost mais j'ai réussi à récupérer le root avec le boot rescue (c'est un VPS chez OVH). Donc j'ai de nouveau accès au compte root car j'avais une clé ssh en place. Maiiiiis, la commande donnée sur la doc est là pour le mot de passe root : quelle est la commande pour changer le mot de passe d'un utilisateur ? (l'utilisateur admin en l'occurrence)
[18:49:03]
<Chatpitaine Caverne> Yaeghs:
```
sudo yunohost user update --help
usage: yunohost user update username
[-h] [-F FULLNAME] [-m MAIL] [-p [PASSWORD]]
[--add-mailforward [MAIL ...]]
[--remove-mailforward [MAIL ...]]
[--add-mailalias [MAIL ...]]
[--remove-mailalias [MAIL ...]] [-q {SIZE|0}]
[-s LOGINSHELL]
Update user informations
positional arguments:
username Username to update
options:
-h, --help show this help message and exit
-F FULLNAME, --fullname FULLNAME
The full name of the user. For example 'Camille
Dupont'
-m MAIL, --mail MAIL
-p [PASSWORD], --change-password [PASSWORD]
New password to set
--add-mailforward [MAIL ...]
Mailforward addresses to add
--remove-mailforward [MAIL ...]
Mailforward addresses to remove
--add-mailalias [MAIL ...]
Mail aliases to add
--remove-mailalias [MAIL ...]
Mail aliases to remove
-q {SIZE|0}, --mailbox-quota {SIZE|0}
Mailbox size quota
-s LOGINSHELL, --loginShell LOGINSHELL
The login shell used
```
[18:51:07]
<Chatpitaine Caverne> Ce qui donnerait (sans le sudo vu que tu es root :
`yunohost user update admin --change-password [PASSWORD]`
[18:51:28]
<Yaeghs> Je me sens ... stupide
[18:51:34]
<Yaeghs> J'ai cherché le help sur le user mais pas sur le update
[18:51:47]
<Yaeghs> Merci !
[18:51:48]
<Chatpitaine Caverne> Faut pas. Aucune raison
[18:52:19]
<Yaeghs> (Cependant, j'en profite pour découvrir Matrix et voir à quoi ça ressemble, ce fut toujours ça de gagner 👀 )
[18:55:08]
<Chatpitaine Caverne> J'oubliais, et peut-être trop tard. Ajouter un espace avant la commande pour éviter de laisser une trace dans les log, vu qu'il y aura un password en clair.
[18:57:36]
<Yaeghs> pas encore trop tard ! Mettre un espace avant le début d'une commande l'empêche d'apparaître dans les logs ? :o
[18:58:11]
<Chatpitaine Caverne> Dans le history en tout cas. Les logs, pas certain.
[18:58:13]
<Chatpitaine Caverne> Faudrait regarder la log de l'API yunohost pour voir ce que ça donne.
[18:58:13]
<Yaeghs> Je le rechangerais à la main via l'admin panel quand j'y aurais accès alors
[19:23:32]
<Yaeghs> L'espace ne marche pas pour history ? Ca apparait bien dans les logs (avec un espace devant)
[19:23:32]
<Yaeghs> si tu me dis où faut regarder, je peux te dire ce que ça donne
[19:24:29]
<Yaeghs> Je ne vois rien de licencieux dans les logs. Moulinette dit d'aller voir le log spécifique à l'action et dans le log spéicifque à l'action il y a 4 lignes pour dire qu'il invalide les sessions, exporte et met à jour le SSO
[20:01:20]
<nojhan> Est-ce qu'il y a des gens qui bossent sur le packaging de Loomio ?
[20:05:26]
<Chatpitaine Caverne> La log de l'API est dans `/var/log/yunohost/yunohost-api.log` avec des droits root.
Le history (c'est ce qui s'affiche quand tu fais flèche haute / flèche haute ... pour remonter dans les commandes passées) tu l'obtiens avec la commande history.
Les commandes avec un espace devans n'apparaissent pas dans le history (ça j'en suis sûr et l'ai appris récemment) dans les logs, je ne sais pas.
[20:05:40]
<Chatpitaine Caverne> La log de l'API est dans `/var/log/yunohost/yunohost-api.log` avec des droits root.
Le history (c'est ce qui s'affiche quand tu fais flèche haute / flèche haute ... pour remonter dans les commandes passées) tu l'obtiens avec la commande history.
Les commandes avec un espace devant n'apparaissent pas dans le history (ça j'en suis sûr et l'ai appris récemment) dans les logs, je ne sais pas.