WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.510 --> 00:00:08.190
In this video,

1
00:00:08.190 --> 00:00:11.410
you'll learn how to audit your Lennox host using logging and audit D.

2
00:00:13.160 --> 00:00:16.940
Our plan is to explore authentication, auditing and logging on your Lennox host.

3
00:00:17.400 --> 00:00:20.860
You'll use the audit D application to create a file system rule to track

4
00:00:21.140 --> 00:00:21.973
security events.

5
00:00:22.520 --> 00:00:25.620
You learn how to search logs with security information on your host.

6
00:00:27.460 --> 00:00:29.390
When looking at potential security issues,

7
00:00:29.490 --> 00:00:33.070
you can use an application called Audit D to track events on a host.

8
00:00:33.480 --> 00:00:37.710
Audit D is an application that writes events from the Linux auditing system in

9
00:00:37.710 --> 00:00:41.910
the kernel to a log. In our case, that log is audit dot log.

10
00:00:42.790 --> 00:00:45.570
The audit application is made up of four different tools.

11
00:00:45.980 --> 00:00:49.060
Audit D is the Damon that runs in the background audit.

12
00:00:49.440 --> 00:00:51.820
CTL can make changes to the kernel audit system.

13
00:00:52.280 --> 00:00:54.660
We will use this command when we're setting up our rule.

14
00:00:55.660 --> 00:00:58.480
AU search allows you to search for security events in the audit log.

15
00:00:59.100 --> 00:01:02.920
And au report creates a report based on the audit log entries.

16
00:01:03.920 --> 00:01:06.910
Rules are created either from the command line or they can be kept in the audit.

17
00:01:07.190 --> 00:01:11.170
D rules, D directory security logging.

18
00:01:11.750 --> 00:01:14.610
So system D logs information into one convenience spot.

19
00:01:15.180 --> 00:01:20.150
This part of System D is called Journal Before System D services wrote to many

20
00:01:20.150 --> 00:01:22.430
different files using different log formats.

21
00:01:23.150 --> 00:01:26.810
You could search logs and journal by using the journal CTL command.

22
00:01:26.950 --> 00:01:28.090
We will do that a bit later.

23
00:01:28.890 --> 00:01:33.860
Security events are captured in secure dot log information like logins

24
00:01:33.860 --> 00:01:35.140
via console and ssh.

25
00:01:35.840 --> 00:01:40.580
Pseudo and SU commands user and group creation are all written to this secured

26
00:01:40.580 --> 00:01:43.190
out log file. Okay, let's get started.

27
00:01:45.490 --> 00:01:48.980
Okay, so the first thing we're gonna do is set up a rule on audit D.

28
00:01:49.350 --> 00:01:53.220
Audit D should already be installed on your Amazon Lenux host, but if it's not,

29
00:01:53.360 --> 00:01:56.980
you can just do the pseudo yum install audit D.

30
00:01:57.660 --> 00:01:59.920
And don't forget you have to, it's installed.

31
00:02:00.120 --> 00:02:04.320
You'll have to make sure it is started using the system D CTL command.

32
00:02:05.050 --> 00:02:05.850
I was thinking to keep it,

33
00:02:05.850 --> 00:02:09.820
the theme with the rest of these videos is that we create a file system rule

34
00:02:10.010 --> 00:02:14.620
that watches for any new files inside the user local engineering directory when

35
00:02:14.620 --> 00:02:18.780
a new file is created or change is made to it and Audit D should created an

36
00:02:18.780 --> 00:02:19.613
event for it.

37
00:02:20.180 --> 00:02:24.920
So we're gonna need pseudo elevated privileges to do anything we want to do with

38
00:02:24.920 --> 00:02:28.160
audit. Since the audit log is actually, um,

39
00:02:28.540 --> 00:02:33.350
you need elevated permissions to look at it and to interact with any of

40
00:02:33.370 --> 00:02:36.070
the uh, kernel audit system as well. Okay,

41
00:02:36.210 --> 00:02:40.310
so I am gonna cut and paste this command here and then we can talk about it.

42
00:02:42.970 --> 00:02:43.803
Okay,

43
00:02:44.000 --> 00:02:48.860
so you could see here that we're calling the audit CTL command and the

44
00:02:48.860 --> 00:02:51.980
lowercase W is for watching a filer directory.

