Rook使用简介

article/2025/9/23 11:30:35

Rook使用简介（Ceph）

1、简介

Rook是一个自管理的分布式存储编排系统，可以为Kubernetes提供便利的存储解决方案。Rook本身并不提供存储，而是在kubernetes和存储系统之间提供适配层，简化存储系统的部署与维护工作。目前，rook支持的存储系统包括：Ceph、CockroachDB、Cassandra、EdgeFS、Minio、NFS，其中Ceph为Stable状态，其余均为Alpha。本文仅介绍Ceph相关内容。

Rook由Operator和Cluster两部分组成：

  • Operator：由一些CRD和一个All in one镜像构成，包含包含启动和监控存储系统的所有功能。
  • Cluster：负责创建CRD对象，指定相关参数，包括ceph镜像、元数据持久化位置、磁盘位置、dashboard等等…

下图是Rook的体系结构图，Operator启动之后，首先创建Agent和Discover容器，负责监视和管理各个节点上存储资源。然后创建Cluster，Cluster是创建Operator时定义的CRD。Operator根据Cluster的配置信息启动Ceph的相关容器。存储集群启动之后，使用kubernetes元语创建PVC为应用容器所用。

Rook Components on Kubernetes

2、部署

2.1、环境说明

[root@master-0 ~]# kubectl get nodes -o wide
NAME       STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION          CONTAINER-RUNTIME
master-0   Ready    master   24m   v1.13.0   172.16.7.11   <none>        CentOS Linux 7 (Core)   3.10.0-862.el7.x86_64   docker://18.9.2
worker-0   Ready    worker   23m   v1.13.0   172.16.7.12   <none>        CentOS Linux 7 (Core)   3.10.0-862.el7.x86_64   docker://18.9.2
worker-1   Ready    worker   23m   v1.13.0   172.16.7.13   <none>        CentOS Linux 7 (Core)   3.10.0-862.el7.x86_64   docker://18.9.2[root@master-0 ~]# lsblk 
NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda               8:0    0   20G  0 disk 
├─sda1            8:1    0    1G  0 part /boot
└─sda2            8:2    0   19G  0 part ├─centos-root 253:0    0   17G  0 lvm  /└─centos-swap 253:1    0    2G  0 lvm  
sdb               8:16   0   20G  0 disk 
sr0              11:0    1 1024M  0 rom

每个节点两块磁盘，第二块sdb用来做ceph的数据盘

2.2、部署Operator

[root@master-0 ~]# kubectl apply -f https://raw.githubusercontent.com/rook/rook/master/cluster/examples/kubernetes/ceph/operator.yaml[root@master-0 ~]# kubectl get pods --all-namespaces 
NAMESPACE          NAME                                                   READY   STATUS    RESTARTS   AGE
<snip>
rook-ceph-system   rook-ceph-agent-4tf9h                                  1/1     Running     0          17m
rook-ceph-system   rook-ceph-agent-4zg9t                                  1/1     Running     0          17m
rook-ceph-system   rook-ceph-agent-r82n7                                  1/1     Running     0          17m
rook-ceph-system   rook-ceph-operator-b996864dd-zbn29                     1/1     Running     0          18m
rook-ceph-system   rook-discover-88zkc                                    1/1     Running     0          17m
rook-ceph-system   rook-discover-ffsns                                    1/1     Running     0          17m
rook-ceph-system   rook-discover-wt942                                    1/1     Running     0          17m[root@master-0 ~]# kubectl get ds --all-namespaces 
NAMESPACE          NAME                             DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                     AGE
<snip>
rook-ceph-system   rook-ceph-agent                  3         3         3       3            3           <none>                            17m
rook-ceph-system   rook-discover                    3         3         3       3            3           <none>                            17m

需要重点关注的是deployment:rook-ceph-operator，rook-ceph-operator启动之后会以DS启动Agent和Discover

2.3、部署Cluster

