WirelessPhreak.com

I like to travel, f*ck with technology, and partake in the occasional tropical drink.
I am also a co-host on The NBD Show podcast.
Follow Me

 The question is “why log everything?”

Logging your local SSH sessions can provide valuable information for troubleshooting, record-keeping, security, and auditing purposes. It is recommended to enable session logging as part of your SSH client configuration. Logging can save your bacon, for instance when:

  • The telnet/SSH client buffer is full
  • Something goes wrong
  • You mistakenly close SecureCRT
  • You want to check what you have done


The original guide was posted on Ciscozine.com. It was such a good article I wanted to capture it here and add some Apple screenshots for everyone.

Below the steps to configure it:

1. Open the software.

2. On the top bar click “Options”then “Global Options”.


3. Select “Default Session”, click “Edit Default Settings…”; then select “Log File”.


There are many customization's:Log file name: where to save the log file.
Upon connect: text at the beginning of the file.
Upon disconnect: text at the end of the file.
On each line: text added on each line.

These fields accept several variables; a complete list is shown below:%H – hostname
%S – session name
%Y – four-digit year
%M – two-digit month
%D – two-digit day of the month
%h – two-digit hour
%m – two-digit minute
%s – two-digit seconds
%t – three-digit milliseconds
%% – percent (%)
%envvar% – environment variable (for instance %USERNAME%)

Note: These settings will be applied ONLY on new sessions!

4. If you would apply these settings on the current saved sessions click “File” on the top bar then “Connect…”. Select the devices or the group of devices, right click and select “Properties”. A new window will appear:

 

You can customize each field as you prefer. In my case, I have used the previous settings.

Below an example of a saved session:
19:19:58.965 $ Start recording Test_Switch (192.168.0.10) - 19:19:58
19:19:58.983 $ C
19:19:58.983 $ *
19:19:58.984 $ *
19:19:58.984 $ * Test_Switch
19:19:58.984 $ *
19:19:58.985 $
19:20:00.950 $ Username: Cisco
19:20:00.980 $ Password:
19:20:00.980 $
19:20:48.403 $ Test_Switch#sh ver
19:20:48.620 $ Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 15.1(2)SY, RELEASE SOFTWARE (fc4) 19:20:48.620 $ Technical Support: http://www.cisco.com/techsupport
19:20:48.620 $ Copyright (c) 1986-2013 by Cisco Systems, Inc.
19:20:48.620 $ Compiled Wed 04-Sep-13 13:05 by prod_rel_team
19:20:48.620 $
19:20:48.621 $ ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
19:20:48.621 $ 19:20:48.621 $ SW-6500-VSS uptime is 23 weeks, 2 hours, 8 minutes
19:20:48.621 $ Uptime for this control processor is 23 weeks, 2 hours, 0 minutes
19:20:48.621 $ System returned to ROM by reload at 12:16:02 UTC Fri May 23 2014 (SP by reload)
19:20:48.622 $ System restarted at 14:20:04 CST Fri May 23 2014
19:20:48.622 $ System image file is "sup-bootdisk:s72033-adventerprisek9-mz.151-2.SY.bin"
19:20:48.622 $ Last reload reason: Admin reload CLI
19:20:48.622 $
19:20:48.622 $
19:20:48.624 $
19:20:48.624 $ This product contains cryptographic features and is subject to United
19:20:48.625 $ States and local country laws governing import, export, transfer and
19:20:48.625 $ use. Delivery of Cisco cryptographic products does not imply
19:20:48.625 $ third-party authority to import, export, distribute or use encryption.
19:20:48.625 $ Importers, exporters, distributors and users are responsible for
19:20:48.626 $ compliance with U.S. and local country laws. By using this product you
19:20:48.626 $ agree to comply with applicable laws and regulations. If you are unable
19:20:48.626 $ to comply with U.S. and local laws, return this product immediately.
19:20:48.626 $
19:20:48.626 $ A summary of U.S. laws governing Cisco cryptographic products may be found at:
19:20:48.626 $ http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
19:20:48.626 $
19:20:48.627 $ If you require further assistance please contact us by sending email to
19:20:48.627 $ [email protected].
19:20:48.627 $
19:20:48.627 $ cisco WS-C6509-E (R7000) processor (revision 1.6) with 983008K/65536K bytes of memory.
19:20:48.627 $ Processor board ID SMC17330086
19:20:48.957 $ SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache 19:20:48.958 $ Last reset from s/w reset
19:20:48.958 $ 12 Virtual Ethernet interfaces
19:20:48.958 $ 216 Gigabit Ethernet interfaces
19:20:48.958 $ 36 Ten Gigabit Ethernet interfaces
19:20:48.958 $ 1917K bytes of non-volatile configuration memory.
19:20:48.958 $ 19:20:48.959 $ 65536K bytes of Flash internal SIMM (Sector size 512K).
19:20:48.959 $ Configuration register is 0x2102
19:20:48.960 $ 19:20:59.632 $ Test_Switch#
19:22:23.284 $ Test_Switch#exit
19:22:23.585 $ Stop recording Test_Switch (192.168.0.10) - 19:22:23

