Kategorie: IT

sftp-Server unter Ubuntu installieren
To configure an SFTP server on Ubuntu, you can use OpenSSH, which is a widely-used and secure implementation of the SSH protocol suite. Here’s a step-by-step guide to setting up an SFTP server using OpenSSH on Ubuntu:
1. Update your system: Before proceeding, it’s a good practice to update your Ubuntu system’s package repositories and installed packages. Open a terminal and run the following commands:
```
sudo apt update
sudo apt upgrade
```
1. Install OpenSSH server: Install the OpenSSH server package by running the following command:
```
sudo apt install openssh-server
```
1. Verify the SSH server status: After installation, the SSH server should start automatically. You can verify its status by running:
```
sudo systemctl status ssh
```
If the SSH server is active and running, you will see a message indicating its status.
1. Configure SSH server options: Open the SSH server configuration file using a text editor like Nano or Vim:
```
sudo nano /etc/ssh/sshd_config
```
In this file, you can customize various options. Here are a few important settings you might want to consider:
- Port: By default, SSH listens on port 22. If you wish to change the port, locate the Port line and modify it accordingly.
- PermitRootLogin: If you want to allow or restrict root login, find the PermitRootLogin line and adjust the value. It’s generally recommended to disable root login for enhanced security.
- PasswordAuthentication: To enforce key-based authentication and disable password-based authentication (recommended for security), locate the PasswordAuthentication line and set it to no.
- AllowUsers (optional): If you want to restrict SSH access to specific users, you can use the AllowUsers directive followed by a space-separated list of usernames. For example, AllowUsers user1 user2. After making any changes, save the file and exit the text editor.
1. Restart the SSH server: To apply the changes made in the configuration file, restart the SSH server by running:
```
sudo systemctl restart ssh
```
1. Create SFTP-only user (optional): If you want to create a user specifically for SFTP access and restrict them from shell access, you can create a user with the nologin shell. Run the following command, replacing sftpuser with the desired username:
```
sudo adduser --shell /usr/sbin/nologin sftpuser
```
Follow the prompts to set a password and additional details for the user.
1. Configure SFTP directory: By default, SSH users can access their home directories via SFTP. However, if you want to restrict a user to a specific directory, you can modify the SSH server configuration. Open the SSH configuration file again:
```
sudo nano /etc/ssh/sshd_config
```
Add the following lines at the end of the file to configure the SFTP directory for a user (replace sftpuser with the actual username and /path/to/directory with the desired directory):
```
Match User sftpuser
    ForceCommand internal-sftp
    ChrootDirectory /path/to/directory
    PermitTunnel no
    AllowAgentForwarding no
    AllowTcpForwarding no
    X11Forwarding no
```
Save the file and exit the text editor.
1. Restart the SSH server: Restart the SSH server again for the configuration changes to take effect:
```
sudo systemctl restart ssh
```
After completing these steps, your SFTP server should be configured and ready to use on Ubuntu. Users can connect to the server using SFTP clients by specifying the server’s IP address

or hostname, the SSH port (default is 22), and their SSH key pair or password, depending on the authentication method allowed by the server.
Linux: schnell eine große Random-Datei erstellen
```
 head -c 350M </dev/urandom > LargeFile.bin
```

ClamAV

ClamAV installieren

sudo apt-get install clamav

Virendefinition aktualisieren

sudo freshclam

Benutzung

clamscan OPTIONS File/Folder 

# z.B.
# To check all files on the computer, displaying the name of each file:

clamscan -r /

# To check all files on the computer, but only display infected files and ring a bell when found:

clamscan -r --bell -i /

# To scan all files on the computer but only display infected files when found and have this run in the background:

clamscan -r -i / &
#Note - Display background process's status by running the jobs command.

# To check files in the all users home directories:

clamscan -r /home

# To check files in the USER home directory and move infected files to another folder:

# clamscan -r --move=/home/USER/VIRUS /home/USER

#To check files in the USER home directory and remove infected files (WARNING: Files are gone.):

clamscan -r --remove /home/USER

# To see more options:

clamscan --help

Docker data in ein anderes Verzeichnis verschieben

Quelle: https://mrkandreev.name/snippets/how_to_move_docker_data_to_another_location/

The standard data location used for docker is /var/lib/docker. Because this directory contains all containers/images/volumes, it can be large. So you no need to store this in OS Volume when you can use separate data volume.

1. Stop daemon

# service docker stop

2. Add configuration file with location of new data directory

Create/Edit /etc/docker/daemon.json file:

{
   "graph": "/path/to/new/docker/location"
}

3. Copy docker files to new location

# rsync -aP /var/lib/docker/ /path/to/new/docker/location

4. Remove old directory

# rm -rf /var/lib/docker

5. Start daemon

# service docker start

6. Copy docker files to new location

# docker run hello-world

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

Mauszeigergeschwindigkeit unter MacOS
Auslesen der aktuellen Geschwindigkeit
```
defaults read -g com.apple.mouse.scaling
```
Festlegen der neuen Geschwindigkeit
```
defaults write -g com.apple.mouse.scaling 20
```
Danach ab- und wieder anmelden

vmware Tools installieren

sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
tar xzvf /mnt/cdrom/VMwareTools-x.x.x-xxxx.tar.gz -C /tmp/
cd /tmp/vmware-tools-distrib/
sudo ./vmware-install.pl

vmware: Alle Shared Folder mounten

sudo vmhgfs-fuse .host:/shared /mnt/hgfs/shared -o allow_other -o uid=1000
MSSQL-Version aus einer *.bak-Datei ermitteln
Folgenden T-SQL-Befehl absetzen:

RESTORE HEADERONLY FROM DISK =‘c:\Backupdir\backupfile.bak‘;

Die Spalte „DatabaseVersion“ gibt dann die MSSQL-Version an, mit welcher dieses Backup erstellt wurde:
- 539 – SQL 2000
- 611 – SQL 2005
- 655 – SQL 2008
- 661 – SQL 2008R2
- 706 – SQL 2012
- 782 – SQL 2014
- 852 – SQL 2016
- 869 – SQL 2017
SQL Server in Docker unter MacOs auf M1

How to Install SQL Server on an M1 Mac (ARM64)
Docker-Schmierzettel

bash in Container

docker exec -it --user root MSSQL2019 "bash"

bspw. MSSQL-Server starten

docker run --name "MSSQL2019" -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=GEHEIM" -e "MSSQL_PID=Express" -v d:\mssql\data:/var/opt/mssql/data -p 1433:1433 -d mcr.microsoft.com/mssql/server:2019-latest