### 设置label，标记哪些节点用来部署哪些应用 ###
[root@master-0 ~]# kubectl label node master-0 role=storage-node
node/master-0 labeled
[root@master-0 ~]# kubectl label node worker-0 role=storage-node
node/worker-0 labeled
[root@master-0 ~]# kubectl label node worker-1 role=storage-node
node/worker-1 labeled
[root@master-0 ~]# kubectl get nodes -L role
NAME       STATUS   ROLES    AGE   VERSION   ROLE
master-0   Ready    master   26m   v1.13.0   storage-node
worker-0   Ready    worker   25m   v1.13.0   storage-node
worker-1   Ready    worker   25m   v1.13.0   storage-node

这里仅设置一个label，ceph的mon、ose、mgr都运行在这个label对应的节点上，当然也可以分别设置～

### cluster.yml ###
apiVersion: v1
kind: Namespace
metadata:name: rook-ceph
---
apiVersion: v1
kind: ServiceAccount
metadata:name: rook-ceph-osdnamespace: rook-ceph
---
apiVersion: v1
kind: ServiceAccount
metadata:name: rook-ceph-mgrnamespace: rook-ceph
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-osdnamespace: rook-ceph
rules:
- apiGroups: [""]resources: ["configmaps"]verbs: [ "get", "list", "watch", "create", "update", "delete" ]
---
# Aspects of ceph-mgr that require access to the system namespace
kind: Role
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-mgr-systemnamespace: rook-ceph
rules:
- apiGroups:- ""resources:- configmapsverbs:- get- list- watch
---
# Aspects of ceph-mgr that operate within the cluster's namespace
kind: Role
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-mgrnamespace: rook-ceph
rules:
- apiGroups:- ""resources:- pods- servicesverbs:- get- list- watch
- apiGroups:- batchresources:- jobsverbs:- get- list- watch- create- update- delete
- apiGroups:- ceph.rook.ioresources:- "*"verbs:- "*"
---
# Allow the operator to create resources in this cluster's namespace
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-cluster-mgmtnamespace: rook-ceph
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: rook-ceph-cluster-mgmt
subjects:
- kind: ServiceAccountname: rook-ceph-systemnamespace: rook-ceph-system
---
# Allow the osd pods in this namespace to work with configmaps
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-osdnamespace: rook-ceph
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: rook-ceph-osd
subjects:
- kind: ServiceAccountname: rook-ceph-osdnamespace: rook-ceph
---
# Allow the ceph mgr to access the cluster-specific resources necessary for the mgr modules
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-mgrnamespace: rook-ceph
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: rook-ceph-mgr
subjects:
- kind: ServiceAccountname: rook-ceph-mgrnamespace: rook-ceph
---
# Allow the ceph mgr to access the rook system resources necessary for the mgr modules
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-mgr-systemnamespace: rook-ceph-system
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: rook-ceph-mgr-system
subjects:
- kind: ServiceAccountname: rook-ceph-mgrnamespace: rook-ceph
---
# Allow the ceph mgr to access cluster-wide resources necessary for the mgr modules
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:name: rook-ceph-mgr-clusternamespace: rook-ceph
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: rook-ceph-mgr-cluster
subjects:
- kind: ServiceAccountname: rook-ceph-mgrnamespace: rook-ceph
---
apiVersion: ceph.rook.io/v1
kind: CephCluster
metadata:name: rook-cephnamespace: rook-ceph
spec:cephVersion:# The container image used to launch the Ceph daemon pods (mon, mgr, osd, mds, rgw).# v12 is luminous, v13 is mimic, and v14 is nautilus.# RECOMMENDATION: In production, use a specific version tag instead of the general v13 flag, which pulls the latest release and could result in different# versions running within the cluster. See tags available at https://hub.docker.com/r/ceph/ceph/tags/.image: 192.168.101.88:5000/ceph/ceph:v13.1 # Whether to allow unsupported versions of Ceph. Currently only luminous and mimic are supported.# After nautilus is released, Rook will be updated to support nautilus.# Do not set to true in production.allowUnsupported: false# The path on the host where configuration files will be persisted. If not specified, a kubernetes emptyDir will be created (not recommended).# Important: if you reinstall the cluster, make sure you delete this directory from each host or else the mons will fail to start on the new cluster.# In Minikube, the '/data' directory is configured to persist across reboots. Use "/data/rook" in Minikube environment.dataDirHostPath: /var/lib/rook# set the amount of mons to be startedmon:count: 3allowMultiplePerNode: true# enable the ceph dashboard for viewing cluster statusdashboard:enabled: true# serve the dashboard under a subpath (useful when you are accessing the dashboard via a reverse proxy)# urlPrefix: /ceph-dashboard# serve the dashboard at the given port.# port: 8443# serve the dashboard using SSL# ssl: truenetwork:# toggle to use hostNetworkhostNetwork: falserbdMirroring:# The number of daemons that will perform the rbd mirroring.# rbd mirroring must be configured with "rbd mirror" from the rook toolbox.workers: 0# To control where various services will be scheduled by kubernetes, use the placement configuration sections below.# The example under 'all' would have all services scheduled on kubernetes nodes labeled with 'role=storage-node' and# tolerate taints with a key of 'storage-node'.placement:all:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:- matchExpressions:- key: roleoperator: Invalues:- storage-node
#      podAffinity:
#      podAntiAffinity:tolerations:- key: node-role.kubernetes.io/masteroperator: Existseffect: NoSchedule
# The above placement information can also be specified for mon, osd, and mgr components
#    mon:
#    osd:
#    mgr:resources:
# The requests and limits set here, allow the mgr pod to use half of one CPU core and 1 gigabyte of memory
#    mgr:
#      limits:
#        cpu: "500m"
#        memory: "1024Mi"
#      requests:
#        cpu: "500m"
#        memory: "1024Mi"
# The above example requests/limits can also be added to the mon and osd components
#    mon:
#    osd:storage: # cluster level storage configuration and selectionuseAllNodes: falseuseAllDevices: falsedeviceFilter:location:config:# The default and recommended storeType is dynamically set to bluestore for devices and filestore for directories.# Set the storeType explicitly only if it is required not to use the default.# storeType: bluestoredatabaseSizeMB: "1024" # this value can be removed for environments with normal sized disks (100 GB or larger)# journalSizeMB: "1024"  # this value can be removed for environments with normal sized disks (20 GB or larger)osdsPerDevice: "1" # this value can be overridden at the node or device level
# Cluster level list of directories to use for storage. These values will be set for all nodes that have no `directories` set.
#    directories:
#    - path: /rook/storage-dir
# Individual nodes and their config can be specified as well, but 'useAllNodes' above must be set to false. Then, only the named
# nodes below will be used as storage resources.  Each node's 'name' field should match their 'kubernetes.io/hostname' label.nodes:- name: "master-0"devices:- name: "sdb"- name: "worker-0"devices:- name: "sdb"- name: "worker-1"devices:- name: "sdb"
#    - name: "172.17.4.101"
#      directories: # specific directories to use for storage can be specified for each node
#      - path: "/rook/storage-dir"
#      resources:
#        limits:
#          cpu: "500m"
#          memory: "1024Mi"
#        requests:
#          cpu: "500m"
#          memory: "1024Mi"
#    - name: "172.17.4.201"
#      devices: # specific devices to use for storage can be specified for each node
#      - name: "sdb"
#      - name: "nvme01" # multiple osds can be created on high performance devices
#        config:
#          osdsPerDevice: "5"
#      config: # configuration can be specified at the node level which overrides the cluster level config
#        storeType: filestore
#    - name: "172.17.4.301"
#      deviceFilter: "^sd."