45
00:02:51.980 --> 00:02:54.700
And in this case we're gonna watch the user local engineering directory

46
00:02:54.700 --> 00:02:58.940
recreated earlier on in the series. The dash P is for.

47
00:02:59.820 --> 00:03:04.360
So there's the read, write and then access and execute here.

48
00:03:04.360 --> 00:03:07.200
These are not like the standard permissions we learned about earlier when we

49
00:03:07.200 --> 00:03:08.720
looked at, when we were talking about users and groups,

50
00:03:09.380 --> 00:03:11.560
but these are kernel level system calls.

51
00:03:12.820 --> 00:03:14.600
So here we're using the W and the A.

52
00:03:14.620 --> 00:03:18.440
So we're basically looking for any type of writing to a file.

53
00:03:19.060 --> 00:03:23.280
And then the A is for any type of modifications or may I modifying the

54
00:03:23.280 --> 00:03:27.360
attributes of that file or directory in this case. K we're using here.

55
00:03:27.360 --> 00:03:31.240
Is this an easy identifier that we can find in our events and logs and it allows

56
00:03:31.240 --> 00:03:34.360
us to search for it when we use a Aus search later. Okay,

57
00:03:34.540 --> 00:03:39.010
so let's go ahead and hit enter and there's no error come back,

58
00:03:39.010 --> 00:03:42.250
which is good. If there was any problem with it,

59
00:03:42.350 --> 00:03:46.890
the application would give us an error. So with that being said, let's go ahead.

60
00:03:48.100 --> 00:03:52.810
We're gonna create a file in user local engineering called

61
00:03:53.010 --> 00:03:53.850
malicious dot text.

62
00:03:59.550 --> 00:04:03.810
And so by, remember by using the, the touch command, if the file does not exist,

63
00:04:03.820 --> 00:04:07.280
it'll create it for us. Okay?

64
00:04:07.660 --> 00:04:11.440
So it is now in aside the user local engineering directory,

65
00:04:12.620 --> 00:04:15.690
these events should now be captured inside our off log.

66
00:04:15.950 --> 00:04:18.570
So instead of searching this log by hand, which you could do,

67
00:04:18.860 --> 00:04:22.090
we're gonna go ahead and use the AU search command. And there's,

68
00:04:22.090 --> 00:04:23.610
there's multiple ways you could do this.

69
00:04:23.750 --> 00:04:28.300
We could search by our engineering dash modify keyword here

70
00:04:28.760 --> 00:04:32.220
or we could search by a file or directory. So let's do this first.

71
00:04:32.240 --> 00:04:36.640
I'm gonna clear the screen and then we're gonna use au search.

72
00:04:37.300 --> 00:04:41.480
And then I'm gonna use dash F for the file and we'll say engineering

73
00:04:43.640 --> 00:04:47.360
directory malicious txt file. Okay.

74
00:04:49.040 --> 00:04:53.730
Okay. So there is a lot of structured output here and this is so,

75
00:04:54.310 --> 00:04:57.490
um, if you want to pipe this into your monitoring system,

76
00:04:57.490 --> 00:05:00.250
in case you wanna get alerted on some type of events, which you should do,

77
00:05:01.070 --> 00:05:05.690
you can parse this file. There's a specific format and obviously, um,

78
00:05:05.690 --> 00:05:07.330
we're not gonna go into how to parse it here,

79
00:05:07.750 --> 00:05:10.650
but there's a few things that I want you to pay attention to the most.

80
00:05:11.580 --> 00:05:16.080
So here it tells us right here that there is a user local file.

81
00:05:16.540 --> 00:05:19.960
You can see the I node of when it got created, the mode of the file.

82
00:05:20.700 --> 00:05:25.570
You can see go down here, we could see another item here,

83
00:05:25.740 --> 00:05:29.010
which is the directory, the eye note of the directory,

84
00:05:29.890 --> 00:05:33.620
stuff along those lines. Then here, if you come here on this type,

85
00:05:33.620 --> 00:05:35.940
this is the SIS call cuz you have different types here.

86
00:05:35.960 --> 00:05:40.280
So this was the create type, um, this was actually creating the file,

87
00:05:40.730 --> 00:05:43.680
right here's the path, this is the type path,

