mailman-lists-archive/pipermail/zapps-wg/2018/000276.html

78 lines
3.2 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [zapps-wg] Go implementation - Problems with Go 1.9.4
</TITLE>
<LINK REL="Index" HREF="/pipermail/zapps-wg/2018/index.html" >
<LINK REL="made" HREF="mailto:zapps-wg%40lists.zfnd.org?Subject=Re%3A%20%5Bzapps-wg%5D%20Go%20implementation%20-%20Problems%20with%20Go%201.9.4&In-Reply-To=%3C5A8A8BD8.2080706%40z.cash%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000260.html">
<LINK REL="Next" HREF="000278.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[zapps-wg] Go implementation - Problems with Go 1.9.4</H1>
<B>Daira Hopwood</B>
<A HREF="mailto:zapps-wg%40lists.zfnd.org?Subject=Re%3A%20%5Bzapps-wg%5D%20Go%20implementation%20-%20Problems%20with%20Go%201.9.4&In-Reply-To=%3C5A8A8BD8.2080706%40z.cash%3E"
TITLE="[zapps-wg] Go implementation - Problems with Go 1.9.4">daira at z.cash
</A><BR>
<I>Mon Feb 19 03:33:28 EST 2018</I>
<P><UL>
<LI>Previous message (by thread): <A HREF="000260.html">[zapps-wg] Go implementation - Problems with Go 1.9.4
</A></li>
<LI>Next message (by thread): <A HREF="000278.html">[zapps-wg] Go implementation - Problems with Go 1.9.4
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#276">[ date ]</a>
<a href="thread.html#276">[ thread ]</a>
<a href="subject.html#276">[ subject ]</a>
<a href="author.html#276">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 14/02/18 21:36, Philip Stehlik via zapps-wg wrote:
&gt;<i> Hey folks,
</I>&gt;<i> In case you were planning to use the go implementation for your upcoming
</I>&gt;<i> participation, be aware of this issue with go 1.9.4 --
</I>&gt;<i> <A HREF="https://github.com/golang/go/issues/23739">https://github.com/golang/go/issues/23739</A>
</I>
I honestly think the Go developers are deluding themselves if they think
that gcc and clang can be used on untrusted input just by sanitizing
compiler and linker flags; they were never designed to be secure for
untrusted input.
That said, please report which compiler flags need to be whitelisted at
&lt;<A HREF="https://github.com/golang/go/issues/23749">https://github.com/golang/go/issues/23749</A>&gt;
--
Daira Hopwood &#9895;&#9398;
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message (by thread): <A HREF="000260.html">[zapps-wg] Go implementation - Problems with Go 1.9.4
</A></li>
<LI>Next message (by thread): <A HREF="000278.html">[zapps-wg] Go implementation - Problems with Go 1.9.4
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#276">[ date ]</a>
<a href="thread.html#276">[ thread ]</a>
<a href="subject.html#276">[ subject ]</a>
<a href="author.html#276">[ author ]</a>
</LI>
</UL>
<hr>
<a href="/mailman/listinfo/zapps-wg">More information about the zapps-wg
mailing list</a><br>
</body></html>