Committing Changes to CVS

In my last post I set up CVS so I could upload my Sguil scripts. I decided I would document how I make changes to those scripts and commit them to CVS.

First I needed to check out a copy of the scripts. I made a dev directory and will now use that for all future development.

richard@macmini:~$ export CVS_RSH=ssh
richard@macmini:~$ mkdir dev
richard@macmini:~$ cd dev
richard@macmini:~/dev$ cvs -z3 \
> -d:ext:taosecurity@taosecurity.cvs.sf.net:/cvsroot/taosecurity checkout -P \
> taosecurity_sguil_scripts
taosecurity@taosecurity.cvs.sf.net's password: 
cvs checkout: Updating taosecurity_sguil_scripts
U taosecurity_sguil_scripts/README
U taosecurity_sguil_scripts/sancp
U taosecurity_sguil_scripts/sguil_client_install.sh
U taosecurity_sguil_scripts/sguil_database_install_pt1.sh
U taosecurity_sguil_scripts/sguil_database_install_pt2.sh
U taosecurity_sguil_scripts/sguil_sensor_install.sh
U taosecurity_sguil_scripts/sguil_sensor_install_patch.sh
U taosecurity_sguil_scripts/sguil_server_install.sh
U taosecurity_sguil_scripts/sguild_adduser.sh
U taosecurity_sguil_scripts/snort
U taosecurity_sguil_scripts/snort_src_install.sh
richard@macmini:~/dev$ cd taosecurity_sguil_scripts/
richard@macmini:~/dev/taosecurity_sguil_scripts$ ls
CVS                      sguild_adduser.sh              sguil_sensor_install.sh
README                   sguil_database_install_pt1.sh  sguil_server_install.sh
sancp                    sguil_database_install_pt2.sh  snort
sguil_client_install.sh  sguil_sensor_install_patch.sh  snort_src_install.sh

With the scripts checked out I edit the 'snort' script and commit it.

richard@macmini:~/dev/taosecurity_sguil_scripts$ cvs commit -m \
> "Update for Snort 2.6.1.2." snort
taosecurity@taosecurity.cvs.sf.net's password: 
Checking in snort;
/cvsroot/taosecurity/taosecurity_sguil_scripts/snort,v  <--  snort
new revision: 1.2; previous revision: 1.1
done

When done I realize I need to change two other scripts, so I change them and commit them at the same time.

richard@macmini:~/dev/taosecurity_sguil_scripts$ cvs commit -m \
> "Update for Snort 2.6.1.3." snort_src_install.sh README 
taosecurity@taosecurity.cvs.sf.net's password: 
Checking in snort_src_install.sh;
/cvsroot/taosecurity/taosecurity_sguil_scripts/snort_src_install.sh,v  <--  snort_src_install.sh
new revision: 1.2; previous revision: 1.1
done
Checking in README;
/cvsroot/taosecurity/taosecurity_sguil_scripts/README,v  <--  README
new revision: 1.2; previous revision: 1.1
done
richard@macmini:~/dev/taosecurity_sguil_scripts$

That's it. The changes are visible immediately via Web-based CVS.

Comments

Anonymous said…
Hi,
great job!!
FreeBSD_6_2 SECURITY on vmware - it works :)

sguil_database_install_pt1.sh - after script finishd it is necessary hit "ENTER"

sorry, I know my english is terrible
4:02 PM
Post a Comment

Popular posts from this blog

Zeek in Action Videos

Image
This is a quick note to point blog readers to my Zeek in Action YouTube video series for the Zeek network security monitoring project .  Each video addresses a topic that I think might be of interest to people trying to understand their network using Zeek and adjacent tools and approaches, like Suricata, Wireshark, and so on.  I am especially pleased with Video 6 on monitoring wireless networks . It took me several weeks to research material for this video. I had to buy new hardware and experiment with a Linux distro that I had not used before -- Parrot .  Please like and subscribe, and let me know if there is a topic you think might make a good video.
Read more

MITRE ATT&CK Tactics Are Not Tactics

Image
Just what are "tactics"? Introduction MITRE ATT&CK  is a great resource, but something about it has bothered me since I first heard about it several years ago. It's a minor point, but I wanted to document it in case it confuses anyone else. The MITRE ATT&CK Design and Philosophy document from March 2020 says the following: At a high-level, ATT&CK is a behavioral model that consists of the following core components: • Tactics, denoting short-term, tactical adversary goals during an attack; • Techniques, describing the means by which adversaries achieve tactical goals; • Sub-techniques, describing more specific means by which adversaries achieve tactical goals at a lower level than techniques; and • Documented adversary usage of techniques, their procedures, and other metadata. My concern is with MITRE's definition of "tactics" as "short-term, tactical adversary goals during an attack," which is oddly recursive. The key word in the tacti...
Read more

New Book! The Best of TaoSecurity Blog, Volume 4

Image
  I've completed the TaoSecurity Blog book series . The new book is  The Best of TaoSecurity Blog, Volume 4: Beyond the Blog with Articles, Testimony, and Scholarship .  It's available now for Kindle , and I'm working on the print edition.  I'm running a 50% off promo on Volumes 1-3 on Kindle through midnight 20 April. Take advantage before the prices go back up. I described the new title thus: Go beyond TaoSecurity Blog with this new volume from author Richard Bejtlich. In the first three volumes of the series, Mr. Bejtlich selected and republished the very best entries from 18 years of writing and over 18 million blog views, along with commentaries and additional material.  In this title, Mr. Bejtlich collects material that has not been published elsewhere, including articles that are no longer available or are stored in assorted digital or physical archives. Volume 4 offers early white papers that Mr. Bejtlich wrote as a network defender, either for technica...
Read more