Thanks! I just tested it. It works!
On Sun, Oct 26, 2014 at 5:52 PM, David du Colombier <0in...@gmail.com>
wrote:
> Just to be clearer. The patch (unified diff) attached in my
> previous email can be applied with ape/patch.
>
> A patch(1) (/n/sources/patch) can't be applied automatically
> withou
> you make a good point.
David did explain. It's fixed in the patch.
Lucio.
-
This email has been scanned by the MxScan Email Security System.
---
On Mon Oct 27 00:22:36 EDT 2014, lu...@proxima.alt.za wrote:
> > @@ -1594,6 +1595,7 @@
> > static Ints7 oid_md4WithRSAEncryption = {7, 1, 2, 840, 113549, 1, 1, 3 };
> > static Ints7 oid_md5WithRSAEncryption = {7, 1, 2, 840, 113549, 1, 1, 4 };
> > static Ints7 oid_sha1WithRSAEncryption ={7, 1, 2,
On Mon Oct 27 05:20:04 EDT 2014, 9f...@hamnavoe.com wrote:
> > A patch(1) (/n/sources/patch) can't be applied automatically
> > without modifying patch/apply.
>
> Actually it can, thanks to the magic of bind(1):
>
> cpu% 9fs sources
> cpu% PATCH=libsec-x509-sha256rsa
> cpu% mkdi
> A patch(1) (/n/sources/patch) can't be applied automatically
> without modifying patch/apply.
Actually it can, thanks to the magic of bind(1):
cpu% 9fs sources
cpu% PATCH=libsec-x509-sha256rsa
cpu% mkdir -p $home/patch/$PATCH
cpu% bind -bc $home/patch/$PATCH /n/s
> It was a typo. I fixed it before submitting the patch to /n/sources.
I thought it might be; better safe than sorry, I suppose.
Lucio.
-
This email has been scanned by the MxScan Email Security System.
> The existing identifiers are prefixed with "oid_"; is there a reason
> for leaving the prefix out?
It was a typo. I fixed it before submitting the patch to /n/sources.
--
David du Colombier
> @@ -1594,6 +1595,7 @@
> static Ints7 oid_md4WithRSAEncryption = {7, 1, 2, 840, 113549, 1, 1, 3 };
> static Ints7 oid_md5WithRSAEncryption = {7, 1, 2, 840, 113549, 1, 1, 4 };
> static Ints7 oid_sha1WithRSAEncryption ={7, 1, 2, 840, 113549, 1, 1, 5 };
> +static Ints7 sha256WithRSAEncryption ={7,
> Then you have to rebuild libsec and hget.
... and any other client of libsec, presumably?
Lucio.
-
This email has been scanned by the MxScan Email Security System.
-
Just to be clearer. The patch (unified diff) attached in my
previous email can be applied with ape/patch.
A patch(1) (/n/sources/patch) can't be applied automatically
without modifying patch/apply. You have to copy the individual
files by hand to the destination indicated in the "files" file.
--
> Thanks! Quick question: how do I apply the patch? I didn't see an
> argument to diff or a patch utility.
You can apply the patch with ape/patch, or simply copy the
x509.c file from /n/sources:
cp /n/sources/patch/libsec-x509-sha256rsa/x509.c /sys/src/libsec/port
--
David du Colombier
Thanks! Quick question: how do I apply the patch? I didn't see an argument
to diff or a patch utility.
On Sun, Oct 26, 2014 at 5:30 PM, David du Colombier <0in...@gmail.com>
wrote:
> The patch is now available here:
>
> /n/sources/patch/libsec-x509-sha256rsa
>
> --
> David du Colombier
>
>
--
The patch is now available here:
/n/sources/patch/libsec-x509-sha256rsa
--
David du Colombier
> I'm trying to download the a Python script and keep running into
> trouble. I am running this:
>
> hget https://hg.python.org/cpython/raw-file/4391ab72dd7b/Lib/types.py
> > types.py
>
> However, hget keeps complaining with `tlsClient: tls: local invalid
> x509/rsa certificate`. The time and dat
I'm trying to download the a Python script and keep running into trouble. I
am running this:
hget https://hg.python.org/cpython/raw-file/4391ab72dd7b/Lib/types.py >
types.py
However, hget keeps complaining with `tlsClient: tls: local invalid
x509/rsa certificate`. The time and date of my Plan 9 V
15 matches
Mail list logo
