Ubuntu-fr

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

les commandes que j'ai faites n'ont rien endommagées ?

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Non, tu as juste créé un répertoire dans ton /home/$USER et mis des fichiers dedans.

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Je commence l'étape suivante je suis là :

facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/server$ cd ..
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine$ 

Dernière modification par polinux (Le 19/11/2022, à 16:40)

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

C'est bon.
Je dois sortir.

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

ok,
profites de ton week end
si je coince je posterai et j'attendrai gentiment la réponse

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Il faudra surement recommencer certaines manip. J'ai trouvé comment corriger l'erreur (non bloquante) du #68

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Petit coincage dans la 3 eme étape
je mets la totalité des commandes pour plus de clarté

facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine$ mkdir -p client-configs/keys
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine$ cd server
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/server$ ./easyrsa gen-req client1 nopass

Note: using Easy-RSA configuration from: ./vars

Using SSL: openssl OpenSSL 1.1.1f  31 Mar 2020
Generating an EC private key
writing new private key to '/media/facon-piscine/server/facon-piscine/server/pki/private/client1.key.GgLiTN2qiW'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Common Name (eg: your user, host, or server name) [client1]:

Keypair and certificate request completed. Your files are:
req: /media/facon-piscine/server/facon-piscine/server/pki/reqs/client1.req
key: /media/facon-piscine/server/facon-piscine/server/pki/private/client1.key

facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/server$ cp pki/private/client1.key ../client-configs/keys/
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/server$ 
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/server$ cd ../CA
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/CA$ ./easyrsa import-req ../server/pki/reqs/client1.req client1

Note: using Easy-RSA configuration from: ./vars

Using SSL: openssl OpenSSL 1.1.1f  31 Mar 2020

The request has been successfully imported with a short name of: client1
You may now use this name to perform signing operations on this request.

facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/CA$ ./easyrsa sign-req client client1

Note: using Easy-RSA configuration from: ./vars

Using SSL: openssl OpenSSL 1.1.1f  31 Mar 2020


You are about to sign the following certificate.
Please check over the details shown below for accuracy. Note that this request
has not been cryptographically verified. Please be sure it came from a trusted
source or that you have verified the request checksum with the sender.

Request subject, to be signed as a client certificate for 1080 days:

subject=
    commonName                = client1


Type the word 'yes' to continue, or any other input to abort.
  Confirm request details: 

Aborting without confirmation.
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/CA$ cp pki/issued/client1.crt ../client-configs/keys/
cp: impossible d'évaluer 'pki/issued/client1.crt': Aucun fichier ou dossier de ce type
facon-piscine@facon-piscine:/media/facon-piscine/server/facon-piscine/CA$ 

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

C'est bon j'avais pas vu la question qui me demandait de mettre YES pour valider

par contre pour démarrer l'étape 4 on est toujours sur la clé ou je dois revenir à la racine du PC ?

Dernière modification par polinux (Le 19/11/2022, à 17:10)

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

J'ai bien avancé

J'ai supposé que vu la commande et les dossiers cités on était revenu à la racine du pc.
Je suis arrivé à la fin du tuto et la dernière commande me donne un retour que j'ai du mal à analyser :
Il y a le mot FAILURE  et ça j'aime pas

