From cf804c4193b25bdb89dfb242935060acfdfa6c90 Mon Sep 17 00:00:00 2001
From: chai001125 <94744119+chai001125@users.noreply.github.com>
Date: Fri, 11 Nov 2022 21:50:35 +0800
Subject: [PATCH] translating

---
 ...07 Identify security properties on Linux using checksec.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sources/tech/20210607 Identify security properties on Linux using checksec.md b/sources/tech/20210607 Identify security properties on Linux using checksec.md
index 3d1e118830..e10996be18 100644
--- a/sources/tech/20210607 Identify security properties on Linux using checksec.md	
+++ b/sources/tech/20210607 Identify security properties on Linux using checksec.md	
@@ -2,7 +2,7 @@
 [#]: via: (https://opensource.com/article/21/6/linux-checksec)
 [#]: author: (Gaurav Kamathe https://opensource.com/users/gkamathe)
 [#]: collector: (lujun9972)
-[#]: translator: ( )
+[#]: translator: (chai001125)
 [#]: reviewer: ( )
 [#]: publisher: ( )
 [#]: url: ( )
@@ -435,4 +435,4 @@ The topic of security is never-ending, and while it's not possible to cover ever
 
 You don't have to provide each binary to checksec individually. Instead, you can provide a directory path where multiple binaries reside, and checksec will verify all of them for you in one go:
 ```
-`$ checksec --dir=/usr
\ No newline at end of file
+`$ checksec --dir=/usr