88
00:05:44.240 --> 00:05:49.210
this is type current working directory. And this is where I made the call from,

89
00:05:49.210 --> 00:05:52.130
which was home EC two user. And here's the system call,

90
00:05:52.130 --> 00:05:56.610
the kernel level system call that was actually used to create this file.

91
00:05:57.700 --> 00:06:00.840
And as you could see here, it says success. Yes.

92
00:06:01.380 --> 00:06:03.880
So obviously if we were monitoring this, looking for this,

93
00:06:04.420 --> 00:06:07.320
we would be looking for some sort of malicious type of activity where it was

94
00:06:07.320 --> 00:06:08.400
successful. I mean,

95
00:06:08.400 --> 00:06:11.240
maybe you want something that was not successful too to give you a heads up or a

96
00:06:11.240 --> 00:06:14.400
warning that somebody's trying stuff. But I feel like that might be, um,

97
00:06:14.600 --> 00:06:16.400
a lot of information you'd be getting.

98
00:06:17.190 --> 00:06:18.810
You could see the command that was used here,

99
00:06:18.810 --> 00:06:22.250
which was touch and what we executed the executable,

100
00:06:22.540 --> 00:06:26.090
which was under user bin touch. And here's our key that we made.

101
00:06:26.090 --> 00:06:29.090
So if we wanted to search by the key, we absolutely could do that.

102
00:06:29.710 --> 00:06:33.570
And I will show you how to do that really quick. So if we get rid of,

103
00:06:34.190 --> 00:06:38.220
you can do dash k and then we say engineering

104
00:06:39.170 --> 00:06:40.003
modify.

105
00:06:41.540 --> 00:06:46.440
So you can see here that we have two outputs now and the

106
00:06:46.440 --> 00:06:50.080
first output is that there was a config change that we added a rule,

107
00:06:50.260 --> 00:06:52.640
we added the key. So we, you can safely ignore that,

108
00:06:52.640 --> 00:06:54.400
that was just us running our uh, command.

109
00:06:54.660 --> 00:06:58.640
But you can see is here we have the exact same output and rule that we did

110
00:06:58.640 --> 00:07:03.600
before. So those are two ways of you being able to

111
00:07:05.460 --> 00:07:07.280
add a rule and be able to search for it.

112
00:07:07.280 --> 00:07:09.640
Obviously searching for it is not good enough.

113
00:07:09.860 --> 00:07:12.360
You definitely wanna pipe this into your monitoring system so you can get

114
00:07:12.360 --> 00:07:15.840
alerted if somebody's doing something malicious, uh, any bad actor.

115
00:07:17.090 --> 00:07:19.990
So there's other things that you can, um, do as well.

116
00:07:20.010 --> 00:07:21.470
Not just file systems for audit.

117
00:07:22.010 --> 00:07:26.790
You can say if this pseudo command gets run or say you have a very special

118
00:07:27.020 --> 00:07:30.790
sensitive command that only a few people get to be able to run it and you want

119
00:07:30.790 --> 00:07:33.630
to be able to watch that command, you can set up audit,

120
00:07:33.630 --> 00:07:36.910
you can set a rule for audit D to manage that as well. Um,

121
00:07:36.910 --> 00:07:39.870
you can manage certain system calls like um,

122
00:07:40.090 --> 00:07:43.510
create user or something along those lines and you wanna watch those,

123
00:07:43.510 --> 00:07:47.190
that type of activity you have all that thing I just showed you the simple file

124
00:07:47.190 --> 00:07:50.510
system one just to get you get your feet wet in the, uh,

125
00:07:50.530 --> 00:07:52.270
so you can start a foundation learn.

126
00:07:52.270 --> 00:07:54.750
Obviously there's a lot more you can do with audit d

127
00:07:58.220 --> 00:07:59.440
I'm gonna clear the screen here.

128
00:08:00.830 --> 00:08:05.450
The other command that you can use is AU report and

129
00:08:05.720 --> 00:08:10.450
what you can do, this will basically run a summary of everything in that log.

130
00:08:10.790 --> 00:08:14.490
So the output's gonna be a lot because I'm, I'm not limiting it to anything,

131
00:08:14.510 --> 00:08:16.210
but I'll go ahead and run it.

132
00:08:16.310 --> 00:08:21.290
You do pseudo AE report and here it's gonna run from February to

