Crypto Wrapper issueshttps://gitlab.nic.cz/turris/crypto-wrapper/-/issues2020-10-26T18:11:29+01:00https://gitlab.nic.cz/turris/crypto-wrapper/-/issues/6Use os-release file to determine device type2020-10-26T18:11:29+01:00Vojtech MyslivecUse os-release file to determine device type`OPENWRT_DEVICE_PRODUCT` variable in `/etc/os-release` should be used to determine device type`OPENWRT_DEVICE_PRODUCT` variable in `/etc/os-release` should be used to determine device typehttps://gitlab.nic.cz/turris/crypto-wrapper/-/issues/5Secure handling tmp files2021-11-13T01:07:10+01:00Vojtech MyslivecSecure handling tmp filesCheck and prevent other users to mangle directory structure within `/tmp`. I.e. detect wrong user ownership of crypto-wrapper *root* directory and check for symlink redirection.Check and prevent other users to mangle directory structure within `/tmp`. I.e. detect wrong user ownership of crypto-wrapper *root* directory and check for symlink redirection.https://gitlab.nic.cz/turris/crypto-wrapper/-/issues/4Limit RAM usage2022-01-19T14:23:48+01:00Vojtech MyslivecLimit RAM usageAs `crypto-wrapper` stores its cache in `/tmp`, it can consume a lot of RAM if one will use `crypto-wrapper` very often.
Limit RAM usage to some reasonable value (3 % of total RAM or so). Old cache files could be deleted when a new one ...As `crypto-wrapper` stores its cache in `/tmp`, it can consume a lot of RAM if one will use `crypto-wrapper` very often.
Limit RAM usage to some reasonable value (3 % of total RAM or so). Old cache files could be deleted when a new one is to be created.