From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: creating unibyte strings
Date: Mon, 25 Mar 2019 09:47:26 +0800 [thread overview]
Message-ID: <CADtN0WKrEFOsw=VhmHo+BkCg1X0QcJD57XbO0qEk06TOzS9oAw@mail.gmail.com> (raw)
In-Reply-To: <83ftrcnqp0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Mon, 25 Mar 2019, 01:10 Eli Zaretskii, <eliz@gnu.org> wrote:
>
> Can you tell why the byte buffer needs to be exposed to Lisp in this
> case? IOW, what would a Lisp program using this module want to do
> with these byte buffers?
>
In this particular case, I'm exposing GSSAPI, which is a rather low level
interface to Kerberos (well, it supports multiple systems, but it's mostly
used for Kerberos).
For example, one function is called gss-unwrap, and it takes an encrypted
byte array and decrypts it, returning a new byte array with the decrypted
content.
What the impact is depends on the Elisp code that uses GSS. In the case of
IMAP for example, it's not too bad, since only the initial handshake is
passed through these functions (IMAP encryption is handled by TLS, not
Kerberos). However, there are other uses where every single package is
passed through the wrap and unwrap functions.
Regards,
Elias
Regards,
Elias
>
[-- Attachment #2: Type: text/html, Size: 1702 bytes --]
next prev parent reply other threads:[~2019-03-25 1:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:12 Oddities with dynamic modules Eli Zaretskii
2018-10-12 14:29 ` Kaushal Modi
2019-02-10 20:23 ` Philipp Stephani
2019-02-11 15:45 ` Eli Zaretskii
2019-02-11 16:04 ` Yuri Khan
2019-03-21 20:04 ` Philipp Stephani
2019-03-21 20:17 ` Eli Zaretskii
2019-03-21 20:32 ` Philipp Stephani
2019-03-21 20:46 ` Eli Zaretskii
2019-03-21 20:51 ` Philipp Stephani
2019-03-21 20:12 ` Philipp Stephani
2019-03-21 20:25 ` Eli Zaretskii
2019-03-21 20:34 ` Philipp Stephani
2019-03-21 20:51 ` Eli Zaretskii
2019-03-21 20:58 ` Philipp Stephani
2019-03-22 1:26 ` creating unibyte strings (was: Oddities with dynamic modules) Stefan Monnier
2019-03-22 7:41 ` Eli Zaretskii
2019-03-22 12:33 ` creating unibyte strings Stefan Monnier
2019-03-22 13:27 ` Eli Zaretskii
2019-03-22 14:23 ` Stefan Monnier
2019-03-22 15:11 ` Eli Zaretskii
2019-03-22 15:37 ` Stefan Monnier
2019-03-22 15:54 ` Eli Zaretskii
2019-03-24 14:51 ` Elias Mårtenson
2019-03-24 17:10 ` Eli Zaretskii
2019-03-25 1:47 ` Elias Mårtenson [this message]
2019-03-25 3:41 ` Eli Zaretskii
2019-03-26 10:23 ` Elias Mårtenson
2019-03-26 11:12 ` Stefan Monnier
2019-03-22 8:20 ` Oddities with dynamic modules Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADtN0WKrEFOsw=VhmHo+BkCg1X0QcJD57XbO0qEk06TOzS9oAw@mail.gmail.com' \
--to=lokedhs@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).