wamster/BUT2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
Alexis WAMSTER
2023-10-23 13:23:36 +02:00
parent 667dae6f1a
commit 322b22f9bf
5711 changed files with 72953 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
SCR/IMUNES/TP22/ETC-BIND/README Normal file
View File

@@ -0,0 +1,52 @@
--------------------------------------------------------------------------
DEBUT DE L'EPREUVE :
-------------------
ATTENTION : Un malus sera applique en cas de non-respect des consignes.
-----------------------------------------------------------------------
Creer le repertoire <login>-scr.2.1 directement dans le domicile de user1
<login> est a remplacer par son identifiant sur le reseau de l'IUT
de Fontainebleau, tout en minuscules donc, et sans ajouter les symboles < >
Ce repertoire sera appele le repertoire de base.
Se placer dans le repertoire ~user1/<login>-scr.2.1
Deplacer le fichier devoir dans le repertoire de base.
Creer le fichier <login>-reponses.txt et placer NOM/PRENOM/NOM_MACHINE/
au debut du fichier.
C'est dans ce fichier que toutes les reponses
seront donnees, chacune precedee du numero de la question. Dans la suite,
on appellera ce fichier simplement le fichier reponses.
Le fichier reponses est un fichier texte saisi a l'aide d'un editeur de texte
type vi/vim, emacs, etc. En particulier les formats .doc, .odt, .pdf, ne sont
pas acceptes et entrainent la note 0.
Desarchiver le devoir. Le travail a faire est decrit dans le fichier TaF.
FIN DE L'EPREUVE :
----------------
ATTENTION : Un malus sera applique en cas de non-respect des consignes.
-----------------------------------------------------------------------
VERIFIER QU'ON EST BIEN DANS LE REPERTOIRE DE BASE <login>-scr.2.1
qui se trouve directement dans le domicile de user1
---------------------------------------------------------------------
On rendra l'archive <login>-scr.2.1.tar contenant le fichier
<login>-reponses.txt et le programme <login>-number-weight.s, qui fait l'objet
d'un exercice.
S'assurer que les fichiers a archiver sont bien enregistres, qu'on a quitte
tout editeur de texte et laisser la machine allumee.
L'archive est a creer par :
tar cvf <login>-scr.2.1.tar <login>-reponses.txt <login>-number-weight.s
S'assurer que l'archive est bien dans le repertoire de base.
LAISSER LA MACHINE ALLUMEE.
-----------------------------------------------------------------------

178
SCR/IMUNES/TP22/ETC-BIND/README.Debian Normal file
View File