facon-piscine@facon-piscine:~$ sudo systemctl status openvpn-server@server.service
● openvpn-server@server.service - OpenVPN service for server
     Loaded: loaded (/lib/systemd/system/openvpn-server@.service; enabled; vend>
     Active: activating (auto-restart) (Result: exit-code) since Sat 2022-11-19>
       Docs: man:openvpn(8)
             https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
             https://community.openvpn.net/openvpn/wiki/HOWTO
    Process: 15027 ExecStart=/usr/sbin/openvpn --status /run/openvpn-server/sta>
   Main PID: 15027 (code=exited, status=1/FAILURE)
lines 1-8/8 (END)

Je vais donc attendre sagement ton retour et ton commentaire

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Etape 4 : Ca n'a pas d'importance, les chemins sont absolus.

Je vais modifier le #46 (je t'indiquerai quand ce sera fait, je ne pense pas avoir le temps de le faire maintenant). Je dois :
- y ajouter ce qu'il faut pour corriger l'erreur sur la génération du certificat
- trouver un moyen pour mettre le chemin absolu pour éviter les erreurs en cas d'arrêt/reprise de la procédure

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Donne le retour de :

cat /var/log/openvpn/openvpn.log

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Un grand merci pour ton aide, moi aussi je dois lâcher l'affaire pour ce soir .

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

ok, pas de problème.

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Je ne sais pas si cela à un lien mais je n'arrive plus à connecter mon second poste sur Laurux
Impossible de se connecter à MySQL .

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Peut être ce que tu as fait hier avec le pare feu (UFW). Il faut que je regarde en détail ce qu'a fait Ocean Digital.

EDIT : je viens de regarder ce qui est fait avec le pare-feu. En fait c'est un MASQUERADE du trafic du VPN. Aucune incidence sur ton serveur SQL.

Dernière modification par NicoApi73 (Le 19/11/2022, à 22:11)

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

voici le retour de ma console serveur :

facon-piscine@facon-piscine:~$ cat /var/log/openvpn/openvpn.log
cat: /var/log/openvpn/openvpn.log: Aucun fichier ou dossier de ce type
facon-piscine@facon-piscine:~$ 

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Donne moi le retour des commandes suivantes (sur le serveur) :

ls -l /etc/openvpn/server/

puis

cat /etc/openvpn/server/server.conf

Aucune de ces commandes ne donnent d'information privée.

Dernière modification par NicoApi73 (Le 20/11/2022, à 00:20)

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

voici les retours :

facon-piscine@facon-piscine:~$ ls -l /etc/openvpn/server/
total 24
-rw------- 1 root root   749 nov.  19 16:36 ca.crt
-rw-r--r-- 1 root root 10906 nov.  19 17:26 server.conf
-rw------- 1 root root   306 nov.  19 16:34 server.key
-rw------- 1 root root   636 nov.  19 16:36 ta.key
facon-piscine@facon-piscine:~$

et aussi

facon-piscine@facon-piscine:~$ cat /etc/openvpn/server/server.conf
#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
################################################## Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
proto tcp
;proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key  # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh2048.pem 2048
;dh dh2048.pem
dh none
# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist /var/log/openvpn/ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret
tls-crypt ta.key
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
;cipher AES-256-CBC
cipher AES-256-GCM
auth SHA256
# Enable compression on the VPN link and push the
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo
# If you enable it here, you must also
# enable it in the client config file.
;comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status /var/log/openvpn/openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 0
facon-piscine@facon-piscine:~$ 

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Bonjour,

Il te manque le fichier server.crt dans /etc/openvpn/server. Branche ta clé puis passe la commande :

sudo cp /media/facon-piscine/server/facon-piscine/CA/pki/issued/server.crt /etc/openvpn/server/ 

Dans ton fichier de  conf (/etc/openvpn/server.conf), décommente la ligne en supprimant le ";"

;log         /var/log/openvpn/openvpn.log

devient

log         /var/log/openvpn/openvpn.log

Tu devrais pouvoir démarrer le serveur.

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

voici le retour de la première commande :

facon-piscine@facon-piscine:~$ sudo cp /media/facon-piscine/server/facon-piscine/CA/pki/issued/server.crt /etc/openvpn/server/ 
[sudo] Mot de passe de facon-piscine : 
cp: impossible d'évaluer '/media/facon-piscine/server/facon-piscine/CA/pki/issued/server.crt': Aucun fichier ou dossier de ce type
facon-piscine@facon-piscine:~$ 

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

Soit ta clé n'est pas montée, soit le chemin a changé.

EDIT : que donne

ls /media/facon-piscine/server/facon-piscine/CA/pki

Vérifie le point de montage de ta clé avec

lsblk

Tu devrais y trouver quelque chose comme ceci :

sda           8:0    1   7,2G  0 disk 
└─sda1        8:1    1   7,2G  0 part /media/facon-piscine/server

Ou alors une étape ne s'est pas bien passée, on va d'abord voir si on trouve. Sinon, je vois ce qui a peut être été râté. (pas bien grave)

Dernière modification par NicoApi73 (Le 20/11/2022, à 11:32)

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

facon-piscine@facon-piscine:~$ ls /media/facon-piscine/server/facon-piscine/CA/pki
ca.crt           index.txt       openssl-easyrsa.cnf  revoked
certs_by_serial  index.txt.attr  private              safessl-easyrsa.cnf
ecparams         index.txt.old   renewed              serial
extensions.temp  issued          reqs                 serial.old
facon-piscine@facon-piscine:~$ 

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

facon-piscine@facon-piscine:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0         7:0    0 114,9M  1 loop /snap/core/13741
loop1         7:1    0     4K  1 loop /snap/bare/5
loop2         7:2    0   115M  1 loop /snap/core/13886
loop3         7:3    0  55,6M  1 loop /snap/core18/2566
loop4         7:4    0  63,2M  1 loop /snap/core20/1634
loop5         7:5    0    79M  1 loop /snap/icloud-for-linux/235
loop6         7:6    0  72,8M  1 loop /snap/core22/310
loop7         7:7    0  70,4M  1 loop /snap/core22/275
loop8         7:8    0  81,3M  1 loop /snap/gtk-common-themes/1534
loop9         7:9    0    79M  1 loop /snap/icloud-for-linux/238
loop10        7:10   0 346,3M  1 loop /snap/gnome-3-38-2004/115
loop11        7:11   0 260,7M  1 loop /snap/kde-frameworks-5-core18/32
loop12        7:12   0  45,9M  1 loop /snap/snap-store/592
loop13        7:13   0    48M  1 loop /snap/snapd/17336
loop14        7:14   0  55,6M  1 loop /snap/core18/2620
loop15        7:15   0   219M  1 loop /snap/gnome-3-34-1804/77
loop16        7:16   0 346,3M  1 loop /snap/gnome-3-38-2004/119
loop17        7:17   0 162,9M  1 loop /snap/gnome-3-28-1804/145
loop18        7:18   0 164,8M  1 loop /snap/gnome-3-28-1804/161
loop19        7:19   0  49,7M  1 loop /snap/snapd/17576
loop20        7:20   0  63,2M  1 loop /snap/core20/1695
loop21        7:21   0 918,3M  1 loop /snap/libreoffice/262
loop22        7:22   0   219M  1 loop /snap/gnome-3-34-1804/72
loop23        7:23   0 521,4M  1 loop /snap/gimp/393
loop24        7:24   0 918,5M  1 loop /snap/libreoffice/260
loop25        7:25   0  45,9M  1 loop /snap/snap-store/599
loop26        7:26   0  91,7M  1 loop /snap/gtk-common-themes/1535
loop27        7:27   0   140K  1 loop /snap/gtk2-common-themes/13
loop28        7:28   0 391,3M  1 loop /snap/gimp/383
sda           8:0    1   7,2G  0 disk 
└─sda1        8:1    1   7,2G  0 part /media/facon-piscine/server
nvme0n1     259:0    0 232,9G  0 disk 
├─nvme0n1p1 259:1    0   260M  0 part /boot/efi
├─nvme0n1p2 259:2    0    16M  0 part 
├─nvme0n1p3 259:3    0  93,3G  0 part 
├─nvme0n1p4 259:4    0     1G  0 part 
└─nvme0n1p5 259:5    0 138,4G  0 part /
facon-piscine@facon-piscine:~$ 

polinux

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

donc j'ai bien la ligne media ,
dans la commande  :

sudo cp /media/facon-piscine/server/facon-piscine/CA/pki/issued/server.crt /etc/openvpn/server/ 

EDIT  pourquoi y a t'il facon-piscine entre server et CA ?
question idiote oublie la

Dernière modification par polinux (Le 20/11/2022, à 11:51)

NicoApi73

Re : Connexion distante d'un PC sur mon serveur [RESOLU]

La question n'est pas idiote.
/media est le répertoire qui sert de point de montage pour les disques amovibles (clés USB entre autre)
Dans ce répertoire, un sous-répertoire est créé par utilisateur qui monte un disque amovible (le premier facon-piscine)
Ensuite, ta clé est montée (elle s'appelle server)
Donc la racine de ta clé est à /media/facon-piscine/server

Comme elle est en ext4, pour pouvoir gérer aisément les fichiers dedans, je t'ai fait créé un répertoire utilisateur, appelé facon-piscine (puisque c'est ton utilisateur), ce qui permet de mettre éventuellement d'autres utilisateurs, comme c'est fait dans /home.

Et donc l'équivalent du /home/$USER sur ta clé est /media/facon-piscine/server/facon-piscine

Que donne :

ls /media/facon-piscine/server/facon-piscine/CA/pki/issued

Dernière modification par NicoApi73 (Le 20/11/2022, à 12:41)