133
00:08:21.290 --> 00:08:22.690
March. So there's a lot of information.

134
00:08:22.710 --> 00:08:26.850
You can tell how many failed login attempts and we'll actually look at those in

135
00:08:26.850 --> 00:08:29.530
a second. How many logins, um,

136
00:08:29.530 --> 00:08:33.290
different host names that are in that log from people. How many try, uh,

137
00:08:33.290 --> 00:08:34.290
fail failed CIS calls.

138
00:08:34.310 --> 00:08:38.250
That's probably something I did by not putting pseudo in front of it that needed

139
00:08:38.250 --> 00:08:42.850
to be done. Um, but anyway, you get the idea and this would be like a good,

140
00:08:43.110 --> 00:08:43.610
um,

141
00:08:43.610 --> 00:08:47.570
a good plan to email yourself like this once a week or whatever the frequency

142
00:08:47.570 --> 00:08:49.410
you need to get an idea of what's going on.

143
00:08:49.410 --> 00:08:51.650
And then maybe you could map trends to this.

144
00:08:54.240 --> 00:08:58.540
Okay, let's pivot away from audit D right now and let's learn how to do general

145
00:08:58.560 --> 00:09:02.100
authentication and security searching using the journal CTL command.

146
00:09:02.760 --> 00:09:06.460
So Journal CTL is a a very large application.

147
00:09:06.670 --> 00:09:08.180
There are a lot of flags,

148
00:09:08.440 --> 00:09:11.500
but so we're only gonna focus on a couple ones here and we're gonna base it more

149
00:09:11.520 --> 00:09:16.140
to looking at s SSH authentication and like system D, login D.

150
00:09:16.960 --> 00:09:20.660
So there are three main flags that we're gonna use when searching for these

151
00:09:20.770 --> 00:09:24.340
logs. We're gonna use the dash U, which tells it what unit to search.

152
00:09:24.340 --> 00:09:26.700
Our case would be S S H D. Um,

153
00:09:26.700 --> 00:09:30.820
there's an R which shows reverse showing the newest logs first and then we're

154
00:09:30.820 --> 00:09:34.300
gonna do a dash dash since, cuz we, we don't wanna search for all time.

155
00:09:34.300 --> 00:09:35.820
We're only gonna search starting from yesterday.

156
00:09:36.000 --> 00:09:37.980
So I'm gonna go ahead and paste the command in and you'll,

157
00:09:37.980 --> 00:09:42.420
it'll make a little bit more sense. Okay,

158
00:09:42.720 --> 00:09:47.540
so here we have the journal CTL command. Obviously, um,

159
00:09:47.640 --> 00:09:52.540
the reason why we're using pseudo is because some logs are not owned by the

160
00:09:52.580 --> 00:09:55.220
e C two user and you would need pseudo to be able to look at 'em.

161
00:09:55.610 --> 00:09:59.420
Journal CTL will kind of quietly just not read those logs if it doesn't have

162
00:09:59.420 --> 00:10:02.940
permission and not warn you. So it's a pretty good habit when you're searching,

163
00:10:03.080 --> 00:10:06.620
uh, a bunch of different logs, especially secure logs which are, um,

164
00:10:06.620 --> 00:10:10.620
more protected than you should preface it with pseudo. Okay,

165
00:10:10.620 --> 00:10:14.800
so here we're using the dash U to say what unit,

166
00:10:15.030 --> 00:10:19.120
what unit are we going to get logs from? And in this case the s SSH server.

167
00:10:20.280 --> 00:10:22.780
So we also have the system D, login D

168
00:10:24.300 --> 00:10:28.560
and the system D login D is responsible for managing user logins for the system

169
00:10:28.640 --> 00:10:31.280
D system. It keeps track of user sessions amongst other things.

170
00:10:31.500 --> 00:10:33.200
So we wanna look in both of those.

171
00:10:34.820 --> 00:10:39.640
And then we are using the dash R here and that is to show all the newest logs

172
00:10:39.640 --> 00:10:41.560
first. And then here we're gonna do dash,

173
00:10:41.560 --> 00:10:44.480
dash since we're gonna say since yesterday. Okay,

174
00:10:44.620 --> 00:10:47.120
so I'm gonna go ahead and return. There's gonna be a lot of output.

