Here’s how you can allow ping through Windows Firewall in Windows Server 2022 with command line or through the graphical user interface (GUI).

1. Command Line

Simply run this command in command prompt or PowerShell to allow ping requests in from any source:

netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow

Alternatively, you can use the Windows graphical user interface to allow this:

2. Allow ping through Windows Firewall GUI

1. First we need to open Windows Firewall, this can be done a few ways. My favorite method is to simply hit the Windows key to open start, then start typing firewall. As shown below Windows Firewall with Advanced Security should show, click this.
   

   Alternatively you can simply type ‘firewall’ and press enter in PowerShell to open the basic firewall interface

2. Scroll down and click “Advanced Settings”.

3. From the Windows Defender Firewall with Advanced Security window that opens up, select Inbound Rules from the menu on the left.

4. From the rules listed under Inbound Rules, select “File and printer Sharing (Echo Request – ICMPv4-In)” and enable the rule.

   Note that this will only allow IPv4 requests in, you can customize the rule to only allow certain IP addresses in if required.

   If you need IPv6 then you will want to enable the “File and Printer Sharing (Echo Request – ICMPv6-In)” rule, listed just below.

5. Once enabled the server should now respond to ping requests. From my desktop I begun to ping my Windows Server 2022 virtual machine at 192.168.162.185 before enabling the rule, and then again after enabling it. You can see below that the first requests timed out, as inbound ICMP requests were disabled by default in Windows Server 2022. As soon as the ICMP rule was enabled, the ping requests start to succeed, confirming that this is working as expected.

Summary

By Default Windows Firewall prevents ICMP echo requests, this results in the server not responding to ping. By enabling this firewall rule we have enabled ping in Windows Server 2022, which can help us with network troubleshooting.

The post How To Enable Ping In Windows Server 2022 Firewall appeared first on RootUsers.

Allowing Remote Desktop With The GUI

Remote desktop can be enabled through the graphical user interface (GUI) with the following easy steps.

1. Open Server Manager. This can be found by opening the start menu, as shown below.
   

   If Server Manager does not show here, simply type “Server Manager” into the start menu to search for it. By default Server Manager will open when you log in to the GUI, otherwise you can select it from the task bar.

2. Within the Server Manager window, select Local Server from the left hand side. You may need to wait a little for it to detect the current state of your system. You should see that Remote Desktop is listed as Disabled as shown below.

3. Click on the Disabled text which will open the System Properties window in the Remote tab.
4. From the System Properties window, select “Allow remote connections to this Computer” as shown below.

   Tip: You can also open the System Properties window shown above by entering “SystemPropertiesRemote” into a Command Prompt or PowerShell terminal.

5. Once you select “Allow remote connections to this computer” the below warning message will appear, advising that this will create the required firewall rules in Windows firewall to allow remote desktop traffic in from any source address, select OK to proceed. You can customize the firewall to only allow certain IP addresses in too.

6. At this point you can optionally click the “Select Users…” button to define specific users or groups that have permission to connect via remote desktop. Select the OK button to close out of the System Properties window and enable remote desktop.
7. Back in Server Manager, Remote Desktop may still show as Disabled until you refresh the view. After clicking the refresh button as highlighted below (or pressing F5 on the keyboard), the status should update to Enabled.

That’s it, remote desktop should now be ready to use!

Allowing Remote Desktop With PowerShell

While there isn’t currently an explicit PowerShell cmdlet used for enabling remote desktop, we can use the Set-ItemPropery cmdlet to modify the registry value that enables or disables Remote Desktop:

Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -name "fDenyTSConnections" -value 0

Once complete we can use the ‘Enable-NetFirewallRule’ to configure Windows Firewall to allow remote desktop connections in:

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Remote Desktop should now be accessible in Windows Server 2022.

By default this will allow all connections in, the same as if we had just enabled it using the GUI steps shown above. It is highly recommended that you configure more specific firewall rules where possible to only allow inbound traffic from known hosts.

Summary

Windows Server 2022 disables external remote desktop connects by default as a security measure. But we can easily enable remote desktop from within the server console GUI or via PowerShell to allow everyone or a specific set of users or groups to connect to RDP.

The post How To Enable Remote Desktop In Windows Server 2022 appeared first on RootUsers.

This can be done both with PowerShell or through the GUI, we’ll cover both methods here.

Install IIS With PowerShell

If you don’t have the GUI installed or just want to use the PowerShell command line interface (CLI) instead, follow these steps. This method is a lot faster than going through all of the GUI options.

1. Open PowerShell with administrative privileges and run the Install-WindowsFeature cmdlet as shown below.

   Install-WindowsFeature -name Web-Server -IncludeManagementTools
   

   Include the management tools so that you can manage IIS on this server. These are normally installed when using the GUI, making this PowerShell command equivalent with the GUI method below. If you do not plan on managing IIS through this server, then don’t use this option.

2. Once the installation has succeeded, you’ll be returned to the PowerShell prompt. At this point IIS should be running on port 80 by default with the firewall rule “World Wide Web Services (HTTP Traffic-In)” enabled in Windows firewall automatically.
3. We can perform a simple test by opening up a web browser and browsing to the server that we have installed IIS on. You should see the default IIS page.

Install IIS Through GUI

If your server has the graphical user interface component installed you can also install IIS by following these steps.

1. Open Server Manager, this can be found in the start menu. If it’s not there simply type “Server Manager” with the start menu open and it should be found in the search.

2. Click the “Add roles and features” text.

3. On the “Before you begin” window, simply click the Next button.

4. On the “Select installation type” window, leave “Role-based or feature-based installation” selected and click Next.

   >

5. As we’re installing to our local machine, leave “Select a server from the server pool” with the current machine selected and click Next. Alternatively you can select another server that you are managing from here, or a VHD.

6. From the “Select server roles” window, check the box next to “Web Server (IIS)”. Doing this may open up a new window advising that additional features are required, simply click the “Add Features” button to install these as well. Click Next back on the Select server roles menu once this is complete.

7. We will not be installing any additional features at this stage, so simply click Next on the “Select features” window.