CephCluster中需要重点注意啊的几个地方：

  • spec.dataDirHostPath：存放rook元数据，确保在服务器重启后能正常运行，重新部署时 需要手动删除遗留文件
  • spec.storage.useAllNodes：是否根据配置将所有节点用于存储，如果指定了nodes，该值必须设置为false
  • spec.storage.config：根据实际磁盘大小，可以删除config下的某些配置
  • spec.storage.nodes：分别设置各个节点的存储路径，可以说磁盘或者目录
[root@master-0 ~]# kubectl apply -f cluster.yml 
namespace/rook-ceph created
serviceaccount/rook-ceph-osd created
serviceaccount/rook-ceph-mgr created
role.rbac.authorization.k8s.io/rook-ceph-osd created
clusterrole.rbac.authorization.k8s.io/rook-ceph-mgr-system created
role.rbac.authorization.k8s.io/rook-ceph-mgr created
rolebinding.rbac.authorization.k8s.io/rook-ceph-cluster-mgmt created
rolebinding.rbac.authorization.k8s.io/rook-ceph-osd created
rolebinding.rbac.authorization.k8s.io/rook-ceph-mgr created
rolebinding.rbac.authorization.k8s.io/rook-ceph-mgr-system created
clusterrolebinding.rbac.authorization.k8s.io/rook-ceph-mgr-cluster created
cephcluster.ceph.rook.io/rook-ceph created[root@master-0 ~]# kubectl get pods --all-namespaces 
<snip>
rook-ceph-system   rook-ceph-agent-4tf9h                                  1/1     Running     0          19m
rook-ceph-system   rook-ceph-agent-4zg9t                                  1/1     Running     0          19m
rook-ceph-system   rook-ceph-agent-r82n7                                  1/1     Running     0          19m
rook-ceph-system   rook-ceph-operator-b996864dd-zbn29                     1/1     Running     0          20m
rook-ceph-system   rook-discover-88zkc                                    1/1     Running     0          19m
rook-ceph-system   rook-discover-ffsns                                    1/1     Running     0          19m
rook-ceph-system   rook-discover-wt942                                    1/1     Running     0          19m
rook-ceph          rook-ceph-mgr-a-7b9667498-j4bdx                        1/1     Running     0          16m
rook-ceph          rook-ceph-mon-a-749779c884-bqm9b                       1/1     Running     0          17m
rook-ceph          rook-ceph-mon-b-b97f6cbdb-hmrln                        1/1     Running     0          17m
rook-ceph          rook-ceph-mon-c-67d7dcc89f-pcjpn                       1/1     Running     0          16m
rook-ceph          rook-ceph-osd-0-86dff67f75-mvjkc                       1/1     Running     0          15m
rook-ceph          rook-ceph-osd-1-6cdd46dcdc-p62zq                       1/1     Running     0          15m
rook-ceph          rook-ceph-osd-2-c7b97f7bf-65r6d                        1/1     Running     0          15m
rook-ceph          rook-ceph-osd-prepare-master-0-vvp6c                   0/2     Completed   0          16m
rook-ceph          rook-ceph-osd-prepare-worker-0-spfbn                   0/2     Completed   0          16m
rook-ceph          rook-ceph-osd-prepare-worker-1-blmsz                   0/2     Completed   0          16m