175
00:10:47.120 --> 00:10:50.680
It's gonna drop us into a page where you hit space bar to keep paging,

176
00:10:51.340 --> 00:10:54.960
but let's go ahead and see what that looks like. Okay,

177
00:10:55.540 --> 00:10:58.480
so as you can see one thing, there's a specific format.

178
00:10:58.780 --> 00:11:01.680
You get the date, the host,

179
00:11:02.660 --> 00:11:06.300
these are the different columns. And then the, the service unit,

180
00:11:06.790 --> 00:11:09.980
which is S S H D here. And then the log entry.

181
00:11:11.370 --> 00:11:13.870
So couple things here.

182
00:11:14.770 --> 00:11:17.380
Journal does not try to fit it all onto the screen.

183
00:11:17.930 --> 00:11:22.500
Instead what it does is it lets you scroll to the right to see more. Um,

184
00:11:22.640 --> 00:11:24.020
so if you hit the right arrow,

185
00:11:24.520 --> 00:11:28.500
you could see that we now get more of the, um,

186
00:11:29.920 --> 00:11:34.180
the remainder of what is not in the logs that you can't see on the,

187
00:11:34.180 --> 00:11:36.100
at the screen. Um, I,

188
00:11:36.120 --> 00:11:38.340
I'm gonna leave it here cause I think it's just a little bit better view,

189
00:11:38.340 --> 00:11:41.380
especially with the blown up for the recording. Um,

190
00:11:41.760 --> 00:11:44.140
but let's just go over a couple things that you're seeing here.

191
00:11:44.640 --> 00:11:49.270
So you're seeing these connection close by, um, these, uh, IP addresses.

192
00:11:49.270 --> 00:11:52.470
You see these pre-ops invalid user support.

193
00:11:52.940 --> 00:11:57.840
So you can see here that this is basically bad actors trying to break

194
00:11:57.990 --> 00:12:01.040
into, uh, my e c two instance. Um,

195
00:12:01.600 --> 00:12:06.560
somebody was doing a port scan and found this instance was running s ssh and now

196
00:12:06.910 --> 00:12:11.080
they are just looking and trying to brute force their way in with a user,

197
00:12:11.540 --> 00:12:15.200
all the different users and any kind of passwords they're finding in rainbow

198
00:12:15.340 --> 00:12:20.260
tables or or password hash dumps. And so if we just go down,

199
00:12:20.320 --> 00:12:24.500
you could see that all these invalid user ll um,

200
00:12:24.500 --> 00:12:28.730
during pre-op. So these are all unsuccessful attempts,

201
00:12:28.750 --> 00:12:29.610
but as you could see,

202
00:12:30.450 --> 00:12:34.740
this box is being hammered constantly with people trying to get in. Um,

203
00:12:34.740 --> 00:12:38.490
if you look at these timestamps, I mean it's literally every,

204
00:12:38.580 --> 00:12:41.330
every like every few minutes, um,

205
00:12:41.720 --> 00:12:44.730
there's multiple attempts and this is because somebody's scripting this.

206
00:12:44.730 --> 00:12:47.930
They're uh, they're automating this. Um, and so they're trying to get in.

207
00:12:48.570 --> 00:12:52.190
And the next video, we're actually gonna make some tweaks here to try to, uh,

208
00:12:52.190 --> 00:12:55.870
help fix this. So you see here we have reverse mapping where this,

209
00:12:55.930 --> 00:12:59.870
the number that they're trying to connect from Dou, which is Russia,

210
00:13:00.380 --> 00:13:03.550
does not actually resolve to the IP address they're coming from.

211
00:13:03.550 --> 00:13:05.580
They're trying to spoof it. You have,

212
00:13:05.680 --> 00:13:10.340
Ali has a user here and so they're just going through all the different things.

213
00:13:10.440 --> 00:13:14.700
So nothing to really worry about there except that we're to know that you're

214
00:13:14.700 --> 00:13:19.540
always under attack and having understanding that someone's watching these logs

215
00:13:19.540 --> 00:13:22.980
and looking for these things knows because what you don't wanna see is a

216
00:13:22.980 --> 00:13:25.980
successful session being created for one of these, uh,

217
00:13:25.980 --> 00:13:29.220
users that is not you or somebody that you want in the system.