8. Click Next on the “Web Server Role (IIS)” window after reading the information provided.

9. At this point on the “Select role services” window you can install additional services for IIS if required. You don’t have to worry about this now as you can always come back and add more later, so just click Next for now to install the defaults.

10. Finally on the “Confirm installation selections” window , review the items that are to be installed and click Install when you’re ready to proceed with installing the IIS web server.

    No reboot should be required with a standard IIS installation, however if you remove the role a reboot will be needed.

11. Once the installation has succeeded, click the close button. At this point IIS should be running on port 80 by default with the firewall rule “World Wide Web Services (HTTP Traffic-In)” enabled in Windows firewall automatically.
12. We can perform a simple test by opening up a web browser and browsing to the server that we have installed IIS on. You should see the default IIS page.

As you can see, it’s quite a lot faster to use PowerShell to perform the same task.

Summary

As shown we can easily install the IIS web server in Windows Server 2022 with both the PowerShell command line or the graphical user interface.

The post How To Install IIS In Windows Server 2022 appeared first on RootUsers.

3 Ways to Enable the Telnet Client

Firstly you need to enable the telnet client, if you don’t enable it you’ll get a result similar to the below message when trying to use it.

C:\>telnet google.com 80
'telnet' is not recognized as an internal or external command, operable program or batch file.
C:\>

You can enable the telnet client either by command line or through the graphical interface.

1. Enabling the telnet client through command prompt

Using the command line is the easiest and fastest way to install the telnet client. Run the below command in command prompt with administrator permissions.

dism /online /Enable-Feature /FeatureName:TelnetClient

That’s it, after a few seconds telnet should be ready to use.

2. Enabling the telnet client through PowerShell

We can also do this instead with PowerShell, we can run the below cmdlet in a PowerShell console with administrator permissions which will install the telnet client.

Install-WindowsFeature -name Telnet-Client

Once complete, you should see the following output returned:

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
True    No             Success        {Telnet Client}

3. Enabling the telnet client through the graphical user interface (GUI)

1. Open Server Manager.
2. From Server Manager click “Add roles and features”.
   
3. The Add Roles and Features Wizard opens to the Before you Begin screen, click next.
   
4. On the Installation Type screen, leave Role-based or Feature-based installation selected and click next.
   
5. On the server selection screen, select the server to install on. By default it should be the local server itself, click next.
   
6. On the Server Roles screen, click next. We are installing a feature rather than a role so don’t select anything here.
   
7. On the Features screen, tick the check box next to Telnet Client.
   
8. On the Confirmation screen, click Install.
   
9. Once the installation succeeds, click the Close button. The telnet client is now installed and ready for use.
   

Verifying that the telnet client is enabled

Simply open command prompt or powershell, type ‘telnet’ and press enter. If this was successful you should have a prompt similar to the below:

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet>

This confirms that you have successfully turned on and enabled the telnet client in Windows Server 2022.

Already have telnet installed but still failing?
In some cases you must run command prompt or powershell as administrator in order to issue the telnet command, otherwise it will give the same error as if it was not enabled at all.

Summary

Now that you have installed telnet in Windows Server 2022 you should be able to start issuing commands with it and using it to troubleshoot TCP connectivity problems.

The post How To Enable Telnet Client in Windows Server 2022 appeared first on RootUsers.

In the comments of that video, Nick warned me that the 8 port TL-SX1008 was actively cooled. “No problem!”, I thought, I’ve got enough fans going I’m sure this won’t be much extra.

I was incorrect.

Loud fan noise

Upon first powering on the TL-SX1008 I was greeted to fan noise of ~67dB(A), however before long it settled in at ~47dB(A) while running completely idle – absolutely audible over my other equipment.

I found the fan would ramp up and down a little inconsistently even with minimal network usage, and considering we’re only just exiting winter here in Australia I’d expect the fan to ramp harder in the coming warmer months.

There’s no sort of management interface or otherwise any other way to control the fan speed, at least nothing that stuck out in documentation online.

Stock fan details

Opening the TL-SX1008 is simple, unscrew 6 Phillips head screws and pull off the metal cover, here’s the fan it ships with.

The fan model is EF40201BX-Q18C-F99, after searching for it I was able to find the following spec sheet.

The following helpfully breaks down what the model number means:

Along with the dimensions (40x40x20) which are apparent from just measuring the fan, this tells us it’s 12V, which was on the sticker anyway, but what I found interesting was that the “X” denotes “Super High” fan speed – lucky us. Otherwise it’s noted that it’s a 6,800 RPM fan with an air flow of 10.8 CFM at 28.5dB(A).

The fan appears to use a regular 3-Pin connector, but someone thought it was a good idea to glue it to a nearby capacitor.

I carefully removed the glue from the cable with a knife. Consider holding down the capacitor with your finger while pulling the fan cable out if there’s still some glue sticking it.

The fan is held in with two long Phillips head screws, you can see the nuts holding them in place in the image above.

Replacement fan

After less than a minute of thoroughly researching Google for the best 40mm fan replacement, I settled on the Noctua-NF-A4x20 FLX. The main reason was because it was rated much quieter while also offering increased air flow.

Even at 5,000 RPM it’s quieter, but the NF-A4x20 also comes two low-noise adapters (L.N.A.) should you want to run even quieter. The stock fan at 10.8 CFM equates to 6.36m³/h, so even with Noctua’s ultra-low-noise adapter at 8.5dB(A) we’re getting more at 6.9m³/h.

Given there’s space for a 20mm deep fan, it’s probably not worth considering a 10mm option. Generally more space allows you to get more air flow with quieter operating temperatures, so might as well use the space if you’ve got it!

Installing the new fan

I wasn’t able to install the new fan with the screws from the original fan, at least not without taking out the switches board due to a lack of clearance and I was lazy. I used two of the shorter screws that came with the Noctua fan instead which worked perfectly.

The metal cover fit right back into place, good as new. Well – Almost, the cover still fit perfectly fine but the screws weren’t completely flush against the case so there’s a little bump, but it still closes comfortably. If that’s a concern then just use the screws that came with the original fan.