@@ -0,0 +1,178 @@
DNSSEC validation turned on by default as of BIND 9.8.1
-------------------------------------------------------
As of version 9.8.1.dfsg-1, BIND ships with DNSSEC validation turned on
by default. As the keys get changed over time, this means that a fresh
install of BIND will require that the admin manually upgrade bind.keys
to account for the change, before BIND will be able to resolve hosts in
DNSSEC validated zones.
Upgrading from BIND 8.X:
-----------------------
If you are upgrading an authoritative server from BIND 8.X, please install
the bind9-doc package and read /usr/share/doc/bind9-doc/misc/migration.gz,
which contains a set of notes from the BIND maintainers on what changed
that is likely to need your attention during an upgrade.
Upgrading from earlier bind9 packages:
-------------------------------------
If you installed an early version of the Debian bind9 packages, prior to
version 1:9.2.0-2 to be more precise, you may have an /etc/bind/rndc.conf
configuration file still on your system. There's nothing wrong with that,
and if you've explicitly configured keys for using rndc you may well want to
leave things exactly as they are!
However, since 9.2.0 BIND 9.X has supported an rndc.key file that both named
and rndc will read to obtain a shared key for rndc use against a daemon on
the same host. The rndc-confgen program will easily create a suitable key
file. To take advantage of this mechanism, you may want to:
remove the /etc/bind/rndc.conf file
remove the rndc key specification in the /etc/bind/named.conf file
rndc-confgen -r /dev/urandom -a
Alternatively, you can 'purge' the bind9 packages and reinstall them and you
will end up with the new behavior since it is now the default.
This is more secure than using a static key that isn't generated on a per-host
basis, and is an easy alternative to more complex key schemes if you only need
to use rndc to talk to named on the same host.
Known Issues:
------------
I've had a report that lwresd, at least, fails to work with some recent 2.5
kernels. If you see something in your logs like
loading configuration from '/etc/bind/lwresd.conf'
none:0: open: /etc/bind/lwresd.conf: permission denied
Try rebuilding with --disable-linux-caps added to the configure call in the
rules file. I'm hoping this is a temporary problem in the 2.5 kernel series,
but we'll see.
Configuration Schema:
--------------------
The Debian BIND package ships with a config that will work for the majority
of leaf servers with no user input required.
The named configuration file named.conf is located in /etc/bind, so that all
static configuration files relating to bind are in one place. If you really
don't want named.conf in /etc/bind, then the best way to handle it is probably
to replace /etc/bind/named.conf with a symlink to the location you want to use.
You could also use an option to named in the init.d script, but that only works
for named, not for things like ndc.
Zone data files for the root servers, and the forward and reverse localhost
zones are also provided in /etc/bind.
The working directory for named is now /var/cache/bind. Thus, any transient
files generated by named, such as database files for zones the daemon is
secondary for, will be written to the /var filesystem, where they belong.
To make this work, the named.conf provided uses explicitly fully-qualified
pathnames to reference the files in /etc/bind.
Unlike previous BIND packages for Debian, the named.conf and provided db.*
files are tagged as conffiles. Thus, if you just want a "caching mostly"
server configuration for a server that does not need to be authoritative for
anything else, you can run the provided configuration as-is. If you want to
hack on named.conf, or even the init.d fragment, you can feel free to. Future
package upgrades will treat your configuration changes sanely, as all Debian
packages should.
While you are free to craft whatever structure you wish for servers which need
to be authoritative for additional zones, what we suggest is that you put the
db files for any zones you are master for in /etc/bind (perhaps even in a
subdirectory structure depending on complexity), using full pathnames in the
named.conf file. Any zones you are secondary for should be configured in
named.conf with simple filenames (relative to /var/cache/bind), so the data
files will be stored in BIND's working directory (defaults to /var/cache/bind).
Zones subject to automatic updates (such as via DHCP and/or nsupdate) should be
stored in /var/lib/bind, and specified with full pathnames.
Running Chroot'ed:
-----------------
Several users have asked for Debian BIND to run in a "chroot jail". There are
various issues associated with making this the default configuration for the
package in Debian. In the meantime, reasonable instructions on how to do
this yourself are available on the web from:
http://www.tldp.org/HOWTO/Chroot-BIND-HOWTO.html
Running Non-Root:
-----------------
Recent versions of named can be invoked with options that specify a non-root
user and/or group for named. Read the named man page for more information.
Note that when running named as a user other than root, it will not be able
to find new interfaces that appear dynamically, such as during a PCMCIA card
insertion, or if you're running some flavors of IPSEC and/or IP over IP
tunnels. If you cannot live with those limitations, feel free to edit the
/etc/init.d/bind9 script to change the invocation of named.
The default is now to run as the user 'bind' (which is automatically created
in the group 'bind', if it doesn't exist), unless named.conf has been changed.
To change this, edit /etc/default/bind9
Please note that 'ndc restart' doesn't honor all the original command line
options to named, so we explicitly don't use it in the init.d script provided
with the package, and you should be careful about using it if you decide to
run named non-root.
PPP Control Script:
-----------------
Unfortunately, 'ndc reload' will not honor any command line options that were
fed to named on the initial invocation. If you can live with that, and
want to wiggle your DNS configuration when your PPP link goes up or down, the
following script fragment from Francesco Potorti` <pot@gnu.org> may be helpful
to you:
I suggest adding this as bot /etc/ppp/ip-up.d/bind and
/etc/ppp/ip-down.d/bind:
================================================================
#!/bin/sh
if [ -x /usr/sbin/ndc -a -x /usr/sbin/named ]
then
/usr/sbin/ndc reload > /dev/null
fi
================================================================
This should cause no harm in any case, and should be helpful in these
cases:
- you configure bind as a forwarder. When ppp is down, it cannot access
the network. As soon as ppp is up, it is forced by the script to try
again, and it succeeds.
- someone writes a clever script that, coupled with the `usepeerdns'
command of pppd, makes a forwarding-only bind use the right servers by
rewriting the configuration file after ppp goes up. Then the script
above makes bind reload the configuration.
Now, someone should write that clever script :-)
By the way, this is a badly wanted feature, that should help setting up
a ppp connection automatically. Currently, setting up a ppp connection
is much easier on a windows system than on linux, and there is really no
reason why it should be so, given that all the tools are there.
Apparmor Profile
----------------
If your system uses apparmor, please note that the shipped enforcing profile
works with the default installation, and changes in your configuration may
require changes to the installed apparmor profile. Please see
https://wiki.ubuntu.com/DebuggingApparmor before filing a bug against this
software.