218
00:13:29.860 --> 00:13:33.630
I'll scroll down a little bit. You can see it just goes on and on and on.

219
00:13:35.440 --> 00:13:39.910
There is, there'll be, uh, system D log event, the system D login, uh,

220
00:13:39.910 --> 00:13:43.670
login D events. What they will show, um, when you get to them,

221
00:13:43.670 --> 00:13:46.190
they'll just show that a new session was created for this user.

222
00:13:46.490 --> 00:13:50.750
And so if you saw new session, so like we can just do new.

223
00:13:53.100 --> 00:13:57.520
So as you can see, we have a new session for this user. This is from a,

224
00:13:58.250 --> 00:14:01.620
from a login for me, what you would want want to see is that,

225
00:14:02.830 --> 00:14:07.360
that happen on a user that you did not expect,

226
00:14:07.940 --> 00:14:11.550
uh, to be logging into your system. Okay,

227
00:14:11.650 --> 00:14:14.350
I'm gonna hit Q to get out of this journal.

228
00:14:17.240 --> 00:14:19.670
I'm gonna clear the screen. Okay,

229
00:14:19.930 --> 00:14:23.870
so another handy thing that you could do in with journal CTLs,

230
00:14:23.870 --> 00:14:26.710
if you wanna look for errors, obviously, you know,

231
00:14:26.710 --> 00:14:31.470
different services logged is this standard out standard error, stand it in. Um,

232
00:14:31.530 --> 00:14:32.990
and so this, any law,

233
00:14:33.170 --> 00:14:38.150
any errors that are being logged as a error log journal CTL can find as well.

234
00:14:38.170 --> 00:14:40.630
So we'll get rid of the dash since,

235
00:14:40.890 --> 00:14:44.630
and then what we're gonna do is we're gonna do a dash P for priority and there's

236
00:14:44.630 --> 00:14:46.630
different, the differing logging priorities here.

237
00:14:46.810 --> 00:14:50.750
The number three means errors and that's all we'll just focus on right here.

238
00:14:51.560 --> 00:14:55.740
And as you can see here we go maximum authentication attempts.

239
00:14:56.120 --> 00:15:00.860
So these people trying to log in are reaching the default SS h

240
00:15:01.240 --> 00:15:04.740
max authentication attempts, which I believe is six by default.

241
00:15:06.320 --> 00:15:09.700
And so these people are trying six different times before, uh,

242
00:15:09.700 --> 00:15:13.140
with the same user before they are telling you've re or you've reached the

243
00:15:13.140 --> 00:15:17.540
maximum attempts. No more tries with that. So as you can see,

244
00:15:17.540 --> 00:15:20.560
like there is an obscene amount of 'em here,

245
00:15:20.560 --> 00:15:24.320
you see people trying to log in its route and like I said in the next video when

246
00:15:24.320 --> 00:15:27.520
we talk about hardening ssh, we'll look at that as well. Okay,

247
00:15:27.540 --> 00:15:29.240
I'm gonna hit Q to get out of this as well.

248
00:15:29.360 --> 00:15:33.550
I think you get the idea and then clear the screen. Okay,

249
00:15:33.970 --> 00:15:37.470
so we've covered audit D here. We've made a simple file system rule,

250
00:15:37.730 --> 00:15:39.630
we know where to look for logs. Um,

251
00:15:39.630 --> 00:15:42.150
we know how to look at those event logs in the audit log.

252
00:15:43.150 --> 00:15:47.850
We also learned some basics here on, uh, journal ctl. So let's go over for, uh,

253
00:15:47.850 --> 00:15:50.810
go back over and let's do a full recap on what we did in this video.

254
00:15:52.960 --> 00:15:55.290
Okay, so let's talk about what we did in this video.

255
00:15:55.910 --> 00:15:59.450
So you learn about auditing and authentication logging on your Lennox host.

256
00:15:59.990 --> 00:16:04.450
You used the audit CTL command and created a rule to watch for right access and

257
00:16:04.450 --> 00:16:06.330
change events. For the engineering directory,

258
00:16:07.160 --> 00:16:11.540
you used the AU search and journal CTL commands to find file system events,

259
00:16:11.790 --> 00:16:16.130
login attempts, and s SSH sessions. In the next video,

260
00:16:16.130 --> 00:16:19.450
you'll learn how to harden your SS h server. See you soon.