I measured the new fan at ~37dB(A) during the initial startup, and then once it settled in at idle it was around 36.3dB(A), or very close to my noise floor and barely audible – a massive improvement compared to the stock fan.

Conclusion

TP-Link, you’ve got a nice product here for a reasonable price, but please just increase the price a little more and use a better fan. This simple change has significantly improved my experience with the product, as now I can go back to forgetting about the hardware I use to get the job done.

I understand that this is one of the cheapest 10G 8 port switches out there, and it likely still would be with an extra $10-$20 added to the fan. I suppose this would be less of a problem if you’re deploying it in a server room or elsewhere where the fan noise doesn’t really matter, but at least it’s a relatively easy fix.

Long Term Use Update

June 2022 update: One of the two switches has died, however I don’t believe it’s due to the fan swap. Basically I unplugged one of the switches because I was changing out the desk it was sitting on. All I did was move it carefully to another room and after plugging it back in it didn’t work. It appears to boot up but none of the ports work. There are plenty of reviews online from people having similar issues with ports dying who haven’t changed the fans. It’s probably a case of “buy nice or buy twice”, this is one of the cheapest 10gbe switches available. Anyway I’ve replaced it with a QNAP switch that costs twice as much and runs quiet without any mods. I only bought it because I’ve already been running the same model here for even longer with no issues.

August 2022 update: The 2nd switch has now died lol, so I’m out $1200 AUD or so on these pieces of crap. Going to buy a 2nd QNAP as in above update.

Disclaimer:
We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.

The post How To Fix TP-Link TL-SX1008 Switch Fan Noise appeared first on RootUsers.

In these examples we will cover the Red Hat Certified System Administrator (RHCSA) objective “Create and edit text files”, both through the graphical user interface and command line.

Graphical User Interface

If your installation of Red Hat Enterprise Linux (RHEL) 8 comes with the graphical user interface (GUI) installed, the default, you can open the text editor by following these steps:

1. Click “Activities” towards the top left hand corner of the screen.
2. Select the icon towards the bottom from the bar on the left, allowing you to see more applications.
3. Click on “Text Editor”

Note that this process may differ depending on what display manager your installation is using, this example was done with a fresh default installation of RHEL 8.

Once opened, you’ll have access to a standard text editor where you can write content and then choose where to save the file.

Command Line

The GUI may not always be available, for instance if you’re editing a text file through SSH, so it is important to know how to create and edit text files through the command line interface (CLI).

In this example we’ll be using the ‘vi’ text editor, as it is always available by default within RHEL – perfect for the RHCSA exam. It’s not very beginner friendly unfortunately, so we’ll only be covering the basics of creating and editing text files. Here’s a great game which will help you learn and get better with Vim (vi-improved, basically a newer more modern version of vi).

To edit an existing file, simply enter ‘vi <filename>’ which will open up the file in the vi text editor. If ‘filename’ does not exist, once you save your changes the new file will be created.

In the example below we are creating a new file called ‘testing’ in the current working directory (the home directory of ‘user’, as identified by the ‘~’ symbol at the end of the bash shell).

This is what the vi text editor looks like by default.

At this point vi is in command mode, you cannot yet start typing. To enter text, press ‘i’ to enter insert mode. Insert mode is identified by the – – INSERT – – text down the bottom left corner.

With insert mode activated, we can now edit the text file by typing normally.

Once complete, press the escape key to leave insert mode and go back to command mode. Next we want to save the file and exit vi. To do this, enter ‘:wq’ as shown down the bottom left corner of the screen. The ‘w’ means write the file, so save it, and the ‘q’ means quit vi.

You can of course just use ‘w’ only to save the file without exiting vi. You could also use ‘:q!’ to quit without saving the changes. Combining these into a ‘:wq!’ will save the changes, overwrite the files even if it’s read only if the user account has the privileges and exit vi.

Finally we can check that our new file exists and contains the contents expected.

That’s it, you should now have a basic understanding of how to create and edit text files in RHEL 8 for the RHCSA exam. Make sure you practice these examples yourself to get a full understanding on how the commands work, new Linux users often have trouble escaping vi!

This post is part of our Red Hat Certified System Administrator (RHCSA) exam study guide series for Red Hat Enterprise Linux (RHEL) 8. For more RHCSA related posts and information, see our full RHCSA 8 study guide.

The post Create and edit text files – RHEL 8 RHCSA appeared first on RootUsers.

Create Files and Directories

Let’s start with file creation

Create Files

There are a number of ways to create files within Linux. My favourite way to create a quick test file is with the ‘touch’ command. You simply specify ‘touch’ followed by the name of the file that you want to create.

[root@rhel8 ~]# touch testing
[root@rhel8 ~]# ls -la testing
-rw-rw-r--. 1 root root 0 May 14 00:44 testing

This will create an empty file (we can see above the file size is listed as 0, just before the time stamp) called ‘testing’ in the current working directory. My current session is within the root user’s home directory, /root/, so the file has therefore been created at /root/testing in this example. You can print out the current working directory with the ‘pwd’ command.

The touch command can also be used on an existing file or directory, the act of ‘touching’ it will update the last modified time stamp.

We can also define the specific location where the file should be created:

[root@rhel8 ~]# touch /root/somewhere/file

Another example is using the ‘echo’ command. By default, the ‘echo’ command will print out the text that we feed it, as shown below:

[root@rhel8 ~]# echo "hello"
hello

However we can also use the ‘>’ redirection, as covered in another post, to redirect the output to a new file that we specify:

[root@rhel8 ~]# echo "hello" > hello
[root@rhel8 ~]# cat hello
hello

We have confirmed that our new ‘hello’ file contains the text ‘hello’.

Other tools will create new files too, for instance “vim testing” will open the vim text editor and allow you to edit a file called ‘testing’. The file will not actually be created until you save the file from within the vim editor though.

Create Directories

Directories (also known as folders in Windows) can also be created with a number of different techniques. The most simple way is with the ‘mkdir’ command, simply specify the name of the directory to create afterwards.

[root@rhel8 ~]# mkdir directory

This will create a new directory (or folder) called ‘directory’ in the current working directory. We can now enter it and use it to store content in.

