From: manowar@altlinux.org
To: oss-gost-crypto@lists.altlinux.org
Subject: [oss-gost-crypto] Fwd: Re: GOST support in GnuPG
Date: Wed, 10 Apr 2019 20:29:23 +0000
Message-ID: <3q5kl6.ppri90.rvdfyn-qmf@imap.altlinux.org> (raw)
In-Reply-To: <87mukx1z3y.fsf@wheatstone.g10code.de>
Кажется, дело сдвинулось чуть вперёд --- руководитель проекта GnuPG согласился посмотреть патчи, правда неопределённо когда.
Мне не совсем ясно, что он имеет в виду под словом "domains" в последнем абзаце. Это намёк на интерес расширить сферу (и географию) применения GnuPG или мне показалось?
И ещё вопрос: можно ли говорить о ГОСТ 2001 как о, допустим, RSA 128 бит (или сколько там было вначале)? В том смысле, что даже устаревший и потенциально ненадёжный стандарт нужно поддерживать исходя из соображений обратной совместимости. Ну и ещё потому, что это закладывает кодовую (алгоритмическую) базу для более поздних стандартов, которые являются его развитием.
Ссылка на письмо ниже: https://lists.gnupg.org/pipermail/gnupg-devel/2019-April/034293.html .
--- Исходное сообщение ---
> Hi!
>
> On Wed, 10 Apr 2019 20:56, manowar@altlinux.org said:
>
> > Hi again. My question is still unanswered. Are there some guidelines
> > about adding new key types, curves, ciphers, etc. to GnuPG I should keep
> > to when making such changes?
>
> Aside from doc/HACKING there are no fixed rules. However adding new
> algorithms etc requires that they are part of the implemented standard
> and further we need to see whether it makese sense to implement and
> _maintain_ them.
>
> >> My current set of patches are as follows:
>
> I briefly looked at your patches but concluded that this is a log of new
> code for just another algorithm. Thus your patches requires a closer
> look. Right now I do not have the time for this and unless there is a
> reason to tag it at high priority, I doubt that I can look at it in the
> next weeks.
>
> A reason for this might be that we can foster deployment of OpenPGP in
> certain domains. However, if it turns out that GOST as been weakened on
> purpose, there is no chance that it can part of _gpg_ (ie. to OpenPGP).
>
>
> Shalom-Salam,
>
> Werner
>
next parent reply other threads:[~2019-04-10 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 20:29 ` manowar [this message]
2019-04-10 21:26 ` manowar
2019-04-10 23:09 ` Vitaly Chikunov
2019-04-11 16:24 ` Vitaly Chikunov
2019-04-11 21:12 ` Wartan Hachaturow
2019-04-11 21:05 ` Dmitry Eremin-Solenikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3q5kl6.ppri90.rvdfyn-qmf@imap.altlinux.org \
--to=manowar@altlinux.org \
--cc=oss-gost-crypto@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Open-source aspects of GOST Cryptography
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/oss-gost-crypto/0 oss-gost-crypto/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 oss-gost-crypto oss-gost-crypto/ http://lore.altlinux.org/oss-gost-crypto \
oss-gost-crypto@lists.altlinux.org oss-gost-crypto@lists.altlinux.ru oss-gost-crypto@lists.altlinux.com
public-inbox-index oss-gost-crypto
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.oss-gost-crypto
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git