这一步如果有问题，可以查看operator的日志～

### rook会自动将磁盘分区 ###
[root@master-0 ~]# lsblk 
NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda               8:0    0   20G  0 disk 
├─sda1            8:1    0    1G  0 part /boot
└─sda2            8:2    0   19G  0 part ├─centos-root 253:0    0   17G  0 lvm  /└─centos-swap 253:1    0    2G  0 lvm  
sdb               8:16   0   20G  0 disk 
├─sdb1            8:17   0  576M  0 part 
├─sdb2            8:18   0    1G  0 part 
└─sdb3            8:19   0 18.4G  0 part 
sr0              11:0    1 1024M  0 rom
  • 给rook使用的sdb实现不要自己分区，rook会自行分区
  • 从事例配置来看，除了device外，rook还可以配置directory做存储，这里就先不尝试了～

3、测试

3.1、访问dashboard

[root@master-0 ~]# kubectl get svc --all-namespaces
NAMESPACE       NAME                                     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
<snip>
rook-ceph       rook-ceph-mgr                            ClusterIP   10.100.35.42     <none>        9283/TCP         19m
rook-ceph       rook-ceph-mgr-dashboard                  NodePort    10.109.82.52     <none>        8443/TCP   19m
rook-ceph       rook-ceph-mon-a                          ClusterIP   10.107.76.183    <none>        6789/TCP         20m
rook-ceph       rook-ceph-mon-b                          ClusterIP   10.99.3.203      <none>        6789/TCP         20m
rook-ceph       rook-ceph-mon-c                          ClusterIP   10.97.73.46      <none>        6789/TCP         19m
### 修改dashboard的访问方式为NodePort ###
[root@master-0 ~]# kubectl edit svc -n rook-ceph rook-ceph-mgr-dashboard
[root@master-0 ~]# kubectl get svc -n rook-ceph rook-ceph-mgr-dashboard
NAME                      TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
rook-ceph-mgr-dashboard   NodePort   10.109.82.52   <none>        8443:30372/TCP   20m### 获得dashboard的登录密码，用户为admin ###
[root@master-0 ~]# kubectl get secrets -n rook-ceph rook-ceph-dashboard-password -o jsonpath='{.data.password}' | base64 -d
eXnScTg7nm