[root@rhel8 ~]# cd directory/
[root@rhel8 directory]# pwd
/root/directory

We can also use the ‘mkdir’ command with the ‘-p’ flag to create parent directories if they do not already exist. In the example below, we can create the sub directory structure /root/directory/one/two/three in one step:

[root@rhel8 directory]# mkdir -p one/two/three
[root@rhel8 directory]# ls -lR
.:
total 0
drwxr-xr-x. 3 root root 16 May 14 00:56 one

./one:
total 0
drwxr-xr-x. 3 root root 18 May 14 00:56 two

./one/two:
total 0
drwxr-xr-x. 2 root root 6 May 14 00:56 three

./one/two/three:
total 0

The ‘-R’ flag from ‘ls’ will list all directories within recursively.

Delete Files and Directories

Now that we know how to create files and directories, how do we delete them?

Delete Files

The ‘rm’ command, short for remove, is used to delete files or directories. In this example, we’ll delete the ‘testing’ file that we created in /root/testing earlier.

[root@rhel8 ~]# rm testing
rm: remove regular empty file ‘testing’? y

When using the ‘rm’ command, by default we’re prompted to confirm removal of the file by pressing the ‘y’ key for yes, followed by enter.

If you’re absolutely sure that you want to remove the file in one command without being prompted to confirm, you can use the ‘-f’ command to force the action. For obvious reasons, you’ll want to be careful with this option.

This would be more useful when deleting many files at once. In the example below, we create two new empty files called ‘testing2’ and ‘testing3’. We then delete everything named ‘testing*’, which includes these two files. The ‘*’ acts as a wildcard, and includes anything starting with the string that precedes it.

[root@rhel8 ~]# touch testing2
[root@rhel8 ~]# touch testing3
[root@rhel8 ~]# rm testing*
rm: remove regular empty file ‘testing2’? y
rm: remove regular empty file ‘testing3’? y

As you can see, we were prompted to remove each individual file, which could get tedious if you need to remove thousands of files within a directory.

Delete Directories

Deleting directories is a little different. The ‘rm’ command is still used, however look what happens if we try to delete a directory in the same manner as a file:

[root@rhel8 ~]# rm directory/
rm: cannot remove ‘directory/’: Is a directory

By default, to remove a directory we need to use the ‘-d’ flag, which is used to remove an empty directory.

[root@rhel8 ~]# rm -d directory/
rm: cannot remove ‘directory/’: Directory not empty

Note that I said empty! To demonstrate this, let’s create a fresh empty directory called ’empty’ and try again:

[root@rhel8 ~]# mkdir empty
[root@rhel8 ~]# rm -vd empty/
rm: remove directory ‘empty/’? y
removed directory: ‘empty/’

In the example above I’ve also used the ‘-v’ flag for verbose, this just outputs some extra information. In this case, the final line confirming that the directory has been removed is given due to the increased verbosity.

Now back to our /root/directory, we created content within here in the demonstration above, sub directories with ‘mkdir’ to be specific. We can either go into the directory and remove the files within first, or we can use the ‘-r’ flag

[root@rhel8 ~]# rm -r directory/
rm: descend into directory ‘directory/’? y
rm: descend into directory ‘directory/one’? y
rm: descend into directory ‘directory/one/two’? y
rm: remove directory ‘directory/one/two/three’? y
rm: remove directory ‘directory/one/two’? y
rm: remove directory ‘directory/one’? y
rm: remove directory ‘directory/’? y

This is another good example where the ‘-f’ flag to force the remove may be useful, as I had to manually confirm with ‘y’ multiple times here. The ‘-r’ flag is recursively deleting all content within /root/directory in the above example. Once the contents are removed, it finishes up clearing out everything within, it deletes the directory specified itself.

You may have heard many stories about the classic ‘rm -rf’ command, and for good reason, it’s extremely powerful and cause a lot of damage. For example if you’re deleting a directory recursively and accidentally put in a space somewhere and specify ‘/’ you’ll start deleting the entire file system. Be careful and don’t start using ‘-f’ until you’ve gotten some practice in.

Fun fact: By default when you run the ‘rm’ command, you’re actually running it with the ‘-i’ flag, which is what causes us to be prompted for every file or directory to remove. This works through a Bash alias – in short there is an alias for ‘rm’ that actually runs ‘rm -i’. To list the different aliases for all commands, simply type ‘alias’ into the Bash shell.

[root@rhel8 ~]# alias rm
alias rm='rm -i'

Copy Files and Directories

We can copy files and directories with the ‘cp’ command.

Copy Files

The ‘cp’ command works by first specifying the file that you want to copy, followed by the destination where you want to copy it to.

Let’s start off by creating an example file to copy.

[root@rhel8 ~]# echo "original" > original
[root@rhel8 ~]# cat original
original

We’ve confirmed our /root/original file contains the text ‘original’, now let’s copy it!

[root@rhel8 ~]# cp original cheapcopy
[root@rhel8 ~]# cat cheapcopy
original

This copies the source file ‘original’ to the destination ‘cheapcopy’, in this example within the same working directory of /root/ as no full path was provided. We could instead specify the path we want to create the copied file however:

[root@rhel8 ~]# cp /root/cheapcopy /tmp/morecopy
[root@rhel8 ~]# cat /tmp/morecopy
original

Unlike when we create a hard link, the raw data is copied into a new inode, the copied files can be modified independently of the original file. Hard links differ in this way, as the hard links all point to the same inode, editing one file will show the same modifications if a different hard link is accessed.

Copy Directories

Like the delete command, we’ll be using the same ‘cp’ command as before with the files, except now to work with directories we’ll need an extra flag.

If we just try to copy a directory in the same way we did with files, this is what happens.

[root@rhel8 ~]# cp originaldir/ copydir/
cp: omitting directory ‘originaldir/’

For this to work, we need the ‘-r’ flag, which specifies recursive.

[root@rhel8 ~]# cp -r originaldir/ copydir

By default this will also copy all of the files within the source directory to the destination, for example:

[root@rhel8 ~]# echo "something" > originaldir/file
[root@rhel8 ~]# cp -r originaldir/ newcopy
[root@rhel8 ~]# cat newcopy/file
something

