Tejas Jain

AWS Workspaces Windows 10 has C:\ drive hidden by default.. To unhide it, locate the following directory in Windows Registry (regedit), HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\ Explorer Dword Value - NoDrives. By default it is set to Hexidecimal value of 4.. Change it to Hexidecimal value of 0 Restart the Workspace and C:\ drive should be visible.

Yes.. CDP still very much exists (though LLDP is doing a fairly decent job).. and most probably, would continue to, so long as Cisco is in the big game! And if you are an old Cisco techie, like me, you would be disappointed to know that it is not as simple as "cdp run" or "cdp enable" etc. Since you would be enabling CDP on the leaf interfaces which connect to the devices that are not the part of the fabric, you would find this configuration under Fabric >> Access Policies. Here are the steps for the configuration: Fabric >> Access Policies >> Interface policies Policies >> CDP Interface >> Right click on CDP interface and select "Create CDP Interface Policy" Name it and select the Admin state. 4. Next create Leaf Policy Group from Interface Policies and reference the above CDP policy in it as shown below: 5. Time to stitch the Leaf policy group with the actual Leaf Interface. 6. Go to Interface Policies >> Interface Ove...

Time and tide wait for none.. definitely not for your Application Centric Infrastructure (ACI)!! NTP configuration should always be at the top of your list of configuration items, after you un-box your appliance. I won't delve into the reasons for doing this (imagine carrying your cell phone with wrong time). Disclaimer: The NTP configuration for ACI(just like other configuration in ACI), is not a simple affair, as you would see it below: Login to APIC (obviously) Under Fabric >> Select Fabric Policies >> Quickstart >> Configure an NTP policy. Name the policy and click Next Under NTP Servers, click on the "+" icon and select the NTP server.. can be FQDN or an IP address.. Here I am using pool.ntp.org Use "Management EPG" only if the NTP server is outside the fabric. Click OK and then finish. The NTP policy should now be visible under "Pod Policies". It's not over yet.. There is more work to be done! The ACI policy configuration re...

The Smart Tracker lovers who prefer to have a separate window for checking logs.. you are in for a disappointment!! There is no separate Smart Tracker utility in Smart Console as Checkpoint R80.x boasts of a Unified Work pane and configuration wizard. It is handled by the “Logs and Monitoring” tab as below: The desired traffic log can be filtered as it was done earlier: Right-click on the source / destination / Origin (Gateway) / Application. Below the filter is being applied on: Source = 198.51.100.193 and Destination = 198.51.100.193 The filter can be defined by selecting the IP address or service port as below. Happy troubleshooting!!

Let us exploit try the below exploit.. Disclaimer: I did an intense NMAP scan for FTP port and did a couple of trial and errors before figuring out that the port 21 has the “vstfpd_234_backdoor” vulnerability that can be exploited: Exploiting Unix “vstfpd_234_backdoor” vulnerability of Metasploitable 2 using  Armitage. The end result being, the exploited host now presents its shell prompt via which we were able to create our own directory.

Open Armitage from the Kali Linux “Applications” pane – the lady with green hair, as below: Click “Connect” and “OK” for the below prompts: Ignore the below prompts: Enter the target IP of which the vulnerability needs to be exploited. This seems to be a mandatory window, as no matter how many times I click “Cancel” this window continues to pop up. Run the nmap scan as below to find the list of hosts active on a network: A small excerpt of the scan is as follows.. The list of active responding PCs will be discovered in the right window.. My vulnerable host is 192.168.1.111 (Metasploitable host) List of open ports on this host based on the nmap scan: We will exploit a vulnerability in the next post..

You might have come across a problem with your end users using Cisco AnyConnect client wherein, the user continues using that old VPN profile which you replaced with a new one, simply because he still sees the old profile populated there and doesn't want any trouble of entering the new one!!!   The Cisco Anyconnect VPN client usually stores its cache i.e. the list of all the VPN profiles, it has ever used, in the “preferences.xml” file located below: C:\Users\<Username> \AppData\Local\Cisco\Cisco AnyConnect Secure Mobility Client The preferences.xml file, apart from the client certificate should show all the settings that have been changed from the default such as “Block Untrusted Servers”, “Allow local LAN access” etc. The xml file should look like below: Deleting the “preferences.xml” file should delete the cache and revert the client to its default settings, with that old profile vanishing from the end user's client cache, right away!