17
SCR/IMUNES/TP22/ETC-BIND/db.tp.scr Normal file
View File

@@ -0,0 +1,17 @@
;
; BIND data file for tp.scr zone
;
$TTL 604800
@ IN SOA osiris.tp.scr. root.tp.scr. (
2 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS osiris.tp.scr.
osiris IN A 192.168.1.158
eno IN A 192.168.1.1
owt IN A 192.168.1.2
eerht IN A 192.168.1.3
ruof IN A 192.168.1.4

17
SCR/IMUNES/TP22/ETC-BIND/db.tp.scr.inv Normal file
View File

@@ -0,0 +1,17 @@
;
; BIND reverse data file for local loopback interface
;
$TTL 604800
@ IN SOA osiris.tp.scr. root.osiris.tp.scr. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS osiris.tp.scr.
158 IN PTR osiris.tp.scr.
1 IN PTR eno
2 IN PTR owt
3 IN PTR eerht
4 IN PTR ruof

17
SCR/IMUNES/TP22/ETC-BIND/db.tp.scr.inv~ Normal file
View File

@@ -0,0 +1,17 @@
;
; BIND reverse data file for local loopback interface
;
$TTL 604800
@ IN SOA osiris.tp.scr. root.tp.scr. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS osiris.tp.scr.
192.168.1.158 IN PTR osiris.tp.scr.
192.168.1.1 IN PTR eno
192.168.1.2 IN PTR owt
192.168.1.3 IN PTR eerht
192.168.1.4 IN PTR ruof

18
SCR/IMUNES/TP22/ETC-BIND/named.conf.local Normal file
View File

@@ -0,0 +1,18 @@
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "tp.scr" {
type master ;
file "/etc/bind/db.tp.scr";
};
zone "1.168.192.in-addr.arpa"{
type master ;
file "/etc/bind/db.tp.scr.inv";
};

18
SCR/IMUNES/TP22/ETC-BIND/named.conf.local~ Normal file
View File

@@ -0,0 +1,18 @@
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "tp.scr" {
type master ;
file "/etc/bind/db.tp.scr";
};
zone 1.168.192.in-addr.arpa{
type master ;
file "/etc/bind/db.tp.scr";
};

3
SCR/IMUNES/TP22/ETC-BIND/resolv.conf Normal file
View File

@@ -0,0 +1,3 @@
# Generated by resolvconf
domain tp.scr
nameserver 192.168.1.158

4
SCR/IMUNES/TP22/ETC-BIND/resolv.conf~ Normal file
View File

@@ -0,0 +1,4 @@
# Generated by resolvconf
domain arda.lan
search arda arda.lan
nameserver 172.16.1.158

169
SCR/IMUNES/TP22/dns1.imn Normal file
View File

@@ -0,0 +1,169 @@
node n0 {
type lanswitch
network-config {
hostname switch1
!
}
canvas c0
iconcoords {504 144}
labelcoords {504 167}
interface-peer {e0 n1}
interface-peer {e4 n5}
interface-peer {e1 n2}
interface-peer {e2 n3}
interface-peer {e3 n4}
}
node n1 {
type pc
network-config {
hostname eno
!
interface eth0
mac address 42:00:aa:00:00:00
ip address 192.168.1.1/24
!
interface lo0
type lo
ip address 127.0.0.1/8
ipv6 address ::1/128
!
}
canvas c0
iconcoords {144 288}
labelcoords {144 319}
interface-peer {eth0 n0}
}
node n2 {
type pc
network-config {
hostname owt
!
interface eth0
mac address 42:00:aa:00:00:01
ip address 192.168.1.2/24
!
interface lo0
type lo
ip address 127.0.0.1/8
ipv6 address ::1/128
!
}
canvas c0
iconcoords {312 384}
labelcoords {312 415}
interface-peer {eth0 n0}
}
node n3 {
type pc
network-config {
hostname eerht
!
interface eth0
mac address 42:00:aa:00:00:02
ip address 192.168.1.3/24
!
interface lo0
type lo
ip address 127.0.0.1/8
ipv6 address ::1/128
!
}
canvas c0
iconcoords {576 384}
labelcoords {576 415}
interface-peer {eth0 n0}
}
node n4 {
type pc
network-config {
hostname ruof
!
interface eth0
mac address 42:00:aa:00:00:03
ip address 192.168.1.4/24
!
interface lo0
type lo
ip address 127.0.0.1/8
ipv6 address ::1/128
!
}
canvas c0
iconcoords {792 360}
labelcoords {792 391}
interface-peer {eth0 n0}
}
node n5 {
type host
network-config {
hostname osiris
!
interface eth0
mac address 42:00:aa:00:00:04
ip address 192.168.1.158/24
!
interface lo0
type lo
ip address 127.0.0.1/8
ipv6 address ::1/128
!
}
canvas c0
iconcoords {120 192}
labelcoords {120 228}
interface-peer {eth0 n0}
}
link l0 {
color Blue
nodes {n0 n1}
bandwidth 0
}
link l4 {
color Green
nodes {n0 n5}
bandwidth 0
}
link l1 {
color Magenta
nodes {n0 n2}
bandwidth 0
}
link l2 {
color Cyan
nodes {n0 n3}
bandwidth 0
}
link l3 {
color Black
nodes {n0 n4}
bandwidth 0
}
canvas c0 {
name {Canvas0}
}
option show {
interface_names yes
ip_addresses yes
ipv6_addresses yes
node_labels yes
link_labels yes
background_images no
annotations yes
hostsAutoAssign no
grid yes
iconSize normal
zoom 1.0
}

24
SCR/IMUNES/TP22/reonse.txt Normal file
View File

@@ -0,0 +1,24 @@
TP22-------------------------------------------------------
Q3)ping: oxt: Temporary failure in name resolution
=> le DNS n'a pas été configuré sur les machine, donc la résolution ne se fait pas.
I)---------------------------------------------------------
1)
uname -r => version du noyau linux
uname -a => plus de détails sur ce noyau
/etc/os-release => plus de détails sur ce noyau
1)
apt list --installed ‘‘bind*’’
II)---------------------------------------------------------
1)sudo hcp test eno:test2
permet de copier le dossier test dans le dossier test2 de eno (= une machine de imunes)
1)sudo hcp eno:test2 test
permet de copier le dossier test2 de eno (= une machine de imunes) dans le dossier test de notre machine
III)---------------------------------------------------------

