WEBVTT

00:00:01.340 --> 00:00:02.670
In this final demo,

00:00:02.680 --> 00:00:06.560
we're going to look at what LaZagne will do if we just tell it to go

00:00:06.560 --> 00:00:10.720
ahead and find every password it can. In Windows,

00:00:10.780 --> 00:00:14.260
there are a lot of modules and it would take a long time to

00:00:14.260 --> 00:00:16.250
work out which software is on a machine.

00:00:17.240 --> 00:00:21.020
Getting LaZagne to try to find as many passwords as it can

00:00:21.180 --> 00:00:24.220
might not be the quietest thing to do, but it could

00:00:24.220 --> 00:00:25.950
certainly save you a lot of time.

00:00:26.940 --> 00:00:30.630
We're also going to take a look at the output formats available for

00:00:30.630 --> 00:00:36.830
LaZagne. Automation is an important part of security, so it's certainly

00:00:36.830 --> 00:00:39.560
useful when tools can generate formatted output.

00:00:40.940 --> 00:00:44.760
Starting with our LaZagne executable, we'll look at the help and

00:00:44.760 --> 00:00:48.870
see the options available. In the other demos, we've done this

00:00:48.870 --> 00:00:52.950
for individual options, but here, we're doing it at the top

00:00:52.950 --> 00:00:54.560
level without any options.

00:00:55.440 --> 00:00:55.790
Here,

00:00:55.790 --> 00:01:00.110
we can see a long list of commands we can give and each one has a number

00:01:00.110 --> 00:01:05.269
of modules beneath it. The one at the top there is all and that allows

00:01:05.269 --> 00:01:07.750
us to run every module that LaZagne has.

00:01:08.340 --> 00:01:14.130
Let's give it a try. We see it give us various passwords that it's found.

00:01:14.330 --> 00:01:15.060
That's great.

00:01:15.440 --> 00:01:19.460
But we've seen that in previous demos too, so it's perhaps no more special.

00:01:20.340 --> 00:01:23.760
Let's take a look at the verbose output Here,

00:01:23.820 --> 00:01:28.510
we can see some messages at the end in red seeing that LaZagne is trying to

00:01:28.510 --> 00:01:32.660
use the passwords it's already found to decrypt master keys.

00:01:33.540 --> 00:01:36.860
What's happening here is that it's found lots of passwords

00:01:36.920 --> 00:01:40.410
and now it's using those passwords to try to decrypt stored

00:01:40.410 --> 00:01:42.660
data for users of this machine.

00:01:43.340 --> 00:01:47.360
It's trying to use the passwords it found to find more passwords.

00:01:47.740 --> 00:01:48.360
Pretty cool.

00:01:49.340 --> 00:01:49.940
Finally,

00:01:49.950 --> 00:01:52.770
we'll get a look at getting all of those passwords into

00:01:52.770 --> 00:01:54.760
something that might help with automation.

00:01:55.740 --> 00:01:58.050
A quick look at the help shows us the options.

00:01:58.940 --> 00:02:02.870
We're going to output in all formats and stick with the default,

00:02:02.900 --> 00:02:05.450
which will put the files in our current directory.

00:02:06.440 --> 00:02:09.259
Once that's complete, we'll open up the JSON file.

00:02:10.240 --> 00:02:14.070
JSON tends to be good if you're going to programmatically use the file

00:02:14.350 --> 00:02:17.050
so perhaps if you're going to use Python to read it,

00:02:17.940 --> 00:02:19.650
We can see all the deals in there.

00:02:21.740 --> 00:02:24.470
Opening up the text file, we can see essentially

00:02:24.480 --> 00:02:26.060
everything we see on the screen.

00:02:27.340 --> 00:02:30.280
If using something like Grep is more your style,

00:02:30.350 --> 00:02:32.560
then this is the direction you're likely to take.