In the above example we first create /root/originaldir/file containing the text “something”. We then copy the /root/originaldir to /root/newcopy, then confirm that the /root/newcopy/file contains the string “something” as per the original.

Move Files and Directories

Moving files and directories is similar to copying, except rather than copying the content we’re moving the original.

Move Files

Moving files is done with the ‘mv’ command, similar to ‘cp’ above we first specify the source file, followed by the destination where we wish to move the file.

[root@rhel8 ~]# echo "movethis" > movethis
[root@rhel8 ~]# mv movethis alright
[root@rhel8 ~]# cat alright
movethis

In this example, we first create the file ‘movethis’ containing the string ‘movethis’. Next we use the ‘mv’ command to move ‘movethis’ to ‘alright’, and view the contents of our newly moved file ‘alright’ to confirm they are as expected.

This example is essentially just renaming the file, we’re moving it from within the current working directory to the same directory but with a different name. This is also generally how you rename files within Linux.

We can of course work with full paths as well, in this example we move our newly moved file to the /tmp directory.

[root@rhel8 ~]# mv /root/alright /tmp/movedagain
[root@rhel8 ~]# cat /tmp/movedagain
movethis

By default you will be prompted if you attempt to move a file to one that already exists, you’ll be given the option to overwrite the destination file, or you can also specify the ‘-f’ flag to force the overwrite without being prompted.

Move Directories

Moving directories with the ‘mv’ command is quite straightforward, it’s the same as moving files, no additional flags are needed.

[root@rhel8 ~]# mkdir newdir
[root@rhel8 ~]# mv newdir moveddir

This will also move anything within the directory:

[root@rhel8 ~]# echo "hello" > moveddir/hello
[root@rhel8 ~]# mv moveddir/ movedagain
[root@rhel8 ~]# cat movedagain/hello
hello

Documentation

During the RHCSA exam you will have access to built in documentation, you can find information on these commands and their flags by running the following commands to view the manual pages:

man cp
man rm
man mv

Basically just use ‘man’ followed by the command name to see the manual page for it.

That’s it, you should now have a basic understanding of how to create, delete, copy and move files and directories in RHEL 8 for the RHCSA exam. Make sure you practice these examples yourself to get a full understanding on how the commands work.

This post is part of our Red Hat Certified System Administrator (RHCSA) exam study guide series for Red Hat Enterprise Linux (RHEL) 8. For more RHCSA related posts and information, see our full RHCSA 8 study guide.

The post Create, delete, copy, and move files and directories – RHEL 8 RHCSA appeared first on RootUsers.

In these examples we will cover the Red Hat Certified System Administrator (RHCSA) objective “Create hard and soft links”.

Create Hard and Soft Links

In these examples we’ll be dealing with two types of links, soft links and hard links. We’ll be using the ‘ln’ command to create both types of links.

Hard Links

Every file on the file system is essentially a hard link to an inode. An inode (index node) is a data structure that described an object, such as a file or directory. The inode stores the actual data of the object, while the hard link is what actually points to the inode.

For example, if we create a new file:

[root@rhel8 ~]# echo "testing" > /root/testing

The file ‘/root/testing’ has been created, and is essentially a hard link to the inode containing the string of “testing”.

Creating a new hard link makes another object that points to the same inode. You can have multiple hard links pointing to an inode, as long as one hard link still exists, the actual file will remain present on the file system.

This example uses the ‘ln’ command to create a new hard link.

[root@rhel8 ~]# ln /root/testing /root/hardlink

The file /root/hardlink points to the same inode as /root/testing, which is why it just appears as another file on the file system:

[root@rhel8 ~]# ls -la /root
-rw-r--r--.  2 root  root       8 May 13 07:05 hardlink
-rw-r--r--.  2 root  root       8 May 13 07:05 testing

Note the ‘2’ before the user and group ownership, this refers to the fact that the file has two hard links to it, as both are now pointing to the same inode.

We can confirm this by viewing the content of the hardlink:

[root@rhel8 ~]#  cat /root/hardlink
testing

If we delete the original /root/testing file, the data will still be accessible via /root/hardlink

[root@rhel8 ~]# rm -f /root/testing
[root@rhel8 ~]# ls -la /root/hardlink
-rw-r--r--. 1 root root 8 May 13 07:05 /root/hardlink

Now that /root/testing is removed, the ‘2’ from earlier is now a ‘1’, as /root/hardlink is the only hard link to the inode containing the string ‘testing’. If we delete the last link, the data will be removed.

As hard links point to the same raw data, if we edit the content of a file through a hard link, then attempt to edit the file through a different hard link, the changes from the first edit will be there – we’re not copying the files like with the ‘cp’ command, we’re linking to the same location on disk multiple times.

Hard links only work on the same file system, it is not possible to create a hard link on one file system to something on a separate file system. This is possible with symlinks, however.

Soft Links

While hard links point to the direct inode, a soft link, also known as a symbolic link, or symlink for short, simply acts as a redirection. If you open a soft link, you’ll be redirected to the location that the soft link points to. The link exists independently to the file that it points to. If the original file is deleted, the link will still exist, albeit pointing to a location that no longer exists. Likewise if the soft link is deleted, it does not affect the file that the link points to.

The following example shows how to create a soft link using the ‘ln’ command. The syntax is almost identical to the hard link example shown previously, except the ‘-s’ flag is used to specify that this is a symbolic link, instead of a hard link which is the default.

In this example, we will create a soft link to our previous hard link, though as we now know the hard link is essentially a normal file on the Linux file system.

[root@rhel8 ~]# ln -s /root/hardlink /root/softlink

Now let’s look at what we have created:

[root@rhel8 ~]# ls -la /root/softlink
lrwxrwxrwx. 1 root root 14 May 13 07:11 /root/softlink -> /root/hardlink

We can see that /root/softlink has been created, and the redirection can be identified by the ‘->’ arrow symbol, which in this case points to the underlying file /root/hardlink.

Now if we try and access the soft link, we should retrieve the contents we previously created with the echo command in the hard link section above.

