Re: EEP Light: Option to override private key lookup when using Erlang ssh client

Irina Guberman <[email protected]> Thu, 12 Nov 2015 13:01:32 -0600
Newsgroups gmane.comp.lang.erlang.patches
Message-ID <CAO5CaNRZ6KktuoPtjOYPVM098WxL1=uNr4JJXnE1Qsc2Af9S5Q@mail.gmail.com>
--===============7762669274724935186==
Content-Type: multipart/alternative; boundary=047d7bb04d6241764005245c929f

--047d7bb04d6241764005245c929f
Content-Type: text/plain; charset=UTF-8

Hello dear Erlang developers,

I would tremendously appreciate any help or if anyone can point me to
someone who can help with linking Erlang/OTP.   I created an experimental
BIF in my own fork of erlang/otp, but can't get past linking stage (on
Mac: Undefined
symbols for architecture x86_64,  but same thing happens on ubuntu 14.04)
 even though I checked everywhere and my BIF seems to be everywhere an
existing BIF from the same module is (with same naming  conventions and
all).   I don't know where to post this question either (Erlang Central
didn't work which is understandable, it's not like people are creating BIFs
everyday), I'm so desperate I'm about to post it on Twitter ;)

Thanks a million for reading this message and even more so for pointing me
to where I can get help with this!

Irina.




On Thu, Nov 12, 2015 at 12:19 PM, Hans Nilsson R <
[email protected]> wrote:

> Great!  If there also is documentation and a test case the likelihood of
> acceptance is higher :)
> -Hans
>
> On 11/12/2015 06:31 PM, Vipin Nair wrote:
> > Hello Hans,
> >
> >> A more general way to pass options to the key callback module would be
> >> to introduce a second form of the key_cb option:
> >>   -  keep todays {key_cb, Module::atom()} to keep compatibility
> >>   -  introduce the variant {key_cb, {Module::atom(), ModuleOptions}}
> >> [...]
> >> In that way it is possible to write a callback module with whatever is
> >> needed as private options.
> >
> > This will work! In retrospect, I should have done this instead. This is
> much
> > simpler and solves my problem. I'll send a new pull request with the
> suggested
> > implementation. Thanks!
> >
>
>
> _______________________________________________
> erlang-patches mailing list
> [email protected]
> http://erlang.org/mailman/listinfo/erlang-patches
>
>

--047d7bb04d6241764005245c929f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello dear Erlang developers,<div><br></div><div>I would t=
remendously appreciate any help or if anyone can point me to someone who ca=
n help with linking Erlang/OTP. =C2=A0 I created an experimental BIF in my =
own fork of erlang/otp, but can&#39;t get past linking stage (on Mac:=C2=A0=
<span style=3D"font-family:Menlo;font-size:11px">Undefined symbols for arch=
itecture x86_64</span>, =C2=A0but same thing happens on ubuntu 14.04) =C2=
=A0even though I checked everywhere and my BIF seems to be everywhere an ex=
isting BIF from the same module is (with same naming =C2=A0conventions and =
all). =C2=A0 I don&#39;t know where to post this question either (Erlang Ce=
ntral didn&#39;t work which is understandable, it&#39;s not like people are=
 creating BIFs everyday), I&#39;m so desperate I&#39;m about to post it on =
Twitter ;) =C2=A0</div><div><br></div><div>Thanks a million for reading thi=
s message and even more so for pointing me to where I can get help with thi=
s!</div><div><br></div><div>Irina.</div><div><br></div><div><br></div><div>=
<br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">O=
n Thu, Nov 12, 2015 at 12:19 PM, Hans Nilsson R <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:[email protected]" target=3D"_blank">hans.r.nilsson@=
ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Great!=
=C2=A0 If there also is documentation and a test case the likelihood of<br>
acceptance is higher :)<br>
<span class=3D"HOEnZb"><font color=3D"#888888">-Hans<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 11/12/2015 06:31 PM, Vipin Nair wrote:<br>
&gt; Hello Hans,<br>
&gt;<br>
&gt;&gt; A more general way to pass options to the key callback module woul=
d be<br>
&gt;&gt; to introduce a second form of the key_cb option:<br>
&gt;&gt;=C2=A0 =C2=A0-=C2=A0 keep todays {key_cb, Module::atom()} to keep c=
ompatibility<br>
&gt;&gt;=C2=A0 =C2=A0-=C2=A0 introduce the variant {key_cb, {Module::atom()=
, ModuleOptions}}<br>
&gt;&gt; [...]<br>
&gt;&gt; In that way it is possible to write a callback module with whateve=
r is<br>
&gt;&gt; needed as private options.<br>
&gt;<br>
&gt; This will work! In retrospect, I should have done this instead. This i=
s much<br>
&gt; simpler and solves my problem. I&#39;ll send a new pull request with t=
he suggested<br>
&gt; implementation. Thanks!<br>
&gt;<br>
<br>
</div></div><br>_______________________________________________<br>
erlang-patches mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><=
br>
<a href=3D"http://erlang.org/mailman/listinfo/erlang-patches" rel=3D"norefe=
rrer" target=3D"_blank">http://erlang.org/mailman/listinfo/erlang-patches</=
a><br>
<br></blockquote></div><br></div>

--047d7bb04d6241764005245c929f--

--===============7762669274724935186==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
erlang-patches mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-patches

--===============7762669274724935186==--