晋太元中,武陵人捕鱼为业。缘溪行,忘路之远近。忽逢桃花林,夹岸数百步,中无杂树,芳草鲜美,落英缤纷。渔人甚异之,复前行,欲穷其林。 林尽水源,便得一山,山有小口,仿佛若有光。便舍船,从口入。初极狭,才通人。复行数十步,豁然开朗。土地平旷,屋舍俨然,有良田、美池、桑竹之属。阡陌交通,鸡犬相闻。其中往来种作,男女衣着,悉如外人。黄发垂髫,并怡然自乐。 见渔人,乃大惊,问所从来。具答之。便要还家,设酒杀鸡作食。村中闻有此人,咸来问讯。自云先世避秦时乱,率妻子邑人来此绝境,不复出焉,遂与外人间隔。问今是何世,乃不知有汉,无论魏晋。此人一一为具言所闻,皆叹惋。余人各复延至其家,皆出酒食。停数日,辞去。此中人语云:“不足为外人道也。”(间隔 一作:隔绝) 既出,得其船,便扶向路,处处志之。及郡下,诣太守,说如此。太守即遣人随其往,寻向所志,遂迷,不复得路。 南阳刘子骥,高尚士也,闻之,欣然规往。未果,寻病终。后遂无问津者。
|
Server : Apache System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64 User : rainic ( 1014) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system Directory : /usr/share/doc/gnupg2/ |
Upload File : |
-*- outline -*- * src/base64 ** Make parsing more robust Currently we don't cope with overlong lines in the best way. ** Check that we really release the ksba reader/writer objects. * sm/call-agent.c ** Some code should go into import.c ** When we allow concurrent service request in gpgsm, we might want to have an agent context for each service request (i.e. Assuan context). * sm/certchain.c ** Try to keep certificate references somewhere This will help with some of our caching code. We also need to test that caching; in particular "regtp_ca_chainlen". * sm/decrypt.c ** replace leading zero in integer hack by a cleaner solution * sm/gpgsm.c ** Implement --default-key ** support the anyPolicy semantic ** Should we prefer nonRepudiation certs over plain signing certs? Also: Do we need a way to allow the selection of a qualSig cert over a plain one? The background is that the Telesec cards have 3 certs capable of signing all with the same subject name. * sm/keydb.c ** Check file permissions ** Check that all error code mapping is done. ** Remove the inter-module dependencies between gpgsm and keybox ** Add an source_of_key field * agent/ ** If we detect that a private key has been deleted Bump the key event counter. * agent/command.c ** Make sure that secure memory is used where appropriate * agent/pkdecrypt.c, agent/pksign.c ** Support DSA * Move pkcs-1 encoding into libgcrypt. * Use a MAC to protect sensitive files. The problem here is that we need yet another key and it is unlikely that users are willing to remember that key too. It is possible to do this with a smartcard, though. * sm/export.c ** Return an error code or a status info per user ID. * common/tlv.c The parse_sexp function should not go into this file. Check whether we can change all S-expression handling code to make use of this function. * scd ** Application context vs. reader slot We have 2 concurrent method of tracking whether a reader is in use: Using the session_list in command.c and the lock_table in app.c. It would be better to do this just at one place. First we need to see how we can support cards with multiple applications. ** Resolve fixme in do_sign of app-dinsig. ** Disconnect Card timeout is currently used as a boolean. Add disconnect support for the ccid driver. * Regression tests ** Add a regression test to check the extkeyusage. * Windows port (W32) ** Regex support is disabled We need to adjust the test to find the regex we have anyway in gpg4win. Is that regex compatible to the OpenPGP requirement? * sm/ ** check that we issue NO_SECKEY xxx if a -u key was not found We don't. The messages returned are also wrong (recipient vs. signer). * g10/ ** issue a NO_SECKEY xxxx if a -u key was not found. * Extend selinux support to other modules See also http://etbe.coker.com.au/2008/06/06/se-linux-support-gpg/ * UTF-8 specific TODOs None. * Manual ** Document all gpgsm options. * Pinpad Reader We do not yet support P15 applications. The trivial thing using ASCII characters will be easy to implement but the other cases need some more work. * Bugs * Howtos ** Migrate OpenPGP keys to another system * Gpg-Agent Locale Although we pass LC_MESSAGE from gpgsm et al. to Pinentry, this has only an effect on the stock GTK strings (e.g. "OK") and not on any strings gpg-agent generates and passes to Pinentry. This defeats our design goal to allow changing the locale without changing gpg-agent's default locale (e.g. by the command updatestartuptty). * RFC 4387: Operational Protocols: Certificate Store Access via HTTP Do we support this?