-
Recent Posts
Recent Comments
Archives
Categories
Meta
Author Archives: Alvin
POSIX permission mapping to Windows DACL(2)
上篇是通过修改文件的安全信息来实现。那么首先一个坑就是，如果文件本身没有写权限，麻烦就大了。虽然可以通过修改DCAL权限得到写权限，根据“代码多就是bug多”的原则，很容易夜长梦多，节外生枝。所以要在创建文件时直接指定权限。
总的过程：先喘一口气，然后根据sid和对应的权限创建Explicit[……]
Posted in tittle tattle
2 Comments
POSIX permission mapping to Windows DACL
在我接触Windows之前，对Windows的文件权限是不屑一顾。要用的时候才发现，Windows文件权限的组合远多于POSIX的rwx。这个坑花了三四天的时间。一句话总结：Windows虽然有更多的组合，但是不能实现全部的rwx组合。
首先是权限本身的转换，这里有个自认为完美的实现，只用一个[……]
Posted in tittle tattle
Leave a comment
-ffunction-sections -fdata-sections -Wl, –gc-sections编译选项
https://gcc.gnu.org/onlinedocs/gcc-7.5.0/gnat_ugn/Compilation-options.html
实际上gcc和clang均可支持。当使用-ffunction-sections -fdata-sections这两个参数编译，并且在链接时使用-[……]
Posted in tittle tattle
Leave a comment
package command
查询文件属于哪个包：
|
1 2 3 |
alvin@chen:~/openenclave/build$ dpkg -S /usr/lib/x86_64-linux-gnu/libsgx_enclave_common.so.1 libsgx-enclave-common: /usr/lib/x86_64-linux-gnu/libsgx_enclave_common.so.1 alvin@chen:~/openenclave/build$ |
|
1 2 3 |
[alvin@wechen3-rhel8-4 ~]$ rpm -qf /usr/lib/debug/usr/lib64/libsgx_dcap_ql.so.1.6.100.2-1.6.100.2-1.el8.x86_64.debug libsgx-dcap-ql-debuginfo-1.6.100.2-1.el8.x86_64 [alvin@wechen3-rhel8-4 ~]$ |
查询包的基本信息：
|
1 2 3 4 5 6 7 8 |
alvin@chen:~/openenclave/build$ dpkg -l libsgx-enclave-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-======================-================-================-================================================== ii libsgx-enclave-common 2.8.100.3-bionic amd64 Intel(R) Software Guard Extensions Enclave Common alvin@chen:~/openenclave/build$ |
[crayon-67ef580f559d09304[……]
Posted in tittle tattle
Leave a comment
ninja: error: manifest ‘build.ninja’ still dirty after 100 tries
网上有很多例子是基于ninja的bug。排除ninja的问题后还有错误：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
C:\open-enclave.0.8.1\openenclave\share\openenclave\samples\switchless\build>ninja ...... VERBOSE-- Looking for sgx_enclave_common library - found VERBOSE-- Looking for sgx_dcap_ql library - found -- Configuring done -- Generating done -- Build files have been written to: C:/open-enclave.0.8.1/openenclave/share/openenclave/samples/switchless/build VERBOSE-- Looking for sgx_enclave_common library - found VERBOSE-- Looking for sgx_dcap_ql library - found -- Configuring done -- Generating done -- Build files have been written to: C:/open-enclave.0.8.1/openenclave/share/openenclave/samples/switchless/build ninja: error: manifest 'build.ninja' still dirty after 100 tries C:\open-enclave.0.8.1\openenclave\share\openenclave\samples\switchless\build> |
带上explain参数能显示具体的错误：
|
1 2 3 4 5 6 7 8 9 10 11 |
C:\open-enclave.0.8.1\openenclave\share\openenclave\samples\switchless\build>ninja -d explain ninja explain: output build.ninja older than most recent input ../CMakeLists.txt (603082958 vs 603092436) VERBOSE-- Looking for sgx_enclave_common library - found VERBOSE-- Looking for sgx_dcap_ql library - found -- Configuring done -- Generating done -- Build files have been written to: C:/open-enclave.0.8.1/openenclave/share/openenclave/samples/switchless/build ninja explain: output build.ninja older than most recent input ../CMakeLists.txt (603082963 vs 603092436) ...... C:\open-enclave.0.8.1\openenclave\share\openenclave\samples\switchless\build> |
查看一下文件时间，Modify time还在[……]
Posted in tittle tattle
Leave a comment
warning C4090: ‘function’: different ‘const’ qualifiers
代码如下：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
const char* enclave_path = argv[1]; const char* tmp_dir = argv[2]; r = oe_create_test_hostfs_enclave( enclave_path, type, flags, NULL, 0, &enclave); OE_TEST(r == OE_OK); #if defined(_WIN32) tmp_dir = oe_win_path_to_posix(tmp_dir); #endif r = test_hostfs(enclave, tmp_dir); OE_TEST(r == OE_OK); r = oe_terminate_enclave(enclave); OE_TEST(r == OE_OK); printf("=== passed all tests (test_hostfs)\n"); #if defined(_WIN32) free(tmp_dir); #endif |
错误如下：
|
1 2 3 4 5 6 7 8 9 |
[build] Starting build [proc] Executing command: "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" --build c:/Users/alvin/openenclave/build --config Debug --target all -- -j 6 [build] [1/2 50% :: 0.063] Building C object tests\syscall\hostfs\host\CMakeFiles\hostfs_host.dir\host.c.obj [build] FAILED: tests/syscall/hostfs/host/CMakeFiles/hostfs_host.dir/host.c.obj [build] C:\PROGRA~2\MICROS~1\2017\BUILDT~1\VC\Tools\MSVC\1416~1.270\bin\Hostx64\x64\cl.exe /nologo -DOE_API_VERSION=2 -DOE_LINK_SGX_DCAP_QL -Itests\syscall\hostfs\host -I..\include -I"C:\oe_prereqs\EnclaveCommonAPI\Header Files" -I"C:\oe_prereqs\DCAP_Components\build\Header Files" /DWIN32 /D_WINDOWS /wd4566 /wd4200 /MDd /Zi /Ob0 /Od /RTC1 /WX /W2 /showIncludes /Fotests\syscall\hostfs\host\CMakeFiles\hostfs_host.dir\host.c.obj /Fdtests\syscall\hostfs\host\CMakeFiles\hostfs_host.dir\ /FS -c ..\tests\syscall\hostfs\host\host.c [build] ..\tests\syscall\hostfs\host\host.c(41): error C2220: warning treated as error - no 'object' file generated [build] ..\tests\syscall\hostfs\host\host.c(41): warning C4090: 'function': different 'const' qualifiers [build] ninja: build stopped: subcommand failed. [build] Build finished with exit code 1 |
有人已经贴了解决方案了，https://stackoverflow.com/questions/2819535/unable-to-fr[……]
Posted in tittle tattle
Leave a comment
error C2017: illegal escape sequence
用vs2017编译时一直报错：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
[build] ..\host\windows\syscall.c(548): error C2017: illegal escape sequence [build] ..\host\windows\syscall.c(552): error C2017: illegal escape sequence [build] ..\host\windows\syscall.c(563): error C2017: illegal escape sequence [build] ..\host\windows\syscall.c(567): error C2017: illegal escape sequence [build] ..\host\windows\syscall.c(588): error C2017: illegal escape sequence [build] ..\host\windows\syscall.c(591): error C2017: illegal escape sequence [build] ..\host\windows\syscall.c(595): error C2017: illegal escape sequence [build] [21/1662 1% :: 1.162] Building C object enclave\core\CMakeFiles\oecore.dir\sgx\thread.c.obj [build] [21/1662 1% :: 1.177] Building C object enclave\core\CMakeFiles\oecore.dir\sgx\getkey.S.obj [build] [21/1662 1% :: 1.287] Building C object enclave\core\CMakeFiles\oecore.dir\sgx\tracee.c.obj [build] [21/1662 1% :: 1.321] Building C object enclave\core\CMakeFiles\oecore.dir\sgx\td_basic.c.obj [build] [21/1662 1% :: 1.344] Creating directories for 'libcxx_includes' [build] ninja: build stopped: subcommand failed. [build] Build finished with exit code 1 |
原来是因为宏定义时转义符后面多了个空格：
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
alvin@chen ~/openenclave/host/windows$ cat -A syscall.c | head -n 27 // Copyright (c) Open Enclave SDK contributors.$ // Licensed under the MIT License.$ $ /*$ **==============================================================================$ **$ ** windows/syscall.c:$ **$ ** This file implements SYSCALL OCALLs for Windows. Most of these are stubs$ ** which are still under development.$ **$ **==============================================================================$ */$ #define _WINSOCK_DEPRECATED_NO_WARNINGS$ $ #define CHECK(exe) \ $ do \$ { \$ int retval = (exe); \$ if (retval != 0) \$ { \$ fprintf(stderr, "Runtime error: %x \nAt %s:%d", \$ GetLastError(), __FILE__, __LINE__); \$ return NULL; \$ } \$ } while (0)$ |
这么隐蔽的问题，显然是隐患。
在.vimrc中添加高亮：
[crayon-67[……]
Posted in tittle tattle
Leave a comment
vi相关
列模式下插入：Ctrl + i
列模式下替换：选中列后按c
保存到只读文件：:w !sudo tee %
删除行尾空格：用替换实现，%s/\s\+$//g
同样的思路，删除空行或者只含有空格的行：%s/^\s\*$//g
匹配printf但不匹配定制的printf(此处[……]
Posted in tittle tattle
Leave a comment
ipdb修改代码显示行数
以为ipdb能够和gdb一样用tui方式运行，结果还是有点遗憾。
补救办法是可以将默认的3行改大。
|
1 2 3 |
alvin@chen:~/python$ python -c 'import ipdb; print(ipdb)' <module 'ipdb' from '/usr/local/lib/python3.6/dist-packages/ipdb/__init__.py'> alvin@chen:~/python$ |
此时可以找到相应的__main__.py为/usr/local/lib/python3.6/dist-packages/ip[……]
Posted in tittle tattle
Leave a comment
git相关
工作区：当前路径下ls或cat能够看到的目录及文件。
暂存区：工作区的历史快照的合集，每次add操作是此合集的一部分。对同一个文件多次add并不是冲突，因为这是同一个作者的修改，以时间为序，最终状态为结果。
如果是多个作者对同一个文件的相同位置（直观说是行数）进行修改，那么就产生了无法直[……]
Posted in tittle tattle
Leave a comment