浏览器登录：https://172.16.7.11:30372

image-20190327140236331

image-20190327140304407

3.2、创建CephBlockPool和StorageClass

### 块存 ###
apiVersion: ceph.rook.io/v1
kind: CephBlockPool
metadata:name: replicapoolnamespace: rook-ceph
spec:failureDomain: hostreplicated:size: 3### sc ###
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:name: rook-ceph-block
provisioner: ceph.rook.io/block
parameters:blockPool: replicapool# The value of "clusterNamespace" MUST be the same as the one in which your rook cluster existclusterNamespace: rook-ceph# Specify the filesystem type of the volume. If not specified, it will use `ext4`.fstype: xfs
# Optional, default reclaimPolicy is "Delete". Other options are: "Retain", "Recycle" as documented in https://kubernetes.io/docs/concepts/storage/storage-classes/
reclaimPolicy: Retain

### 使用busybox测试 ###
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:name: ceph-block-volume
spec:accessModes:- ReadWriteOnceresources:requests:storage: 1GistorageClassName: rook-ceph-block
---
apiVersion: apps/v1
kind: Deployment
metadata:labels:app: busyboxname: busybox
spec:replicas: 1selector:matchLabels:app: busyboxtemplate:metadata:labels:app: busyboxspec:containers:- name: busyboximage: busyboxcommand: ["sh", "-c", "sleep 3600"]volumeMounts:- name: volumemountPath: /volumevolumes:- name: volumepersistentVolumeClaim:claimName: ceph-block-volume

[root@master-0 ~]# kubectl get pvc
NAME                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
ceph-block-volume   Bound    pvc-066408f1-5059-11e9-95ad-005056260373   1Gi        RWO            rook-ceph-block   23s
[root@master-0 ~]# kubectl get pods
NAME                      READY   STATUS    RESTARTS   AGE
busybox-578db44c4-vwszl   1/1     Running   0          25s
[root@master-0 ~]# kubectl exec -ti busybox-578db44c4-vwszl sh
/ # df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  17.0G      4.3G     12.6G  26% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                     1.8G         0      1.8G   0% /sys/fs/cgroup
/dev/rbd0              1014.0M     32.3M    981.7M   3% /volume
<snip>

3.3、文件存储和对象存储

文件存储和对象存储和上面类型，先创建CRD对象，然后使用。但是文件系统目前还不支持使用StorageClass，当使用RWX时，不太好用，后面考虑使用 ganesha 导出NFS服务实现RWX功能。

4、参考

https://rook.io/docs/rook/v0.9/


http://chatgpt.dhexx.cn/article/a1NFKyWN.shtml

相关文章

手机通过magisk获取root权限

手机通过magisk获取root权限

仅做参考&#xff0c;方便自己使用的操作。我是看这篇文章 来进行操作的。 前提 1.手机用的是twrp这个recovery&#xff0c;这个是大前提。 2.默认会配置adb环境和命令使用。 我之前是在这个地方下载的twrp&#xff0c;根据Devices找到对应自己手机的Primary (Americas)的.…
阅读更多...
一个基于 LKM 的 Linux 内核级 rootkit 的实现

一个基于 LKM 的 Linux 内核级 rootkit 的实现

