I am marking this case as closed approved since it times out today.
I believe that all issues raised have been addressed. The two
issues raised included:
- Issues regarding how WebKit supports SSL certificates. Alfred Peng
worked with Darren Moffat to address this issue, and the case
mate
Willie:
>> The main reason for integrating WebKit is so that it can be embedded
>> in programs like yelp and devhelp. If WebKit is not usably accessible,
>> then we can continue to deliver older versions of the yelp and devhelp
>> modules which do not use WebKit and not lose any accessibility.
>>
Willie:
> Are you suggesting that WebKit not integrate in Solaris until it is
> more fully accessible? If so, what do you recommend be done instead?
I notice that you raised this issue in the thread "Who is using WebKit
in GNOME 2.28" on the GNOME desktop-devel-list at gnome.org. From that
disc
Hi Brian:
Brian Cameron wrote:
>> Are you suggesting that WebKit not integrate in Solaris until it is
>> more fully accessible? If so, what do you recommend be done instead?
>
> I notice that you raised this issue in the thread "Who is using WebKit
> in GNOME 2.28" on the GNOME desktop-devel-list
Hi Brian:
The problem is that this portion of the document can mislead people into
thinking WebKit a11y is working and complete:
"WebKit supports the AT-SPI accessibility layer since version 1.0.x.
The GNOME accessibility team are working hard with WebKit team to ensure
WebKit is accessible wh
Willie:
> If there is a chance, some clarification should be made about the a11y
> statement. The WebKit team and GNOME teams are working hard to provide
> fundamental a11y support for WebKit, but there is a lot of work to do. See:
>
> http://mail.gnome.org/archives/desktop-devel-list/2009-July/m
Hi Brian:
If there is a chance, some clarification should be made about the a11y
statement. The WebKit team and GNOME teams are working hard to provide
fundamental a11y support for WebKit, but there is a lot of work to do.
See:
http://mail.gnome.org/archives/desktop-devel-list/2009-July/
Based on the discussion so far, I have updated the WebKit onepager
in the case materials. See attached diff file for details of these
changes.
This case was approved at the August 5th meeting, but then was
re-opened when Darren Moffat raised issues with how SSL certificates
are managed.
I belie
On 08/11/09 05:01 PM, Darren J Moffat wrote:
>> Instead the discussion should maybe stick to just the question of what
>> the default HTTPS setting should be, whether Darren's suggestion of
>> linking this case to shipping a working root CA file is appropriate, and
>> how to document how to load
Alfred Peng wrote:
> On 08/11/09 05:01 PM, Darren J Moffat wrote:
>>> Instead the discussion should maybe stick to just the question of what
>>> the default HTTPS setting should be, whether Darren's suggestion of
>>> linking this case to shipping a working root CA file is appropriate, and
>>> ho
Mark Martin wrote:
>>> Instead the discussion should maybe stick to just the question of
>>> what the default HTTPS setting should be, whether Darren's suggestion
>>> of linking this case to shipping a working root CA file is
>>> appropriate, and how to document how to load alternate certs.
>>
>
we base WebKit on Chrome's network stack?
>
> U.
>
>
>
>> Date: Tue, 11 Aug 2009 01:42:13 +0800
>> From: Alfred.Peng at Sun.COM
>> Subject: Re: [desktop-discuss] WebKit 1.1.x [LSARC/2009/409 FastTrack
>> timeou
Hugh McIntyre wrote:
> Uros Nedic wrote:
>> [2] Let we extend libsoup with additional interfaces capable
>> to deal with this issue, or to change actual implementation
>> of interface we have conflict with.
>
> If you look at the following libsoup bugs, it looks like
> libsoup is planning to add n
Darren J Moffat wrote:
> Hugh McIntyre wrote:
>> Uros Nedic wrote:
>>> [2] Let we extend libsoup with additional interfaces capable
>>> to deal with this issue, or to change actual implementation
>>> of interface we have conflict with.
>>
>> If you look at the following libsoup bugs, it looks like
---
>
>> Date: Sat, 8 Aug 2009 18:32:31 +0800
>> From: Alfred.Peng at Sun.COM
>> Subject: Re: [desktop-discuss] WebKit 1.1.x [LSARC/2009/409 FastTrack
>> timeout 08/04/2009]
>> To: urosn at live.com
>> CC: Darren.Moffat at Sun.COM; desktop-discuss at op
Uros Nedic wrote:
> [2] Let we extend libsoup with additional interfaces capable
> to deal with this issue, or to change actual implementation
> of interface we have conflict with.
If you look at the following libsoup bugs, it looks like
libsoup is planning to add new certificate APIs, and therefo
Is it possible that we base WebKit on Chrome's network stack?
U.
> Date: Tue, 11 Aug 2009 01:42:13 +0800
> From: Alfred.Peng at Sun.COM
> Subject: Re: [desktop-discuss] WebKit 1.1.x [LSARC/2009/409 FastTrack timeout
> 08/04/2009]
> T
Matt Lewandowsky wrote:
>> From "Alfred Peng" , August 07, 2009 2:40 AM:
>
>> On 08/ 7/09 04:12 PM, Hugh McIntyre wrote:
>>> 2. Solaris ships with SOUP_SESSION_SSL_CA_FILE set to /dev/null (HTTPS
>>> disabled) but with documentation saying that users can call
>>> g_object_set(..., SOUP_SESSION_SS
>> Date: Fri, 7 Aug 2009 15:27:08 +0800
>> From: Alfred.Peng at Sun.COM
>> To: Darren.Moffat at Sun.COM
>> CC: desktop-discuss at opensolaris.org; storycrafter at gmail.com; LSARC-ext
>> at Sun.COM
>> Subject: Re: [desktop-discuss] WebKit 1.1.x [LSARC/2009/40
On 08/ 7/09 10:12 PM, Darren J Moffat wrote:
> Alfred Peng wrote:
>
>> Thanks for the comments.
>>
>> Option #2 looks good to me. I'll add those to the manual page if people
>> agree with this.
>>
> I still haven't seen an answer to what happens on other platforms that
> ship webkit. How
an style educational system :).
Best,
Uros Nedic, MSc
> Date: Sat, 8 Aug 2009 18:32:31 +0800
> From: Alfred.Peng at Sun.COM
> Subject: Re: [desktop-discuss] WebKit 1.1.x [LSARC/2009/409 FastTrack timeout
> 08/04/2009]
> To: urosn at live
Alfred Peng:
>> As for an RFE, could you clarify a little on that? An RFE to enable
>> users to pass the certificate in the first place? It's not even
>> available as delivered here?
>>
>>
> Sorry for not making things clear. libsoup does provide the support for
> passing certificate th
On 08/ 7/09 04:12 PM, Hugh McIntyre wrote:
> So roughly speaking this seems to give 3 options:
>
> 1. Solaris adds some code to set SOUP_SESSION_SSL_CA_FILE based on an
> environment variable or system default if they exist by default, else
> either /dev/null (no HTTPS) or the default (no checki
n.COM
> To: Darren.Moffat at Sun.COM
> CC: desktop-discuss at opensolaris.org; storycrafter at gmail.com; LSARC-ext
> at Sun.COM
> Subject: Re: [desktop-discuss] WebKit 1.1.x [LSARC/2009/409 FastTrack timeout
> 08/04/2009]
>
> Hi Darren/Mark,
>
> Before I started the arc ca
Hi Darren/Mark,
Before I started the arc case, I sent a query with regards to this HTTPS
support issue to the WebKit community. Dan Winship, the libsoup
developer, gave me some insight into the problem:
http://lists.macosforge.org/pipermail/webkit-dev/2009-June/008566.html.
Roughly there are two
Alfred Peng wrote:
> Thanks for the comments.
>
> Option #2 looks good to me. I'll add those to the manual page if people
> agree with this.
I still haven't seen an answer to what happens on other platforms that
ship webkit. How is webkit delivered and documented on Linux distros ?
Why should
>From "Alfred Peng" , August 07, 2009 2:40 AM:
> On 08/ 7/09 04:12 PM, Hugh McIntyre wrote:
>> 2. Solaris ships with SOUP_SESSION_SSL_CA_FILE set to /dev/null (HTTPS
>> disabled) but with documentation saying that users can call
>> g_object_set(..., SOUP_SESSION_SSL_CA_FILE, ...) to define either
Darren J Moffat wrote:
> Alfred Peng wrote:
>> Thanks for the comments.
>>
>> Option #2 looks good to me. I'll add those to the manual page if people
>> agree with this.
>
> I still haven't seen an answer to what happens on other platforms that
> ship webkit. How is webkit delivered and documente
Alfred Peng wrote:
> Hi Darren/Mark,
>
> Before I started the arc case, I sent a query with regards to this HTTPS
> support issue to the WebKit community. Dan Winship, the libsoup
> developer, gave me some insight into the problem:
> http://lists.macosforge.org/pipermail/webkit-dev/2009-June/0085
Since the discussion on this case has gotten controversial again, I
have changed the status in the IAM file to "waiting fast-track" and
increased the timeout to 08/12.
Alfred, can you respond to Darren and Mark's issues?
Thanks,
Brian
Darren J Moffat wrote:
> Mark Martin wrote:
>> I don't thi
Mark Martin wrote:
> I don't think the only issue is the lack of a handy, well known cert
> repository; the fact that the underlying implementation doesn't
> validate properly would probably surprise folks.
That really depends on what you mean by "validate properly", sure there
are standards t
Brian Cameron wrote:
>
> LSARC:
>
> The case materials have been updated to reflect that HTTPS support
> will be disabled. See attached updated onepager and a diff file
> that shows the differences between this version of the onepager and
> the previous version.
I'm comeing to this issue late.
Mark Martin wrote:
> Darren J Moffat wrote:
>>
>> Also this is really no different several other similar cases with SSL.
>>
>> If HTTPS is not enabled then I will derail this case and call for a
>> vote.
>>
>
> I don't think the only issue is the lack of a handy, well known cert
> repository; th
Darren J Moffat wrote:
> Brian Cameron wrote:
>>
>> LSARC:
>>
>> The case materials have been updated to reflect that HTTPS support
>> will be disabled. See attached updated onepager and a diff file
>> that shows the differences between this version of the onepager and
>> the previous version.
>
>
LSARC:
The case materials have been updated to reflect that HTTPS support
will be disabled. See attached updated onepager and a diff file
that shows the differences between this version of the onepager and
the previous version.
I have marked this case as "closed approved".
Thanks,
Brian
> N
Note that this case was approved at today's LSARC meeting with
the provision that the specification is updated so that HTTPS
is disabled until the issue with certificates is better addressed,
hopefully in a future release of WebKit. So this case is currently
marked as "need spec".
Alfred, can yo
Alfred Peng wrote:
>
>
> As for accepting certificates by default, we could roll back to the
> behavior of case 2008/782. That's to say, to disable https support by
> default. Currently, Evolution, which supports showing https pages, could
> be the only application in OpenSolaris that'll be impacte
Hi Mark,
On 07/31/09 02:13 AM, Mark Martin wrote:
> Seems like we went from the prior WebKit (2008/782) requiring an
> override to accept all SSL to having that behavior by default.
>
Yes, since the http backend was switched from libcURL to libsoup, the
default behavior was changed in the late
Alfred Peng wrote:
> Hi Mark,
>
> Thanks for pointing this out.
>
> The consumers of libsoup can point a file containing certificates for
> recognized SSL Certificate Authorities. HTTPS connections will be
> checked against these authorities, and rejected if they can't be
> verified
> (http://libra
Hi Mark,
Thanks for pointing this out.
The consumers of libsoup can point a file containing certificates for
recognized SSL Certificate Authorities. HTTPS connections will be
checked against these authorities, and rejected if they can't be
verified
(http://library.gnome.org/devel/libsoup/stable/l
Hi John,
Sorry for not making things clear before the arc submission.
Previously, we submitted the arc case LSARC/2008/782 to integrate WebKit
1.0.x to OpenSolaris for GNOME 2.26. Actually, there was no official
release for WebKit GTK port at that time. We just grabbed the version
information fro
Alfred Peng wrote:
>
> As for the header files, I just compare the new pkgmap with the old one.
> They contain the same set of files. On the other hand, the "Exported
> Interface" /usr/include/webkit-1.0 was declared to be Volatile in the
> previously arc. I think it's not necessary to list the fi
On 07/23/09 09:49 PM, Stefan Teleman wrote:
> Brian Cameron wrote:
>
>
>> Imported Interfaces:
>>
>> Interface Stability Comments
>>
>>
>>
>> cURL
John Fischer wrote:
> Jim,
>
> The OSD (formerly JDS) group will have both a regular end user package
> and a developer package. The developer package will typically contain
> things relating to header files, package configuration scripts and
> sometimes developer documentation. Other packages t
Jim,
Most of these I can not answer but I can answer the library version
question because I asked it prior to the fast track submission. I'll
let the project team answer the others and they can correct me if I
am wrong. Note, I am not part of this project just know enough about
it to answer some
Brian Cameron wrote:
> The libcURL HTTP backend support has been removed from WebKit 1.1.x.
> The
> default HTTP backend is now libsoup. WebKit uses libsoup to verify the
> peer's certificates for HTTPS connections. Currently, WebKit accepts
> all
> SSL certificate
Brian Cameron wrote:
> 4.8. Packaging & Delivery:
>
> The project will be delivering the following packages:
> SUNWwebkit
> SUNWwebkit-devel
What's the difference between the two packages if any?
Cheers,
Jim
BTW. You may want to update 1.4.4. OPG is not a BU
anymore.
Alfred Peng wrote:
> On 07/23/09 09:49 PM, Stefan Teleman wrote:
>> Brian Cameron wrote:
>>
>>
>>> Imported Interfaces:
>>>
>>> Interface Stability Comments
>>>
>>>
>>>
Brian Cameron wrote:
> Imported Interfaces:
>
> Interface Stability Comments
>
>
>
> cURLObsolete Uncommitted PSARC/2007/165
CURL is U
Jim,
The OSD (formerly JDS) group will have both a regular end user package
and a developer package. The developer package will typically contain
things relating to header files, package configuration scripts and
sometimes developer documentation. Other packages that you will see
with the OSD gr
Michael,
The first section is from the sac_nextcase script. The second one is
from the form that the project team filled out.
John
Michael Kearney wrote:
> Why is section 1 partially duplicated?
>
> Brian Cameron wrote:
>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>> This informatio
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
WebKit 1.1.x
1.2. Name of Document Author/Supplier:
Author: Alfred Peng
1.3 Date of This Document:
2
52 matches
Mail list logo