As you can see, each line start with the time. The “$” is used for two reasons:If you import the log file in Excel or similar, you can use this symbol as a delimiter.
I use the “$” and not the “,” because in some configuration the “,” is present, so it would not be possible to use this symbol like a delimiter.



 

 

SC Hot Buttered Rum Batter

1 teaspoon freshly ground cinnamon
1 teaspoon freshly ground nutmeg
1 teaspoon freshly ground black pepper
3/4 teaspoon ground cloves
1/2 teaspoon ground allspice
1/2 teaspoon ground anise seed
2 cups salted butter
4 cups packed golden brown sugar
2 tablespoons Brer Rabbit Mild Molasses
1 teaspoon vanilla extract

Combine the spices in a small bowl and set aside. Melt the butter in a saucepan over low heat, add sugar and stir constantly. Add molasses and vanilla extract and stir. Finally, stir in the spice mixture. Continue to stir on lowest possible heat until all items mix thoroughly and butter does not create a separate layer, about 15 minutes. Let cool slightly and while still soft, pour batter into storage containers. Seal airtight after batter has cooled completely. It will keep until the expiration date of the butter used.

Now that you've done the hard work, make yourself a Smuggler's Cove Hot Buttered Rum by combining 3 barspoons of the above batter and 1 1/2 ounces of blended aged rum in an Irish Coffee glass, top with 6 ounces of hot water and stir. Serve with a cinnamon stick, but feel free to garnish with whipped cream and some freshly grated nutmeg if you so desire. I'm sure Martin, Rebecca, and the Trader wouldn't mind.




Ingredients

  • 1 cup light or dark brown sugar
  • 2 tablespoons water
  • 6 tablespoon butter
  • 1/2 teaspoon  salt
  • 1/2 teaspoon cider vinegar
  • 3/4 cup heavy cream divided
  • 1/2 teaspoon rum extract
  • 4 bottles (12 oz. bottles) cream soda

Instructions

  1. In a small saucepan over medium, combine the brown sugar and water. Bring to a gentle boil and cook, stirring often, until the mixture reads 240 F on a candy thermometer.
  2. Stir in the butter, salt, vinegar and 1/4 heavy cream. Set aside to cool to room temperature.
  3. Once the mixture has cooled, stir in the rum extract.
  4. In a medium bowl, combine 2 tablespoons of the brown sugar mixture and the remaining 1/2 cup of heavy cream. Use an electric mixer to beat until just thickened, but not completely whipped, about 2 to 3 minutes.
  5. To serve, divide the brown sugar mixture between 4 tall glasses (about 1/4 cup for each glass). Add 1/4 cup of cream soda to each glass, then stir to combine. Fill each glass nearly to the top with additional cream soda, then spoon the whipped topping over each.

 

 

So Open SSL announced that they are going to release details of a Critical OpenSSL vulnerability that  affects versions 3.0.0 to 3.0.6. There is rumbling that this vulnerability may be a major deal likened to the everyone's favorite CVE of 2014, heartbleed. 

 

Open SSL will be releasing their patch/update Tuesday 1st November 2022 between 1300-1700 UTC


But unlike heartbleed this OpenSSL vulnerability might not have the same impact to security and network infrastructure that heartbleed had. So far most security and network infrastructure companies are looking ok. As you would expect many of these companies don't run the most bleeding edge versions of open source libraries for this very reason. Also many times stability and security take president over new features. 

 

What I wanted to do is put links to OSS (Open Source Software) lists that are used in different vendors platforms. I started out hopeful but for many of the companies it is very difficult to find. I will post hem as i run across them.

 

Cisco - https://www.cisco.com/c/en/us/about/legal/open-source-documentation-responsive.html

Palo Alto Networks - https://docs.paloaltonetworks.com/oss-listings/pan-os-oss-listings

Juniper - 

Fortinet -

Aruba - 

Arista - 

Extreme Networks - 

Checkpoint - 

F5 - 

Citrix ADC -