46
SCR/IMUNES/TP22/reponses_2.txt Normal file
View File

@@ -0,0 +1,46 @@
3. marche pas
I
1. uname -r
5.15.62-1-lts
2. less /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=debian
1. il est là
2. elles sont là
II
sudo hcp eno:test.txt .
sudo hcp . eno:/test.txt
III
1.
root@osiris:/usr/share/doc/bind9# gunzip README.Debian.gz
sudo hcp osiris:/usr/share/doc/bind9/README.Debian DOC
3.
named-checkzone tp.scr db.tp.scr
4.
dans named.conf.local
-----------------------
ss -na = ouvrir le port 53
machine du serveur:
- dans le /etc/resolv.conf:
domain tp.scr
nameserver 192.168.1.158
machine du maitre:
- /etc/resolv.conf
- /etc/bind/db.tp.scr
- /etc/bind/db.tp.scr.inv

32
SCR/IMUNES/TP22/reponses_2.txt~ Normal file
View File

@@ -0,0 +1,32 @@
3. marche pas
I
1. uname -r
5.15.62-1-lts
2. less /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=debian
1. il est là
2. elles sont là
II
sudo hcp eno:test.txt .
sudo hcp . eno:/test.txt
III
1.
root@osiris:/usr/share/doc/bind9# gunzip README.Debian.gz
sudo hcp osiris:/usr/share/doc/bind9/README.Debian DOC
3.
named-checkzone tp.scr db.tp.scr
4.
dans named.conf.local