[root@rhel8 ~]# cat /root/softlink
testing

Success! This is the text we originally created in the /root/testing file, prior to creating our hard link (essentially just another reference to the actual inode that contains the string ‘testing’).

This is what we’ve done so far in a diagram:

If we move or rename the hard link, it will still point to the inode containing the string and be accessible, however the soft link will fail, as it is pointing to the name of the file ‘/root/hardlink’ rather than the inode.

Likewise if we delete the file the soft link points to, the soft link will still exist, however the contents are gone so attempting to access the destination via the soft link fails:

[root@rhel8 ~]# rm -f /root/hardlink
[root@rhel8 ~]# ls -la /root/softlink
lrwxrwxrwx. 1 root root 14 May 13 07:18 /root/softlink -> /root/hardlink
[root@rhel8 ~]# cat /root/softlink
cat: /root/softlink: No such file or directory

We can also tidy up and delete the soft link without affecting the file that it points to as follows:

[root@rhel8 ~]# rm /root/softlink
rm: remove symbolic link ‘/root/softlink’? y

This will leave the destination the link points to intact, only the soft link will be removed.

Unlike hard links, soft links can cross between different file systems. Additionally, soft links can point to directories, however hard links cannot.

Should you forget the syntax, you can simply refer to the man page through ‘man ln’ during the exam.

That’s it, you should now have a basic understanding of how to create hard and soft links in RHEL 8 for the RHCSA exam. Make sure you practice these examples yourself to get a full understanding on how the commands work.

This post is part of our Red Hat Certified System Administrator (RHCSA) exam study guide series for Red Hat Enterprise Linux (RHEL) 8. For more RHCSA related posts and information, see our full RHCSA 8 study guide.

The post Create hard and soft links – RHEL 8 RHCSA appeared first on RootUsers.

Testing was completed with the latest drivers available, Adrenalin 19.2.1, and Hashcat x64 version 5.1.0.

System specs:
CPU: Intel i7-8700K at stock
GPU: AMD Radeon VII
RAM: 16GB (2x 8gb) DDR4-3200
OS: Windows 10 1809

C:\Users\user\Desktop\hashcat-5.1.0>hashcat64.exe --benchmark-all -b
hashcat (v5.1.0) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx906, 4048/16192 MB allocatable, 60MCU

Benchmark relevant options:
===========================
* --benchmark-all
* --optimized-kernel-enable

Hashmode: 0 - MD5

Speed.#1.........: 29391.2 MH/s (67.35ms) @ Accel:256 Loops:512 Thr:256 Vec:1

Hashmode: 10 - md5($pass.$salt)

Speed.#1.........: 29366.4 MH/s (67.46ms) @ Accel:256 Loops:512 Thr:256 Vec:1

Hashmode: 11 - Joomla < 2.5.18

Speed.#1.........: 29212.0 MH/s (67.89ms) @ Accel:256 Loops:512 Thr:256 Vec:1

Hashmode: 12 - PostgreSQL

Speed.#1.........: 29154.0 MH/s (67.98ms) @ Accel:256 Loops:512 Thr:256 Vec:1

Hashmode: 20 - md5($salt.$pass)

Speed.#1.........: 15910.7 MH/s (62.37ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 21 - osCommerce, xt:Commerce

Speed.#1.........: 15978.6 MH/s (61.96ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 22 - Juniper NetScreen/SSG (ScreenOS)

Speed.#1.........: 16046.5 MH/s (61.66ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 23 - Skype

Speed.#1.........: 16066.4 MH/s (61.66ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 30 - md5(utf16le($pass).$salt)

Speed.#1.........: 28919.1 MH/s (68.52ms) @ Accel:256 Loops:512 Thr:256 Vec:1

Hashmode: 40 - md5($salt.utf16le($pass))

Speed.#1.........: 16091.9 MH/s (61.52ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 50 - HMAC-MD5 (key = $pass)

Speed.#1.........:  4821.4 MH/s (51.05ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 60 - HMAC-MD5 (key = $salt)

Speed.#1.........:  9557.2 MH/s (51.57ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 100 - SHA1

Speed.#1.........: 11955.6 MH/s (83.03ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 101 - nsldap, SHA-1(Base64), Netscape LDAP SHA

Speed.#1.........: 11966.0 MH/s (83.04ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 110 - sha1($pass.$salt)

Speed.#1.........: 11959.8 MH/s (83.06ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 111 - nsldaps, SSHA-1(Base64), Netscape LDAP SSHA

Speed.#1.........: 11953.5 MH/s (83.02ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 112 - Oracle S: Type (Oracle 11+)

Speed.#1.........: 11980.3 MH/s (82.96ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 120 - sha1($salt.$pass)

Speed.#1.........:  8684.3 MH/s (56.90ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 121 - SMF (Simple Machines Forum) > v1.1

Speed.#1.........:  8664.7 MH/s (56.90ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 122 - macOS v10.4, macOS v10.5, MacOS v10.6

Speed.#1.........:  8697.8 MH/s (56.84ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 124 - Django (SHA-1)

Speed.#1.........:  8701.5 MH/s (56.80ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 125 - ArubaOS

Speed.#1.........:  8696.8 MH/s (56.80ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 130 - sha1(utf16le($pass).$salt)

Speed.#1.........: 12027.7 MH/s (82.62ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 131 - MSSQL (2000)

Speed.#1.........: 12015.5 MH/s (82.69ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 132 - MSSQL (2005)

Speed.#1.........: 12023.3 MH/s (82.65ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 133 - PeopleSoft

Speed.#1.........: 12027.9 MH/s (82.63ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 140 - sha1($salt.utf16le($pass))

Speed.#1.........:  8717.0 MH/s (56.71ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 141 - Episerver 6.x < .NET 4

Speed.#1.........:  8713.8 MH/s (56.71ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 150 - HMAC-SHA1 (key = $pass)

Speed.#1.........:  2401.4 MH/s (51.32ms) @ Accel:128 Loops:64 Thr:256 Vec:1

Hashmode: 160 - HMAC-SHA1 (key = $salt)

Speed.#1.........:  4369.3 MH/s (56.50ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 200 - MySQL323