博客已迁移至&#xff1a;https://gls.show/ GitHub链接 演示Slides overview rootkit是一种恶意软件&#xff0c;攻击者可以在获得 root 或管理员权限后安装它&#xff0c;从而隐藏入侵并保持root权限访问。rootkit可以是用户级的&#xff0c;也可以是内核级的。关于rootk…
阅读更多...
Rootkit 后门的利用 --超详细

Rootkit 后门的利用 --超详细

1.通过本地 PC 中渗透测试平台 Kali 对服务器场景进行系统服务及版本扫描 11 / 25 渗透测试;并将该操作显 示结果中 SSH 服务版本信息字符串作为 FLAG 提交&#xff1b; nmap -sV ip 即可扫描出ssh的服务版本信息 2.通过本地 PC 中渗透测试平台 Kali 对服务器场景进行 SSH 暴力…
阅读更多...
Rootkit---进程隐藏

Rootkit---进程隐藏

测试环境&#xff1a; Ubuntu18.04 内核版本&#xff1a;4.15.0 有的内核版本函数不一定都相同&#xff0c;有的修改的程度比较大&#xff0c;需要下载内核源码去看。 Linux内核源码&#xff1a;https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ 使用strace ps命令查…
阅读更多...
Linux Rootkit系列三：实例详解 Rootkit 必备的基本功能

Linux Rootkit系列三：实例详解 Rootkit 必备的基本功能

前言 鉴于笔者知识能力上的不足&#xff0c;如有疏忽&#xff0c;欢迎纠正。 本文所需的完整代码位于笔者的代码仓库&#xff1a;https://github.com/NoviceLive/research-rootkit。 测试建议&#xff1a; 不要在物理机测试&#xff01;不要在物理机测试&#xff01; 不要在物…
阅读更多...
Rootkit演变

Rootkit演变

Rootkit 概述 我第一次接触rootkit是在2004年&#xff0c;当时我还是一个rookie病毒分析师&#xff0c;具备一定的关于UNIX的 rootkit病毒的相关知识。有一天我无意中发现windows系统中的一个可执行程序&#xff0c;在我登录这个程序的时候&#xff0c;windows系统似乎没有做出…
阅读更多...
Rootkit 后门的利用

Rootkit 后门的利用

Ev:Rootkit后门的利用-网络安全文档类资源-CSDN下载 1.通过本地 PC 中渗透测试平台 Kali 对服务器场景进行系统服务及版本扫描 渗透测试&#xff0c;并将该操作显示结果中 SSH 服务版本信息字符串作为 FLAG 提交&#xff1b; 2.通过本地 PC 中渗透测试平台 Kali 对服务器场景…
阅读更多...
Rootkit检测技术发展现状

Rootkit检测技术发展现状

Rootkit 这一概念最早出现于上个世纪九十年代初期&#xff0c;CERT Coordination Center(CERT/CC) 于1994年在 CA-1994-01 这篇安全咨询报告中使用了 Rootkit 这个词汇。在这之后 Rootkit 技术发展迅速&#xff0c;这种快速发展的态势在 2000 年达到了顶峰。2000年后&#xff0…
阅读更多...
rkhunter（Rootkit猎手）安装使用

rkhunter（Rootkit猎手）安装使用

一、rkhunter简介&#xff1a; 1、中文名叫”Rootkit猎手”, rkhunter是Linux系统平台下的一款开源入侵检测工具&#xff0c;具有非常全面的扫描范围&#xff0c;除了能够检测各种已知的rootkit特征码以外&#xff0c;还支持端口扫描、常用程序文件的变动情况检查。 2、root…
阅读更多...
rootkit技术

rootkit技术

rootkit的主要分类&#xff1a; 应用级->内核级->硬件级 早期的rootkit主要为应用级rootkit&#xff0c;应用级rootkit主要通过替换login、ps、ls、netstat等系统工具&#xff0c;或修改.rhosts等系统配置文件等实现隐藏及后门&#xff1b;硬件级rootkit主要指bios roo…
阅读更多...
rootkit概述

rootkit概述

这个是摘自微信公众号里面的文章&#xff1b; rootkit是一个复合词&#xff0c;由root和kit两个词组成。root是用来描述具有计算机最高权限的用户。另一方面&#xff0c;kit被Merrian-Webster定义为工具和实现的集合。因此&#xff0c;rootkit是一组能获得计算机系统root或者管…
阅读更多...
什么是 Rootkit？

