Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: Grief! Date: Mon, 15 Sep 2014 17:32:30 -0400 Organization: A noiseless patient Spider Lines: 38 Message-ID: References: <5416463d$0$299$14726298@news.sunsite.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 15 Sep 2014 21:32:36 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="bd4e1cba8d8592bec5d5ed9e4537fbfd"; logging-data="21923"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+LGDwwBVL/uXb8hlbq83N3" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 In-Reply-To: Cancel-Lock: sha1:qzvA/NwVZ/4r2c2HPZxT1y4/Tw8= Xref: csiph.com comp.lang.java.programmer:29992 On 9/15/2014 5:09 PM, Knute Johnson wrote: > On 9/14/2014 18:51, Arne Vajhøj wrote: >> On 9/14/2014 9:39 PM, Knute Johnson wrote: >>> Two days of grief, my manifest file with only one line in it: >>> >>> Permissions: sandbox >>> >>> Java kept rejecting the app as insecure. >> >> Unsigned Applet and newer Java versions? >> >> Arne > > It's a signed Java Web Start app that runs in the sandbox. I have a > code signing cert and the file is signed. The problem was the blank > spaces between 'Permissions:' and 'sandbox', only one space is > permissible between the colon and the key or value. I couldn't find > anything in the docs but that is the way it works. I've never seen a > properties file or any other pair file that wouldn't ignore blank space. Only one space? Sounds moronic.[*] After some digging, though, I found these syntax productions in Oracle's "JAR File Specification" at : header: name : value ... value: SPACE *otherchar newline *continuation So, the single SPACE character is actually a documented requirement of the syntax, odd[*] as that may seem. [*] Maybe not completely moronic nor totally odd, though. The syntax has no quoting convention, so if the parser were to collapse a run of spaces together there'd be no way to specify a space as the first character of a value -- and what a huge loss THAT would be! -- esosman@comcast-dot-net.invalid