< Return to Video

Sandbox

  • 0:00 - 0:04
    Hello. Today we're going to be talking
    about file organization for a small
  • 0:04 - 0:10
    penetration test company. What is a pen
    test? A pen test is an attack on a
  • 0:10 - 0:15
    computer or a network for the purposes
    of trying to find out what weaknesses
  • 0:15 - 0:21
    the device(s) happen to have so that they
    can be taken care of before the bad guys
  • 0:21 - 0:27
    try to attack. Pen tests are conducted
    with legal written permission by the of
  • 0:27 - 0:32
    the owners of the attacked devices. So
    this company has just started conducting
  • 0:32 - 0:38
    penetration tests. They've got five
    clients so far and they have started to
  • 0:38 - 0:42
    create a number of different files for
    each of the different clients they have.
  • 0:42 - 0:47
    For example, a nondisclosure agreement or
    NDA that pretty much says we won't let
  • 0:47 - 0:54
    anybody else other than the owners of
    the devices know what we found out, so
  • 0:54 - 1:00
    we're not going to tell anybody, "Hey, this
    company has these weaknesses." They have
  • 1:00 - 1:08
    the letter with written permission to be able
    to conduct the tests; this one permission
  • 1:08 - 1:12
    is sometimes called informally a
    "get-out-of-jail-free card." The pen
  • 1:12 - 1:15
    testers have been taking notes as
    they've been conducting the tests and
  • 1:15 - 1:19
    they've developed a final report and
    they have all this documentation on each
  • 1:19 - 1:26
    of the different clients. Now at this point, I
  • 1:26 - 1:31
    have all the relevant files in a
    directory that's inside my home
  • 1:31 - 1:36
    directory. I'd like to copy all of that
    information into the directory we happen
  • 1:36 - 1:45
    to be in at the moment. The command to
    copy things is "cp," and because we're
  • 1:45 - 1:52
    going to be copying a directory, we're
    going to throw in the -r. Next, we
  • 1:52 - 1:56
    have to say what it is we'd like to copy. We'd like to copy files that are in my
  • 1:56 - 2:02
    home directory . The tilde ~ represents the
    home directory, and I'm going to start
  • 2:02 - 2:07
    typing the name of the directory that
    we'd like to copy. It begins with an
  • 2:07 - 2:14
    "f" - it's "files for video". As it happens I
    only have one particular item in
  • 2:14 - 2:17
    my home directory that begins with the
    letter "f," so I'm going to hit the tab key
  • 2:17 - 2:24
    now to autocomplete this relatively long
    name. I just happened to delete the slash
  • 2:24 - 2:28
    that came at the end. When you hit "tab"
    and you have the name of a
  • 2:28 - 2:32
    directory, the name will end with a
    slash / , so you can keep typing
  • 2:32 - 2:36
    additional information. As it happens, I
    don't wish to type anything else, so I just
  • 2:36 - 2:41
    deleted this /. It really doesn't matter
    whether you have that there or not. I'd like
  • 2:41 - 2:46
    to copy that information into our
    current directory. cp always requires two
  • 2:46 - 2:51
    arguments; basically, you're saying, "copy
    what where": What do I wish to copy? The
  • 2:51 - 2:57
    directory "files for video". Where do I
    want to copy it? Here. A single dot . , as
  • 2:57 - 3:04
    you'll recall, represents "Here. The
    current directory." and if I do an ls
  • 3:04 - 3:13
    right now, I can see that I do, in fact,
    have a "files for video" directory. I'm now
  • 3:13 - 3:18
    going to switch into my "files for video,"
    directory, so I type "cd f" and I
  • 3:18 - 3:23
    hit the tab. Now you'll notice that
    everything that begins with "f" in this
  • 3:23 - 3:29
    directory goes on to have an "il" as the next two characters, so Linux was able to
  • 3:29 - 3:33
    autocomplete the "il," but it
    doesn't know at this point: Do I want to
  • 3:33 - 3:38
    keep typing "es" for "files"? Do I want to type the "lters" for "filters"? It doesn't know, so I'm going
  • 3:38 - 3:52
    to give it an "e" and hit tab. It fills in
    the "s" for us. If I hit an "f" it'll in the rest of the "for." Hit "v," hit tab again and it fills in the rest of
  • 3:52 - 3:58
    "video," so you can see that you can hit
    tab multiple times. So now my "files for
  • 3:58 - 4:06
    video" is my active directory and I'm
    going to take a look inside it and I see
  • 4:06 - 4:12
    that I've got a fair number of files
    here. Now if we are only ever going to be
  • 4:12 - 4:16
    having five clients then everything
    could stay in one directory,
  • 4:16 - 4:22
    but we're starting to realize that -- wait
    a minute -- we're going to have a whole lot
  • 4:22 - 4:25
    more clients coming up, and this
    directory that we have is just going to be
  • 4:25 - 4:29
    getting larger and larger and larger,
    and it's going to become less and less
  • 4:29 - 4:35
    easy to be able to find the files that
    we would like, so we better come up with
  • 4:35 - 4:39
    some sort of an organization so that
    we'll be able to find the files that we
  • 4:39 - 4:43
    wish quickly and easily. There are a
    couple of different approaches we could
  • 4:43 - 4:48
    take with these particular files. One
    approach -- and the one we're going to be
  • 4:48 - 4:56
    using -- looks like this. I've ignored all
    the directory structure that's not
  • 4:56 - 5:03
    relevant to us at the moment. We are in
    the CIS one forty-one directory. We're
  • 5:03 - 5:06
    going to create a directory for all of
    our pen test information. I'm just
  • 5:06 - 5:11
    calling it "PT" for "pen test," and then we're
    going to have a separate directory for
  • 5:11 - 5:16
    each of our different clients. Within
    each of the client directories, we'll
  • 5:16 - 5:18
    have the relevant information -- our
    get-out-of-jail-free card, our
  • 5:18 - 5:27
    non-disclosure agreement, the running
    notes, and the final pen test report. We
  • 5:27 - 5:31
    could have organized things in a different
    way; instead of organizing by client, we
  • 5:31 - 5:34
    could have organized by type of
    information. So we could have put all of
  • 5:34 - 5:39
    our get-out-of-jail free cards in one
    directory all of our NDAs in another
  • 5:39 - 5:45
    directory, and so forth. On both this and
    the past slide, some details are omitted
  • 5:45 - 5:52
    just so that the slides wouldn't get too
    cluttered. So the client information for
  • 5:52 - 6:00
    the notes and the reports
    directories were omitted here. Up here,
  • 6:00 - 6:04
    the information for the specific files
    underneath client3 and for client5
  • 6:04 - 6:11
    have been omitted, but you can
    extrapolate what they would be. So okay,
  • 6:11 - 6:16
    we're going to have to create some
    directories. We'll start off by creating
  • 6:16 - 6:23
    the PT directory for our pen tests. The
    command to create a directory is mkdir.
  • 6:23 - 6:28
    It's pronounced "make dir," but it's
    spelled mkdir. OK, so we've created our
  • 6:28 - 6:32
    pen test directory. You can see I've just
    executed another ls, and we can see our
  • 6:32 - 6:37
    pen test directory PT. Inside this
    directory, we're going to be creating a
  • 6:37 - 6:41
    directory called "client1,"
  • 6:41 - 6:51
    so
    mkdirPT /client1
    Now when we go to move our files, we can
  • 6:51 - 6:55
    shorten their names as well. We no longer
    have to have "PT" and "client1" as part
  • 6:55 - 6:59
    of the name of each of these files
    because we can get the information that
  • 6:59 - 7:03
    it's about a pen test and it's for
    client one just from our directory
  • 7:03 - 7:10
    structure. So the syntax of the command
    to move files is very similar to the
  • 7:10 - 7:15
    syntax of the command for copying. The
    command for moving is "mv" and it's
  • 7:15 - 7:28
    "move what where": What are we going to be moving? We're going to be moving our PT client one's get-out-of-jail-free card. Where are we going to be moving it? We're
  • 7:28 - 7:32
    going to be moving it into the PT
    directory -- inside there into the client1
  • 7:32 - 7:44
    sub directory -- and from there we're
    going to call the file simply GooJFC for
  • 7:44 - 7:51
    "get-out-of-jail-free card." We can execute an ls command, and we can see that we no
  • 7:51 - 7:56
    longer have the get out of jail free
    card for client one in our current
  • 7:56 - 8:05
    directory. If we do an ls for our PT/client1 directory, you can see that in
  • 8:05 - 8:14
    fact we do have the file with the
    shortened name inside the directory. Now
  • 8:14 - 8:18
    we're going to do the same thing for
    each of our other three client1 files.
  • 8:18 - 8:29
    I'm going to use the up arrow to
    retrieve my most recent mv command and
  • 8:29 - 8:35
    I'm using the left arrow and the
    backspace to move to where I need to be
  • 8:35 - 8:42
    and to delete the letters I don't want in
    here. This is just a quicker way of
  • 8:42 - 8:49
    coming up with the command rather than having to type it all again by hand. Up arrow
  • 8:51 - 9:06
    notes and report. I'm going to clear the
    screen screen quickly with the ctrl^L
  • 9:06 - 9:12
    keyboard shortcut, and ls shows us that we no longer have client1
  • 9:12 - 9:20
    files in the current directory, but if we
    do a ls of PT/client1, we can see that
  • 9:20 - 9:26
    we have all of the files that we had
    before in our client1 directory. Now
  • 9:26 - 9:33
    okay, we're going to go ahead and create
    a client2 directory mkdir PT/client2
  • 9:33 - 9:43
    and we could copy all of the files here individually into that
  • 9:43 - 9:55
    directory; so we could, for example, say
    mv PTclient2GooJFC Pt/client2/GooJFC
  • 9:55 - 10:39
  • 10:40 - 10:49
    and we could
  • 10:49 - 10:55
    do that similar sort of thing for all of
    the remaining files. There is, however, a
  • 10:55 - 11:01
    faster way to accomplish our task. We
    could we'd once again start out saying
  • 11:01 - 11:08
    mv PTclient2 but now instead
    of listing an end of each individual
  • 11:08 - 11:14
    file we can use an asterisk; the
    asterisk says, "substitute here any zero
  • 11:14 - 11:21
    or more characters," so just in this one
    phrase
    PTclient2*
  • 11:21 - 11:27
    it's as if here we typed all of the files whose names begin with
  • 11:27 - 11:36
    PTclient2
    Where do we want to put them? we want to put them in PT/client2
  • 11:36 - 11:44
    to let's verify that we did what we
    wanted to do. ls. We don't see anything
  • 11:44 - 11:48
    about client2 in our current directory.
    ls PT/client2
    We have all four of out
  • 11:52 - 11:59
    client2-related files within our
    client2 directory. Now, the downside of
  • 11:59 - 12:07
    this is that we would need to rename the
    NDA, the notes, and the report file if we
  • 12:07 - 12:12
    so desired to shorten up the names. In
    the interests of not boring you I'm not
  • 12:12 - 12:17
    going to go through and shorten all
    those right now. In real life we might
  • 12:17 - 12:23
    or might not choose to do so. At this
    point, I'm going to very quickly create
  • 12:23 - 12:30
    client three, four, and five directories
    and put the relevant files into them. So
  • 12:30 - 12:37
    mkdir PT/client3 PT/client4 PT/client5
  • 12:37 - 12:45
    You can use the "mkdir" command with
  • 12:45 - 12:53
    multiple different arguments, so that's
    just created the client3, client4, and
  • 12:53 - 13:04
    client5 directories within our PT
    directory. I'm now going to move all the
  • 13:04 - 13:18
    relevant files for client3 into the
    client3 directory, client 4 into the client4 directory, and client 5 into the client5 directory.
    directory if I do a quick LS I can see I
  • 13:18 - 13:26
    I don't have any ordinary files inside my
    current directory; I could do an
  • 13:26 - 13:35
    ls PT/client3 PT/client4 PT/client5
    if I so desired, but ls actually has a nice
  • 13:35 - 13:46
    option of -R
    The capital R says< "show me a recursive listing." What this
  • 13:46 - 13:51
    means is this is saying not only show me
    what's immediately inside the PT
  • 13:51 - 13:56
    directory, but if there are any
    directories in the PT directory, show me
  • 13:56 - 14:01
    their contents and if there are any
    directories within their contents, show
  • 14:01 - 14:07
    its contents all the way down the
    directory structure. So now we can see
  • 14:07 - 14:12
    all at once that the PT directory
    contains the client1 through client5
  • 14:12 - 14:19
    directories and we can see the contents
    of each of the individual client
  • 14:19 - 14:27
    directories. I'll say as an aside that
    there are ways that you would be able to
  • 14:27 - 14:32
    shorten the names to remove the PT
    client in a fashion that's more
  • 14:32 - 14:37
    efficient than just doing it by hand. How you would do that, though, is
  • 14:37 - 14:41
    beyond the scope of this discussion. OK, I
    just cleared the screen again and I'm
  • 14:41 - 14:48
    going to cd into the PT directory and
    make a new directory for a hypothetical
  • 14:48 - 14:55
    client six. and I'm going to
    cd into the client6 directory. One
  • 14:55 - 15:00
    command that is very useful if you would
    just like to create an empty file -- in
  • 15:00 - 15:03
    fact it's the command that I use to
    create all the files we've worked with
  • 15:03 - 15:11
    today -- that's the "touch" command. So I
    could say
    touch NDA
  • 15:11 - 15:21
    and I've created an empty 0 bytes file called NDA.
  • 15:23 - 15:28
    I'm going to be switching topics a little
    bit so that I can talk about a couple of
  • 15:28 - 15:33
    other things that I did wish to talk
    about in this video. So this is not
  • 15:33 - 15:38
    directly pentest related, but suppose for
    some reason you wish to have the
  • 15:38 - 15:45
    calendar -- the output of the cal command
    -- display not on your screen, but put it
  • 15:45 - 15:53
    into a file. You can redirect the output
    of the "cal" command. This is saying, "Don't
  • 15:53 - 15:57
    show me the calendar -- the output of the
    cal command -- on the screen. Instead, put
  • 15:57 - 16:01
    it into a file that we're going to call
    'calendar'." We now have a calendar file, and
  • 16:01 - 16:06
    if we use the "cat" command to display the
    contents of the calendar file, we can see
  • 16:06 - 16:12
    that it is in fact the calendar for the
    month in which I'm recording this video.
  • 16:12 - 16:17
    Maybe we'll have another file that's
    going to show the output of the "date"
  • 16:17 - 16:24
    command and we'll just call that file
    "day," and a cat of day reveals that it
  • 16:24 - 16:29
    does in fact give us the output of the
    date command. Why am I creating these
  • 16:29 - 16:38
    files? It's because I'd like to show you
    something about the mv command that
  • 16:38 - 16:44
    also applies to the cp command and is
    very important. We've seen a couple of
  • 16:44 - 16:50
    ways in which the mv or the cp commands
    can be used. With "copy what where," if "where"
  • 16:50 - 16:56
    is the name of a file that does not
    exist, cp or mv will create a file by
  • 16:56 - 17:07
    that name with the contents of the
    original file. So if i say cp x y then both of them will have
  • 17:07 - 17:16
    identical content. If the "where" is the
    name of a directory, what we saw
  • 17:16 - 17:19
    mv command holds true with the cp
  • 17:19 - 17:24
    command, that the "copy what where," if the "where" is s directory it will take the
  • 17:24 - 17:29
    "what" file specified and it will create a file within
  • 17:29 - 17:36
    the specified directory with the
    contents of that file, so if I said
    cp x y
  • 17:36 - 17:41
    with "y" being the name of a directory,
    what will result is there's going to be
  • 17:41 - 17:50
    a file called y/ x with the x in the x
    directory containing the same content as
  • 17:50 - 17:55
    the original file named x. There's a
    third possibility, though. The first
  • 17:55 - 18:01
    possibility was the "what" was the name of
    a file that did not yet exist. The second
  • 18:01 - 18:08
    possibility was the name of a directory. The third possibility
  • 18:08 - 18:17
    is the name of a file that does exist. Suppose we decided to
  • 18:17 - 18:23
    take information from "cal" and "date" and
    put it into a single file. I'm just going
  • 18:23 - 18:32
    to call "when". So we can move the contents of our "day" file into a file called "when".
  • 18:32 - 18:43
    We no longer have a file called "day." The
    file called "when" now has the output of
  • 18:43 - 18:50
    the date command.Now watch very carefully: this is what I wanted to show you.
  • 18:50 - 18:57
    If I type
    mv calendar when
    -- "when" is a file that already exists; it
  • 18:57 - 19:02
    contains the output of the date command --
    this is what's currently in the "when" file.
  • 19:02 - 19:11
    I did not get any error messages. mv was
    perfectly happy to move the contents of
  • 19:11 - 19:19
    calendar into the "when" file. An ls command shows again we no longer have
  • 19:19 - 19:28
    a "calendar" file, but look at the contents
    of the "when" file. You see what happened
  • 19:28 - 19:32
    in the calendar file, but the information
    from the output of the "date" file -- what had
  • 19:32 - 19:38
    been in the "when" file before we copied
    the calendar contents into "when" -- that is
  • 19:38 - 19:46
    gone, and this is the important caveat: If
    you're using mv or you're using cp
  • 19:46 - 19:52
    and the second argument is the name of a
    file that exists, that file's original
  • 19:52 - 20:00
    contents will be replaced with the
    contents of whatever was in the first
  • 20:00 - 20:10
    argument, so be very careful with cp and
    mv. OK, so we've created quite a number of
  • 20:10 - 20:14
    different files here and I'd like to
    clean up all the files that we worked
  • 20:14 - 20:17
    with today. They're just ones that were
    created for this video; there's really no
  • 20:17 - 20:23
    pen test company. I'm going to clean up
    the files, so the first thing I'd like to
  • 20:23 - 20:26
    do would be to delete the directory that
    I'm in right now and all of its contents.
  • 20:26 - 20:34
    To delete a directory use the "rmdir"
    command. I'm going to
  • 20:34 - 20:41
    try to delete the directory I'm in right
    now and this period is usually used to
  • 20:41 - 20:48
    mean "here". We saw it in an action earlier
    when we said cp -r cis141 .
  • 20:48 - 20:56
    We're saying copy that
  • 20:56 - 21:04
    one directory here. Dot (.) is a perfectly
    valid argument for many commands, but
  • 21:04 - 21:09
    it's not valid for the "rmdir" command, and
    there's a reason for it which you could
  • 21:09 - 21:14
    probably figure out on your own if you
    stopped to think for a moment. If we deleted
  • 21:14 - 21:19
    the directory we were in, where would we
    be? We just got rid of the directory we
  • 21:19 - 21:25
    were currently in and we have to be in
    some directory so rmdir basically
  • 21:25 - 21:28
    says you can't delete the directory
    you're in, so I'm going to go up one
  • 21:28 - 21:34
    level and I'm going to try deleting my client6
  • 21:34 - 21:41
    directory and rmdir still is not
    going to be very happy. It's saying the
  • 21:41 - 21:48
    directory is not empty; you've got files
    in it, so we can delete all those files.
  • 21:48 - 21:59
    we could type in rm -- the command to
    delete a file -- client6/NDA and we
  • 21:59 - 22:09
    could type in rm client6/when, and
    now we can try again rmdir client6
  • 22:09 - 22:15
    Because we deleted everything inside
    client6, client6 was an empty directory.
  • 22:15 - 22:28
    Because client6 is now an empty directory,
  • 22:28 - 22:35
    rmdir we'll go ahead and delete it without any complaints.
  • 22:35 - 22:41
    An ls shows us we no longer have a client6
    directory. Suppose we wish to delete
  • 22:41 - 22:45
    client5's directory and the first
    thing we wanted to do was to delete
  • 22:45 - 22:50
    everything that's inside the client5
    directory. Stop and think a minute to see
  • 22:50 - 22:54
    if you can figure out how you could
    delete everything in there all in one
  • 22:54 - 23:02
    line. Just a reminder: the contents of the
    client5 directory. Well, one thing we
  • 23:02 - 23:15
    could do would be to type in
    rm client5/ this-filename client5/this-filename client5/this-filename
  • 23:15 - 23:24
    That would be a lot of typing. Another
    thing we could do will be to type in
  • 23:24 - 23:34
    rm client5/*
    That removes everything that's inside client5. Now in
  • 23:34 - 23:38
    this particular case, that's exactly what
    we wanted to have happen, but be very
  • 23:38 - 23:43
    careful with that asterisk, especially
    when you're using it in
  • 23:43 - 23:49
    with a command such as "rm." If we had
    had a file in the client5 directory
  • 23:49 - 23:57
    that we did, in fact, wish to preserve, it's
    too late. It's gone, and there is no trash
  • 23:57 - 24:03
    bin or recycle bin or anything along
    those lines from which to be able to
  • 24:03 - 24:11
    retrieve the data. It's not there
    anymore. One thing that we could do -- I'm
  • 24:11 - 24:19
    going to go ahead and rmdir client5. With a client4 we could say rm -i client4/*
  • 24:19 - 24:27
    What client that -s is saying is
  • 24:27 - 24:32
    "Be interactive about your
    deletions -- ask me, for each individual
  • 24:32 - 24:38
    file, "'Do you really wish to remove this?'"
    I do wish to remove all of them, but
  • 24:38 - 24:42
    you can see that this provides a little
    bit of a safety net to make sure that
  • 24:42 - 24:47
    we're really not deleting anything we
    don't wish to
  • 24:47 - 24:54
    have deleted. So now I'm going to go
    ahead and delete client4, and if we
  • 24:54 - 24:58
    wanted, we could do the same things with
    clients3, client2 and client1, but there's an easier way of doing
  • 24:58 - 25:11
    things if you know for a fact that you wish to remove not only the directory,
    but everything underneath the directory.
  • 25:11 - 25:16
    Any ordinary files or directory files
    inside it any directory files that are
  • 25:16 - 25:20
    in directory files, that are inside it
    all the way down -- you know for a fact you
  • 25:20 - 25:26
    wish to get rid of everything. Instead of
    removing them the rmdir command,
  • 25:26 - 25:36
    you can use rm -r. rm -r, as you can see, works even
  • 25:36 - 25:43
    if the directory contains data, and it's
    nice to be able to have both methods of
  • 25:43 - 25:48
    being able to delete directories. If you
    know for 100% certain
  • 25:48 - 25:52
    that you do wish to
    delete not only directory but everything
  • 25:52 - 25:57
    underneath it, you can do so with rm -r, but that is very powerful.
  • 25:57 - 26:00
    If you have any hesitation whatsoever, if
    you want to make sure that you're just
  • 26:00 - 26:07
    removing empty directories, rmdir is the
    command for you. I'm going to go up a
    directory and say rm -r PT
  • 26:12 - 26:22
    you'll note that at this point the PT directory contains two
    subdirectories which in turn contain a
  • 26:22 - 26:30
    bunch of different files. all of which
    are now gone. So what we have seen so far
  • 26:30 - 26:37
    today is how you can copy and
    move the files. You can create an empty file
  • 26:37 - 26:43
    with the touch command. We've seen that rmdir will
  • 26:43 - 26:50
    remove an empty directory. rm -r will
    remove a directory that may or may not
  • 26:50 - 26:55
    be empty. If you wish to have an
    interactive way of working with rm, you
  • 26:55 - 27:01
    could use -i. We've seen that an asterisk
    can substitute for
  • 27:01 - 27:10
    any zero or more characters, and again
    the asterisk is extremely powerful but
  • 27:10 - 27:14
    you have to be careful with it. The
    asterisk is an example of what is sometimes called
  • 27:14 - 27:19
    a "globbing character." Another globbing
    character is a question mark, and that
  • 27:19 - 27:24
    says, "Substitute exactly one character."
    Instead of "Substituting here zero
  • 27:24 - 27:30
    or more," substitute exactly one. So
    we've also talked a little bit as an
  • 27:30 - 27:35
    aside about what pen testing is and some
    of the documentation -- not all but some of
  • 27:35 - 27:39
    the documentation -- that is involved in
    pen testing. That was just an added bonus.
  • 27:39 - 27:45
    If you have any questions, please do feel
    free to ask your teacher and do be
  • 27:45 - 27:49
    prepared -- if you are one of the Delaware
    Technical Community College CIS 141
  • 27:49 - 27:55
    students for whom this video
    was created -- do be prepared to come
  • 27:55 - 28:03
    into the classroom and to be able
    to conduct various organizations of
  • 28:03 - 28:09
    groups of files. So we've seen one
    example here. Are there any other
  • 28:09 - 28:15
    principles for organizing files? There actually are
  • 28:15 - 28:21
    a variety of different tips I'd like to
    talk about, some of which we've already
  • 28:21 - 28:26
    made mention of; others of which we have
    not. One is when you're organizing files,
  • 28:26 - 28:32
    it's a good idea to keep data files
    separate from application files. One
  • 28:32 - 28:36
    reason for this is that data files are
    going to be backed up much more
  • 28:36 - 28:40
    frequently than application files, and by
    keeping them separate, it makes it easier
  • 28:40 - 28:43
    to execute a backup strategy.
  • 28:43 - 28:53
    You also want to have consistency in naming conventions for files and for folders or directories. We don't want to have client1
  • 28:53 - 28:58
    for one directory and PTclient2 for
    another and thirdclient for a third. If
  • 28:58 - 28:59
    we're using client followed by number, we
    want to keep that throughout.
  • 28:59 - 29:07
    You want your names to be short but descriptive. You don't want to have great big lengthy
  • 29:07 - 29:12
    things that, as you saw in our example, can
    be kind of hard to read and take a while to
  • 29:12 - 29:18
    type, so make them fairly short. Use
    common abbreviations (I used PT for
  • 29:18 - 29:25
    "pen test") and if a folder/directory -- I
    put in "folder" here because these tips
  • 29:25 - 29:30
    are not Linux specific, they apply
    equally to Windows or to any other
  • 29:30 - 29:35
    operating system -- but if you do see your
    container object (whatever it's called)
  • 29:35 - 29:40
    start to have too much information and
    it starts to become unwieldy, create
  • 29:40 - 29:46
    subfolders and sub-directories. A few
    possible ways you can organize things
  • 29:46 - 29:51
    are completed versus incomplete, so if
    you've got different files for different
  • 29:51 - 29:55
    projects, when you've finished a
    particular file -- you've done the work
  • 29:55 - 29:58
    that is involved with that file -- you can
    move it from the "incomplete" to the
  • 29:58 - 30:04
    "completed" directory. You might organize
    things by file type, so you'll have all of
  • 30:04 - 30:07
    your workbooks together, all your
    documents in a separate directory, all of
  • 30:07 - 30:13
    your slideshows in a third. You might
    wish to organize things by project -- that
  • 30:13 - 30:17
    is, in essence, what we did here -- where we
    had client1, client2, client3, and
  • 30:17 - 30:24
    each client involved a separate pen test.
    If you're dealing with Windows,
  • 30:24 - 30:28
    put your documents in the document folder, create subfolders within the "Document" folder.
  • 30:28 - 30:34
    You can use jump lists. I'm going
    to be panning down on my screen so that
  • 30:34 - 30:41
    you can see my taskbar so I can
    demonstrate a jump list. If I right-click
  • 30:41 - 30:50
    on one of the icons in the taskbar, what
    shows up is a jump list. These are my
  • 30:50 - 30:55
    pinned items, these are ones that are
    going to be staying on my list even if I
  • 30:55 - 31:04
    haven't happened to use them in a while.
    these are files that I've recently used. As I
  • 31:04 - 31:09
    added new files, open up new files, the
    older ones will drop from the list. If
  • 31:09 - 31:14
    I'd like to make sure that something
    stays on this list, I can pin it by
  • 31:14 - 31:20
    clicking on the pushpin. I can unpin
    a pinned item by clicking on the push pin
  • 31:20 - 31:28
    again. You might wish use the recent
    items on the start menu, but if for security
  • 31:28 - 31:31
    reasons you don't wish to have a "recent
    items" on the start menu or you don't
  • 31:31 - 31:36
    wish to have a jump list, there
    are ways of getting rid of those as well.
  • 31:36 - 31:42
    If you have certain files that you open
    very, very, very frequently, you might wish
  • 31:42 - 31:47
    to create a desktop shortcut in
    Windows to the particular item. That way,
  • 31:47 - 31:53
    you can go to it directly without having
    to navigate the folder structure. If you
  • 31:53 - 31:59
    are trying to find particular files, you
    can go into "computer" and for our
  • 31:59 - 32:02
    discussion right now. I'd actually like
    to talk a little bit about how things
  • 32:02 - 32:10
    are set up at Del Tech. We have a u: drive
    that teachers can add information to or
  • 32:10 - 32:14
    make changes to. Students can look at and can copy files from it, but they're not
  • 32:14 - 32:19
    allowed to make changes. I think the
    u: drive is an excellent example of
  • 32:19 - 32:24
    organization. Even if you've never looked
    at the u: drive before, if you know that
  • 32:24 - 32:28
    this video is for our CIS 141
    class, you'd be able to just glance at
  • 32:28 - 32:32
    the names of these folders. They're very
    short but they're descriptive. You should
  • 32:32 - 32:36
    be able to figure out that this is the folder
    that you would be interested in. If you
  • 32:36 - 32:40
    happen to know
    that my last name is "Mancini," you'd be
  • 32:40 - 32:46
    able to look at these and you'd be able
    to zero in on exactly which folder would
  • 32:46 - 32:53
    have information that is relevant, and
    then from here again you can go into the
  • 32:53 - 32:59
    relevant folder. At this point, I'd like
    to look at the folder that just says
  • 32:59 - 33:03
    "Windows." This contains a number
    of miscellaneous files for the purposes
  • 33:03 - 33:10
    of practicing organization. Again,
    this is a relatively small number of
  • 33:10 - 33:14
    files in this folder, but pretend that
    there were quite a number and we wish to
  • 33:14 - 33:20
    find a particular one. I happen to be in
    the "Details" view right now. You can
  • 33:20 - 33:25
    change your view by going to the View
    menu. You're going to "Details." If you
  • 33:25 - 33:30
    don't happen to see your view menu, you
    could go to the drop-down list for
  • 33:30 - 33:37
    "Organize," and choose "Layout," and you'll be able to see your menu bar, then you can
  • 33:37 - 33:42
    bring up the View menu. We're
    currently in the details view now. The
  • 33:42 - 33:47
    nice thing about the details view -- or one
    of the nice things beyond the fact that
  • 33:47 - 33:50
    it gives you a lot more information
    about all the different files -- is that
  • 33:50 - 33:54
    you can organize things quickly. If you
    knew that the file you were interested
  • 33:54 - 33:59
    in was one that had been modified fairly
    recently, you can click on "Date Modified,"
  • 33:59 - 34:05
    and if you click on it once, it organizes
    things from the most recently to the
  • 34:05 - 34:09
    least recently modified files. These
    files haven't been modified in quite a
  • 34:09 - 34:15
    while. If you click on it again, it
    reverses the organization. If you knew
  • 34:15 - 34:18
    that you wished to get rid of some files --
    maybe you're running out of space -- and
  • 34:18 - 34:22
    you wanted to see if are there a couple of
    really large files that you wish to get
  • 34:22 - 34:29
    rid of, you could sort by size. The
    default order is sorting by name, and if
  • 34:29 - 34:34
    you happen to have a mixture of both
    files and folders, the folders by default
  • 34:34 - 34:40
    will show up first a through , then the
    ordinary files a through z. So, again, I
  • 34:40 - 34:44
    hope you found these tips useful. Keep
    them in mind. Again, if you happen to be a
  • 34:44 - 34:49
    CIS 141 student at Delaware
    Technical Community College, be sure to
  • 34:49 - 35:01
    practice the commands that we discussed
    earlier in this video: cp, mv, touch, the ls with the -R option, rmdir, rm -r, the
  • 35:01 - 35:09
    -i option, rm without any options. Practice the globbing
  • 35:09 - 35:17
    character, the asterisk. Be prepared to
    come into class and be able to do
  • 35:17 - 35:22
    something similar to what was done in
    this particular presentation.You will be
  • 35:22 - 35:28
    given a directory that has a lot of
    files, and that you are going to have to try
  • 35:28 - 35:33
    to come up with an appropriate
    organization for. Again, I hope you found
  • 35:33 - 35:38
    this video interesting and useful and
    informative. If you have any questions,
  • 35:38 - 35:41
    please do speak with your instructor
Title:
Sandbox
Description:

You can use this Sandbox to try out things with the Amara tool.

The video that is primarily streaming here is http://www.youtube.com/watch?v=ZU2kyr9jRkg , which is completely blank. But you can go to the URLs tab to add the URL of another video and make it primary.

Please remember to download your subtitles if you want to keep them, as they will get deleted - and the streaming URL reverted to the blank video if you changed it - after a week or two,

more » « less
Video Language:
English
Team:
Captions Requested
Duration:
01:46:39
Claude Almansi edited English subtitles for Sandbox
Claude Almansi edited English subtitles for Sandbox
Claude Almansi edited English subtitles for Sandbox
Claude Almansi edited English subtitles for Sandbox
Claude Almansi edited English subtitles for Sandbox
koma edited English subtitles for Sandbox
koma edited English subtitles for Sandbox
Claude Almansi edited English subtitles for Sandbox
Show all
  • Revision 1 = provided subtitles for Lecture 1.2 of Prof. Scott Plous' Social Psychology course

  • Revision 1 = provided subtitles for Lecture 1.2 of Prof. Scott Plous' Social Psychology course

  • Revision 1 = provided subtitles for Lecture 1.2 of Prof. Scott Plous' Social Psychology course

English subtitles

Incomplete

Revisions Compare revisions