什么是 Rootkit？

Rootkit定义 常见的rootkit定义是一种恶意软件程序&#xff0c;它使网络犯罪分子能够在不被检测到的情况下访问和渗透计算机中的数据。 它涵盖了旨在感染计算机&#xff0c;为攻击者提供远程控制并长时间保持隐藏的软件工具箱。因此&#xff0c;Rootkit是最难发现和删除的恶意…
阅读更多...
Java-GUI快速入门

Java-GUI快速入门

目录 1.GUI的介绍 1.1GUI概述 1.2Java提供了三个主要包做GUI开发&#xff1a; 2.Swing组件 2.1顶层容器介绍 2.2中间容器 2.3基本组件 3.API介绍 3.1Jframe组件 3.2Panel组件 3.3功能组件 4.案例代码 4.1UI介绍 4.2代码 5.插件介绍WindowBuilder 5.1搜索Window…
阅读更多...
Python GUI 开发工具

Python GUI 开发工具

Python Tkinter教程&#xff08;GUI图形界面开发教程&#xff09;&#xff1a;http://c.biancheng.net/python/tkinter/ PyQt5教程&#xff1a;http://code.py40.com/face 作为 Pyhon 开发者&#xff0c;我们迟早都会碰到 图形用户界面&#xff08;GUI&#xff09;应用 开发任…
阅读更多...
GUI基础知识

GUI基础知识

GUI编程 1&#xff0c;简介 图形用户界面,Graphical User Interface,又称图形用户接口&#xff0c;是指采用图形方式显示的计算机操作用户界面。GUI的核心技术&#xff1a;AWT,Swing 2&#xff0c;Awt 2.1 AWT简介 AWT:Abstract Window Toolkit,抽象窗口工具包&#xff0c…
阅读更多...
Java——GUI编程

Java——GUI编程

GUI编程 1、简介2、AWT&#xff08;抽象的窗口工具&#xff09;AWT简介1、Frame的使用&#xff1a;2、面板 panel3、布局管理器3.1 流式布局3.2 东西南北中3.3 表格布局 4、事件监听5、文本框&#xff08;TextField&#xff09;的监听6、制作简易计算器7、画笔8、鼠标监听9、窗…
阅读更多...
GUI编程详解

GUI编程详解

1.简介 GUI的核心技术&#xff1a;Swing AWT GUI缺点&#xff1a; 1. 界面不美观2. 需要jre环境为什么要学习GUI&#xff1f; 可以写出自己想要的工具。实际工作中可能需要维护swing界面了解MVC和监听。 2.AWT 2.1相关知识 介绍&#xff1a; 包含了很多类和接口。用于图形…
阅读更多...
python GUI入门（一入门介绍）

python GUI入门（一入门介绍）

CUI: 命令行界面&#xff0c;conmmand line user Interface GUI: Graphical User Interface 1、python常用的主要跨平台图形用户界面库 1.1 Tkinter python自带的GUT库&#xff0c;“官方支持”&#xff0c;无须进行额外的下载安装&#xff0c;只要导入tkinter包即可使用。 …
阅读更多...
GUI系统

GUI系统

1.gui概念 2.OSD实现 1.概念 OSD是on-screen display的简称&#xff0c;即屏幕菜单式调节方式。一般是按Menu键后屏幕弹出的显示器各项调节项目信息的矩形菜单&#xff0c;可通过该菜单对显示器各项工作指标包括色彩、模式、几何形状等进行调整&#xff0c;从而达到最佳的使用…
阅读更多...
Python之GUI编程

Python之GUI编程

一、常用的GUI库 Tkinter&#xff1a;tkinter&#xff08;Tk interface&#xff09;是Python的标准GUI库&#xff0c;支持跨平台的GUI程序开发&#xff0c;tkinter适合小型的GUI程序编写&#xff0c;也特别适合初学者学习GUI编程。wxPython&#xff1a;wxPython是比较流行的GU…
阅读更多...
推荐文章

Copyright @ 2022~2023