Author Stefan Hinker helps you understand the general security concerns in virtualized environments as well as the specific additional threats that arise out of them.
Hello all, thanks for reading my question:
So I've been a Unix/Linux SysAdmin for a couple years, and I'm a bit over my head running solo, trying to set up LDoms using Oracle VM Server 3.1 for SPARC. I've been very careful, and things have gone well up until the point I try to access the new... (9 Replies)
I am getting following error during deployment in solaris. when i deploy same war in other machine (non-solaris) it works fine. the stacktrace is
< ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277738498407> <BEA-149205> <Failed to initialize the... (0 Replies)
Heya,
my university department wants to deploy a UNIX based system instead of various unnetokred windows PCs. We are trying to build a terminal server solution on either FreeBSD,Solaris or Debian Linux. The system would mostly run office applications on X11 and file sharing (with Samba). In... (4 Replies)
I am using shell script to do secure ftp. I have done key file setup to do password less authentication. Following are the FTP Details:
FTP Client has Sun SSH.
FTP Server has F-Secure.
I am using SCP Command to do secure copy files. When I am doing this, I am getting the foll error
scp:... (2 Replies)
SYSTEMD-DETECT-VIRT(1) systemd-detect-virt SYSTEMD-DETECT-VIRT(1)NAME
systemd-detect-virt - Detect execution in a virtualized environment
SYNOPSIS
systemd-detect-virt [OPTIONS...]
DESCRIPTION
systemd-detect-virt detects execution in a virtualized environment. It identifies the virtualization technology and can distinguish full
machine virtualization from container virtualization. systemd-detect-virt exits with a return value of 0 (success) if a virtualization
technology is detected, and non-zero (error) otherwise. By default, any type of virtualization is detected, and the options --container and
--vm can be used to limit what types of virtualization are detected.
When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are
currently identified:
Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization)
+----------+----------------+--------------------------------------+
|Type | ID | Product |
+----------+----------------+--------------------------------------+
|VM | qemu | QEMU software virtualization, |
| | | without KVM |
| +----------------+--------------------------------------+
| | kvm | Linux KVM kernel virtual machine, |
| | | with whatever software, except |
| | | Oracle Virtualbox |
| +----------------+--------------------------------------+
| | zvm | s390 z/VM |
| +----------------+--------------------------------------+
| | vmware | VMware Workstation or Server, and |
| | | related products |
| +----------------+--------------------------------------+
| | microsoft | Hyper-V, also known as Viridian or |
| | | Windows Server Virtualization |
| +----------------+--------------------------------------+
| | oracle | Oracle VM VirtualBox (historically |
| | | marketed by innotek and Sun |
| | | Microsystems), |
| | | for legacy and KVM |
| | | hypervisor |
| +----------------+--------------------------------------+
| | xen | Xen hypervisor (only domU, not dom0) |
| +----------------+--------------------------------------+
| | bochs | Bochs Emulator |
| +----------------+--------------------------------------+
| | uml | User-mode Linux |
| +----------------+--------------------------------------+
| | parallels | Parallels Desktop, Parallels Server |
| +----------------+--------------------------------------+
| | bhyve | bhyve, FreeBSD hypervisor |
+----------+----------------+--------------------------------------+
|Container | openvz | OpenVZ/Virtuozzo |
| +----------------+--------------------------------------+
| | lxc | Linux container implementation by |
| | | LXC |
| +----------------+--------------------------------------+
| | lxc-libvirt | Linux container implementation by |
| | | libvirt |
| +----------------+--------------------------------------+
| | systemd-nspawn | systemd's minimal container |
| | | implementation, see systemd- |
| | | nspawn(1) |
| +----------------+--------------------------------------+
| | docker | Docker container manager |
| +----------------+--------------------------------------+
| | rkt | rkt app container runtime |
+----------+----------------+--------------------------------------+
If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container
virtualization are used in conjunction, only the latter will be identified (unless --vm is passed).
OPTIONS
The following options are understood:
-c, --container
Only detects container virtualization (i.e. shared kernel virtualization).
-v, --vm
Only detects hardware virtualization).
-r, --chroot
Detect whether invoked in a chroot(2) environment. In this mode, no output is written, but the return value indicates whether the
process was invoked in a chroot() environment or not.
--private-users
Detect whether invoked in a user namespace. In this mode, no output is written, but the return value indicates whether the process was
invoked inside of a user namespace or not. See user_namespaces(7) for more information.
-q, --quiet
Suppress output of the virtualization technology identifier.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
If a virtualization technology is detected, 0 is returned, a non-zero code otherwise.
SEE ALSO systemd(1), systemd-nspawn(1), chroot(2), namespaces(7)systemd 237SYSTEMD-DETECT-VIRT(1)