This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
$certs = Get-ChildItem Cert:\LocalMachine\My
foreach ($cert in $certs) {
$sidExtension = $cert.Extensions | Where-Object { $_.Oid.Value -eq "1.3.6.1.4.1.311.25.2" }
[PSCustomObject]@{
Thumbprint = $cert.Thumbprint
Subject = $cert.Subject
HasStrongSID = [bool]$sidExtension
}
}
su root
apt update
apt install ca-certificates curl gnupg -y
curl -fsSL https://download.docker.com/linux/debian/gpg | gpg --dearmor -o /etc/apt/keyrings/docker.gpg
chmod a+r /etc/apt/keyrings/docker.gpg
echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
$(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
apt update
apt install docker-ce docker-ce-cli
systemctl status docker
mkdir -p /opt/rustdesk
cd /opt/rustdesk
nano /opt/rustdesk/compose.yaml
และ ใส่ content ดังนี้services:
hbbs:
image: rustdesk/rustdesk-server:latest
container_name: hbbs
command: hbbs
network_mode: host
volumes:
- ./data:/root
restart: unless-stopped
depends_on:
- hbbr
hbbr:
image: rustdesk/rustdesk-server:latest
container_name: hbbr
command: hbbr
network_mode: host
volumes:
- ./data:/root
restart: unless-stopped
cd /opt/rustdesk
docker compose up -d
c:\temp\policies
\\yourdomain.com\SYSVOL\yourdomain.com\Policies\PolicyDefinitions
หมายเหตุ: folder PolicyDefinitions นั้นปกติ จะไม่มีอยู่ ให้ท่านสร้างเพิ่มเองก่อนนำไฟล์ไปวาง
sudo apt-get update && sudo apt-get install ca-certificates curl -y
curl -sO https://get.glennr.nl/unifi/update/unifi-update.sh && bash unifi-update.sh
sudo apt install -y wget gpg apt-transport-https lsb-release
sudo mkdir -p /etc/apt/keyrings
wget -qO- https://packages.adoptium.net/artifactory/api/gpg/key/public \
| sudo gpg --dearmor -o /etc/apt/keyrings/adoptium.gpg
echo "deb [signed-by=/etc/apt/keyrings/adoptium.gpg] \
https://packages.adoptium.net/artifactory/deb $(lsb_release -cs) main" \
| sudo tee /etc/apt/sources.list.d/adoptium.list
sudo apt update
sudo apt install -y temurin-17-jdk
sudo update-alternatives --config java
echo "deb [signed-by=/etc/apt/keyrings/apache-cassandra.asc] https://debian.cassandra.apache.org 50x main" | sudo tee -a /etc/apt/sources.list.d/cassandra.sources.list
curl -o /etc/apt/keyrings/apache-cassandra.asc https://downloads.apache.org/cassandra/KEYS
sudo apt update
audo apt install cassandra
#
# It is possible to use FSAL_CEPH to provide an NFS gateway to CephFS. The
# following sample config should be useful as a starting point for
# configuration. This basic configuration is suitable for a standalone NFS
# server, or an active/passive configuration managed by some sort of clustering
# software (e.g. pacemaker, docker, etc.).
#
# Note too that it is also possible to put a config file in RADOS, and give
# ganesha a rados URL from which to fetch it. For instance, if the config
# file is stored in a RADOS pool called "nfs-ganesha", in a namespace called
# "ganesha-namespace" with an object name of "ganesha-config":
#
# %url rados://nfs-ganesha/ganesha-namespace/ganesha-config
#
# If we only export cephfs (or RGW), store the configs and recovery data in
# RADOS, and mandate NFSv4.1+ for access, we can avoid any sort of local
# storage, and ganesha can run as an unprivileged user (even inside a
# locked-down container).
#
NFS_CORE_PARAM
{
# Ganesha can lift the NFS grace period early if NLM is disabled.
Enable_NLM = false;
# rquotad doesn't add any value here. CephFS doesn't support per-uid
# quotas anyway.
Enable_RQUOTA = false;
# In this configuration, we're just exporting NFSv4. In practice, it's
# best to use NFSv4.1+ to get the benefit of sessions.
Protocols = 4;
}
NFSv4
{
# Modern versions of libcephfs have delegation support, though they
# are not currently recommended in clustered configurations. They are
# disabled by default but can be re-enabled for singleton or
# active/passive configurations.
# Delegations = false;
# One can use any recovery backend with this configuration, but being
# able to store it in RADOS is a nice feature that makes it easy to
# migrate the daemon to another host.
#
# For a single-node or active/passive configuration, rados_ng driver
# is preferred. For active/active clustered configurations, the
# rados_cluster backend can be used instead. See the
# ganesha-rados-grace manpage for more information.
RecoveryBackend = rados_ng;
# NFSv4.0 clients do not send a RECLAIM_COMPLETE, so we end up having
# to wait out the entire grace period if there are any. Avoid them.
Minor_Versions = 1,2;
}
# The libcephfs client will aggressively cache information while it
# can, so there is little benefit to ganesha actively caching the same
# objects. Doing so can also hurt cache coherency. Here, we disable
# as much attribute and directory caching as we can.
MDCACHE {
# Size the dirent cache down as small as possible.
Dir_Chunk = 0;
}
EXPORT
{
# Unique export ID number for this export
Export_ID=100;
# We're only interested in NFSv4 in this configuration
Protocols = 4;
# NFSv4 does not allow UDP transport
Transports = TCP;
#
# Path into the cephfs tree.
#
# Note that FSAL_CEPH does not support subtree checking, so there is
# no way to validate that a filehandle presented by a client is
# reachable via an exported subtree.
#
# For that reason, we just export "/" here.
Path = /;
#
# The pseudoroot path. This is where the export will appear in the
# NFS pseudoroot namespace.
#
Pseudo = /cephfs_a/;
# We want to be able to read and write
Access_Type = RW;
# Time out attribute cache entries immediately
Attr_Expiration_Time = 0;
# Enable read delegations? libcephfs v13.0.1 and later allow the
# ceph client to set a delegation. While it's possible to allow RW
# delegations it's not recommended to enable them until ganesha
# acquires CB_GETATTR support.
#
# Note too that delegations may not be safe in clustered
# configurations, so it's probably best to just disable them until
# this problem is resolved:
#
# http://tracker.ceph.com/issues/24802
#
# Delegations = R;
# NFS servers usually decide to "squash" incoming requests from the
# root user to a "nobody" user. It's possible to disable that, but for
# now, we leave it enabled.
# Squash = root;
FSAL {
# FSAL_CEPH export
Name = CEPH;
#
# Ceph filesystems have a name string associated with them, and
# modern versions of libcephfs can mount them based on the
# name. The default is to mount the default filesystem in the
# cluster (usually the first one created).
#
# Filesystem = "cephfs_a";
#
# Ceph clusters have their own authentication scheme (cephx).
# Ganesha acts as a cephfs client. This is the client username
# to use. This user will need to be created before running
# ganesha.
#
# Typically ceph clients have a name like "client.foo". This
# setting should not contain the "client." prefix.
#
# See:
#
# http://docs.ceph.com/docs/jewel/rados/operations/user-management/
#
# The default is to set this to NULL, which means that the
# userid is set to the default in libcephfs (which is
# typically "admin").
#
# User_Id = "ganesha";
#
# Key to use for the session (if any). If not set, it uses the
# normal search path for cephx keyring files to find a key:
#
# Secret_Access_Key = "YOUR SECRET KEY HERE";
}
}
# Config block for FSAL_CEPH
CEPH
{
# Path to a ceph.conf file for this ceph cluster.
# Ceph_Conf = /etc/ceph/ceph.conf;
# User file-creation mask. These bits will be masked off from the unix
# permissions on newly-created inodes.
# umask = 0;
}
#
# This is the config block for the RADOS RecoveryBackend. This is only
# used if you're storing the client recovery records in a RADOS object.
#
RADOS_KV
{
# Path to a ceph.conf file for this cluster.
# Ceph_Conf = /etc/ceph/ceph.conf;
# The recoverybackend has its own ceph client. The default is to
# let libcephfs autogenerate the userid. Note that RADOS_KV block does
# not have a setting for Secret_Access_Key. A cephx keyring file must
# be used for authenticated access.
# UserId = "ganesharecov";
# Pool ID of the ceph storage pool that contains the recovery objects.
# The default is "nfs-ganesha".
# pool = "nfs-ganesha";
# Consider setting a unique nodeid for each running daemon here,
# particularly if this daemon could end up migrating to a host with
# a different hostname (i.e. if you're running an active/passive cluster
# with rados_ng/rados_kv and/or a scale-out rados_cluster). The default
# is to use the hostname of the node where ganesha is running.
# nodeid = hostname.example.com
}
# Config block for rados:// URL access. It too uses its own client to access
# the object, separate from the FSAL_CEPH and RADOS_KV client.
RADOS_URLS
{
# Path to a ceph.conf file for this cluster.
# Ceph_Conf = /etc/ceph/ceph.conf;
# RADOS_URLS use their own ceph client too. Authenticated access
# requires a cephx keyring file.
# UserId = "ganeshaurls";
# used if you're storing the client recovery records in a RADOS object.
#
RADOS_KV
{
# Path to a ceph.conf file for this cluster.
# Ceph_Conf = /etc/ceph/ceph.conf;
# The recoverybackend has its own ceph client. The default is to
# let libcephfs autogenerate the userid. Note that RADOS_KV block does
# not have a setting for Secret_Access_Key. A cephx keyring file must
# be used for authenticated access.
# UserId = "ganesharecov";
# Pool ID of the ceph storage pool that contains the recovery objects.
# The default is "nfs-ganesha".
# pool = "nfs-ganesha";
# Consider setting a unique nodeid for each running daemon here,
# particularly if this daemon could end up migrating to a host with
# a different hostname (i.e. if you're running an active/passive cluster
# with rados_ng/rados_kv and/or a scale-out rados_cluster). The default
# is to use the hostname of the node where ganesha is running.
# nodeid = hostname.example.com
}
# Config block for rados:// URL access. It too uses its own client to access
# the object, separate from the FSAL_CEPH and RADOS_KV client.
RADOS_URLS
{
# Path to a ceph.conf file for this cluster.
# Ceph_Conf = /etc/ceph/ceph.conf;
# RADOS_URLS use their own ceph client too. Authenticated access
# requires a cephx keyring file.
# UserId = "ganeshaurls";
# We can also have ganesha watch a RADOS object for notifications, and
# have it force a configuration reload when one comes in. Set this to
# a valid rados:// URL to enable this feature.
# watch_url = "rados://pool/namespace/object";
}
NFS_CORE_PARAM {
Allow_Set_Io_Flusher_Fail = true;
Protocols = 4;
}
EXPORT_DEFAULTS {
Access_Type = RW;
Attr_Expiration_Time = 0;
Squash = None;
}
EXPORT {
Export_Id = 1;
Path = "/";
Pseudo = "/cephfs";
Access_Type = RW;
Squash = None;
Protocols = 4;
Transports = TCP;
FSAL {
Name = "CEPH";
User_Id = "ganesha";
Filesystem = "cephfs";
Ceph_Conf = "/etc/ceph/ceph.conf";
}
CLIENT {
Clients = 10.X.X.0/24; # Replace with your network address
Access_Type = RW;
}
}
LOG {
Default_Log_Level = DEBUG;
Facility {
name = FILE;
destination = "/var/log/ganesha.log";
max_level = FULL_DEBUG;
enable = active;
}
}
acme.sh --issue -d mgw.mydom.com --dns --yes-I-know-dns-manual-mode-enough-go-ahead-please
ระบบจะบอกว่า ให้ท่านไปใส่ txt record เพื่อแสดงความเป็นเจ้าของโดเมนacme.sh --renew -d mgw.mydom.com --yes-I-know-dns-manual-mode-enough-go-ahead-please
5. ทำการสำรองpmg-api.pem ที่อยู่ใน folder /etc/pmg ก่อนด้วยคำสั่งmv pmg-api.pem pmg-api.pem.bak
6. หลังจาก เราจะได้ไฟล์ /root/.acme.sh/<domain>cat fullchain.cert mgw.mydom.com.key > /etc/pmg/pmg-api.pem
$sw = [System.Diagnostics.Stopwatch]::StartNew()
$fs = [System.IO.File]::Create("C:\test1.img")
$buffer = New-Object byte[] (1MB)
1..1024 | ForEach-Object {
$fs.Write($buffer, 0, $buffer.Length)
}
$fs.Flush($true)
$fs.Close()
$sw.Stop()
$speed = 1024 / $sw.Elapsed.TotalSeconds
"Elapsed: $($sw.Elapsed.TotalSeconds) sec"
"Write Speed: $([math]::Round($speed,2)) MB/s"
dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync
dd if=/tmp/test1.img of=/dev/null bs=1G iflag=direct
wget -o Updater.sh https://d111xps0uy3x00.cloudfront.net/res/product/NAKIVO%20Backup_Replication%20v11.2.1.104556%20Updater.exe
chmod +w ./Updater.sh
sudo Updater.sh