Speed.#1.........:   115.9 GH/s (33.74ms) @ Accel:256 Loops:1024 Thr:256 Vec:1

Hashmode: 300 - MySQL4.1/MySQL5

Speed.#1.........:  5068.4 MH/s (48.58ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 400 - phpass, WordPress (MD5), phpBB3 (MD5), Joomla (MD5) (Iterations: 2048)

Speed.#1.........:  8903.5 kH/s (53.65ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 500 - md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) (Iterations: 1000)

Speed.#1.........: 13328.9 kH/s (69.78ms) @ Accel:512 Loops:500 Thr:64 Vec:1

Hashmode: 501 - Juniper IVE (Iterations: 1000)

Speed.#1.........: 13527.4 kH/s (69.78ms) @ Accel:512 Loops:500 Thr:64 Vec:1

Hashmode: 600 - BLAKE2b

Speed.#1.........:  2683.6 MH/s (92.66ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 900 - MD4

Speed.#1.........: 54794.3 MH/s (72.40ms) @ Accel:256 Loops:1024 Thr:256 Vec:1

Hashmode: 1000 - NTLM

Speed.#1.........: 55155.3 MH/s (71.92ms) @ Accel:256 Loops:1024 Thr:256 Vec:1

Hashmode: 1100 - Domain Cached Credentials (DCC), MS Cache

Speed.#1.........: 16735.7 MH/s (59.14ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 1300 - SHA2-224

Speed.#1.........:  4677.5 MH/s (52.65ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1400 - SHA2-256

Speed.#1.........:  4794.4 MH/s (51.46ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1410 - sha256($pass.$salt)

Speed.#1.........:  4785.4 MH/s (51.46ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1411 - SSHA-256(Base64), LDAP {SSHA256}

Speed.#1.........:  4780.3 MH/s (51.44ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1420 - sha256($salt.$pass)

Speed.#1.........:  4360.7 MH/s (56.67ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1421 - hMailServer

Speed.#1.........:  4365.3 MH/s (56.66ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1430 - sha256(utf16le($pass).$salt)

Speed.#1.........:  4748.4 MH/s (51.72ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1440 - sha256($salt.utf16le($pass))

Speed.#1.........:  4364.8 MH/s (56.58ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1441 - Episerver 6.x >= .NET 4

Speed.#1.........:  4384.5 MH/s (56.59ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 1450 - HMAC-SHA256 (key = $pass)

Speed.#1.........:  1020.3 MH/s (60.76ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1460 - HMAC-SHA256 (key = $salt)

Speed.#1.........:  2064.2 MH/s (59.97ms) @ Accel:128 Loops:64 Thr:256 Vec:1

Hashmode: 1500 - descrypt, DES (Unix), Traditional DES

Speed.#1.........:  1083.1 MH/s (56.49ms) @ Accel:4 Loops:1024 Thr:256 Vec:1

Hashmode: 1600 - Apache $apr1$ MD5, md5apr1, MD5 (APR) (Iterations: 1000)

Speed.#1.........: 13470.6 kH/s (69.72ms) @ Accel:512 Loops:500 Thr:64 Vec:1

Hashmode: 1700 - SHA2-512

Speed.#1.........:  1235.5 MH/s (49.92ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1710 - sha512($pass.$salt)

Speed.#1.........:  1235.2 MH/s (49.91ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1711 - SSHA-512(Base64), LDAP {SSHA512}

Speed.#1.........:  1235.7 MH/s (49.93ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1720 - sha512($salt.$pass)

Speed.#1.........:  1174.3 MH/s (52.63ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1722 - macOS v10.7

Speed.#1.........:  1172.4 MH/s (52.62ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1730 - sha512(utf16le($pass).$salt)

Speed.#1.........:  1233.5 MH/s (49.93ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1731 - MSSQL (2012, 2014)

Speed.#1.........:  1236.3 MH/s (49.95ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1740 - sha512($salt.utf16le($pass))

Speed.#1.........:  1180.1 MH/s (52.20ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 1750 - HMAC-SHA512 (key = $pass)

Speed.#1.........:   201.9 MH/s (76.72ms) @ Accel:64 Loops:16 Thr:256 Vec:1

Hashmode: 1760 - HMAC-SHA512 (key = $salt)

Speed.#1.........:   396.7 MH/s (78.24ms) @ Accel:64 Loops:32 Thr:256 Vec:1

Hashmode: 1800 - sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)

Speed.#1.........:   197.3 kH/s (62.18ms) @ Accel:256 Loops:64 Thr:64 Vec:1

Hashmode: 2100 - Domain Cached Credentials 2 (DCC2), MS Cache 2 (Iterations: 10240)

Speed.#1.........:   427.9 kH/s (56.74ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 2400 - Cisco-PIX MD5

Speed.#1.........: 20783.9 MH/s (47.46ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 2410 - Cisco-ASA MD5

Speed.#1.........: 19386.2 MH/s (50.89ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)

* Device #1: ATTENTION! OpenCL kernel self-test failed.

Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver

Speed.#1.........:   534.4 kH/s (56.88ms) @ Accel:128 Loops:64 Thr:256 Vec:1

Hashmode: 2501 - WPA-EAPOL-PMK (Iterations: 1)

Speed.#1.........:   287.3 MH/s (0.04ms) @ Accel:256 Loops:1 Thr:256 Vec:1

Hashmode: 2600 - md5(md5($pass))

Speed.#1.........:  9446.4 MH/s (52.32ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 2611 - vBulletin < v3.8.5

Speed.#1.........:  9446.8 MH/s (52.23ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 2612 - PHPS

Speed.#1.........:  9453.3 MH/s (52.19ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 2711 - vBulletin >= v3.8.5

Speed.#1.........:  6452.9 MH/s (77.16ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 2811 - IPB2+ (Invision Power Board), MyBB 1.2+

Speed.#1.........:  6674.6 MH/s (74.50ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 3000 - LM

Speed.#1.........: 27869.1 MH/s (71.01ms) @ Accel:128 Loops:1024 Thr:256 Vec:1

Hashmode: 3100 - Oracle H: Type (Oracle 7+)

Speed.#1.........:  1976.7 MH/s (62.89ms) @ Accel:128 Loops:64 Thr:256 Vec:1

Hashmode: 3200 - bcrypt $2*$, Blowfish (Unix) (Iterations: 32)

Speed.#1.........:    25530 H/s (72.94ms) @ Accel:16 Loops:8 Thr:8 Vec:1

Hashmode: 3710 - md5($salt.md5($pass))

Speed.#1.........:  8254.8 MH/s (60.12ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 3711 - MediaWiki B type

Speed.#1.........:  8257.6 MH/s (60.15ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 3800 - md5($salt.$pass.$salt)

Speed.#1.........: 16112.3 MH/s (61.61ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 3910 - md5(md5($pass).md5($salt))

Speed.#1.........:  6453.8 MH/s (77.13ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 4010 - md5($salt.md5($salt.$pass))

Speed.#1.........:  7446.1 MH/s (66.79ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 4110 - md5($salt.md5($pass.$salt))

Speed.#1.........:  8020.4 MH/s (61.87ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 4300 - md5(strtoupper(md5($pass)))

Speed.#1.........:  9505.5 MH/s (52.12ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 4400 - md5(sha1($pass))

Speed.#1.........:  6189.5 MH/s (80.47ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 4500 - sha1(sha1($pass))

Speed.#1.........:  4572.9 MH/s (54.15ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 4520 - sha1($salt.sha1($pass))

Speed.#1.........:  3982.5 MH/s (62.33ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 4521 - Redmine

Speed.#1.........:  3987.3 MH/s (62.32ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 4522 - PunBB

Speed.#1.........:  3982.8 MH/s (62.30ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 4700 - sha1(md5($pass))

Speed.#1.........:  6230.8 MH/s (79.88ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 4800 - iSCSI CHAP authentication, MD5(CHAP)

Speed.#1.........: 19457.6 MH/s (50.95ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 4900 - sha1($salt.$pass.$salt)

Speed.#1.........:  7895.2 MH/s (62.88ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 5100 - Half MD5

Speed.#1.........: 18822.1 MH/s (52.64ms) @ Accel:256 Loops:256 Thr:256 Vec:1

Hashmode: 5200 - Password Safe v3 (Iterations: 2048)

Speed.#1.........:  1947.3 kH/s (62.45ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 5300 - IKE-PSK MD5

Speed.#1.........:  2404.9 MH/s (51.47ms) @ Accel:128 Loops:64 Thr:256 Vec:1

Hashmode: 5400 - IKE-PSK SHA1

Speed.#1.........:   765.0 MH/s (81.42ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 5500 - NetNTLMv1 / NetNTLMv1+ESS

Speed.#1.........: 33775.1 MH/s (58.82ms) @ Accel:256 Loops:512 Thr:256 Vec:1

Hashmode: 5600 - NetNTLMv2

Speed.#1.........:  2229.4 MH/s (55.57ms) @ Accel:128 Loops:64 Thr:256 Vec:1

Hashmode: 5700 - Cisco-IOS type 4 (SHA256)

Speed.#1.........:  4808.7 MH/s (51.50ms) @ Accel:256 Loops:64 Thr:256 Vec:1

Hashmode: 5800 - Samsung Android Password/PIN (Iterations: 1023)

Speed.#1.........:  7173.7 kH/s (59.58ms) @ Accel:256 Loops:127 Thr:256 Vec:1

Hashmode: 6000 - RIPEMD-160

Speed.#1.........:  6464.5 MH/s (76.94ms) @ Accel:256 Loops:128 Thr:256 Vec:1

Hashmode: 6100 - Whirlpool

Speed.#1.........:   844.8 MH/s (73.64ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 6211 - TrueCrypt PBKDF2-HMAC-RIPEMD160 + XTS 512 bit (Iterations: 2000)

Speed.#1.........:   411.1 kH/s (76.02ms) @ Accel:128 Loops:32 Thr:256 Vec:1

Hashmode: 6212 - TrueCrypt PBKDF2-HMAC-RIPEMD160 + XTS 1024 bit (Iterations: 2000)

Speed.#1.........:   235.4 kH/s (66.37ms) @ Accel:64 Loops:32 Thr:256 Vec:1

Hashmode: 6213 - TrueCrypt PBKDF2-HMAC-RIPEMD160 + XTS 1536 bit (Iterations: 2000)

Comparisons against other GPUs is an exercise left for the reader.

The post AMD Radeon VII – Hashcat Benchmark appeared first on RootUsers.

In this guide we will cover how to allow ping through Windows Firewall in Windows Server 2019.

A common response is usually to simply disable Windows Firewall entirely, however this is not recommended as the Windows Firewall does a good job at providing a basic level of system protection. We will only be allowing the specific rules required to allow ping to succeed.

Allow ping through Windows Firewall

1. First we need to open Windows Firewall, this can be done a few ways. My favourite method is to simply hit the Windows key to open start, then start typing firewall. As shown below Windows Firewall with Advanced Security should show, click this.
   

   Alternatively you can simply type ‘firewall’ and press enter in PowerShell to open the basic firewall interface, then click “Advanced settings” on the left hand side – this will open the same interface listed in the start menu.

2. From the Windows Firewall with Advanced Security window that opens up, select Inbound Rules from the menu on the left.

3. From the rules listed under Inbound Rules, select “File and printer Sharing (Echo Request – ICMPv4-In)” and enable the rule.

   Note that this will only allow IPv4 requests in, if you need IPv6 then you will want to enable the “File and Printer Sharing (Echo Request – ICMPv6-In)” rule, listed just below.





4. Once enabled the server should now respond to ping requests. From my desktop I begun to ping my Windows Server 2019 virtual machine at 192.168.75.133 before enabling the rule, and then again after enabling it. You can see below that the first requests timed out, as inbound ICMP requests were disabled by default in Windows Server 2019. After enabling the ICMP rule, the ping requests succeed, confirming that this is working as expected.

Summary

By Default Windows Firewall prevents ICMP echo requests, this results in the server not responding to ping. By enabling this firewall rule we have enabled ping in Windows Server 2019, which can help us with network troubleshooting.

The post How To Enable Ping In Windows Server 2019 Firewall appeared first on RootUsers.