Re: [Wireshark-dev] Git + Gerrit: next steps

2014-01-06 Thread Gerald Combs
On 1/2/14 6:36 AM, Joerg Mayer wrote:
 On Wed, Jan 01, 2014 at 02:11:43PM -0800, Gerald Combs wrote:
 I was able to shoehorn openid-selector
 (http://code.google.com/p/openid-selector/) into the login page on
 test.code.wireshark.org. If you have an account at one of the top
 providers listed at http://meta.stackoverflow.com/a/147872/139350
 (including Stack Exchange itself) logging in should be trivial.
 
 Technically I do have a launchpad account, so I could use that.
 My core issue is that I don't want to provide any of these entities
 with information about when I do Wireshark work.

I've been trying to come up with a response that's less awful than find
an OpenID provider you trust or set up your own but so far I've been
unsuccessful.

Gerrit supports several authentication methods (OpenID, LDAP, and HTTP)
but each one seems to assume that you have an existing account
somewhere. I.e. if we switch to LDAP or HTTP authentication the account
will have to be created and managed elsewhere.

The wiki and blog should both be able to act as providers in theory but
failed in practice. MoinMoin's provider code scans the entire user
database at least once for each page load. Enabling it on
wiki.wireshark.org immediately slows the system to a crawl. Wordpress'
OpenID provider doesn't seem to generate valid output. Neither Gerrit
nor Stack Exchange recognized it.

I'll keep looking for options.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Git + Gerrit: next steps

2014-01-02 Thread Joerg Mayer
On Wed, Jan 01, 2014 at 02:11:43PM -0800, Gerald Combs wrote:
 I was able to shoehorn openid-selector
 (http://code.google.com/p/openid-selector/) into the login page on
 test.code.wireshark.org. If you have an account at one of the top
 providers listed at http://meta.stackoverflow.com/a/147872/139350
 (including Stack Exchange itself) logging in should be trivial.

Technically I do have a launchpad account, so I could use that.
My core issue is that I don't want to provide any of these entities
with information about when I do Wireshark work.

Ciao
 Jörg
-- 
Joerg Mayer   jma...@loplof.de
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Git + Gerrit: next steps

2014-01-01 Thread Gerald Combs
On 12/23/13 12:12 PM, Gerald Combs wrote:
 On 12/21/13 2:39 AM, Joerg Mayer wrote:
 On Wed, Dec 18, 2013 at 04:12:20PM -0800, Gerald Combs wrote:
 I'm assuming everyone has had a chance to test the Gerrit installation
 at test.code.wireshark.org If you haven't, now might be a good time.
 Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific
 idea I'm going to start the process of migrating from Subversion. The
 timeline looks roughly like this:

 Preparation (next few days, early January):

 1. Create a Gerrit instance at code.wireshark.org.

 I failed at this step. I neither have nor will I have a google/yahoo/whatever
 ID.  Is there another way to provide authentication?
 
 Do you have an account with *any* OpenID provider? There are plenty of
 options aside from Google or Yahoo, including hosting your own:
 
 https://help.launchpad.net/YourAccount/OpenID
 https://fedoraproject.org/wiki/OpenID
 https://sourceforge.net/apps/trac/sourceforge/wiki/OpenID
 http://wiki.openid.net/w/page/12995226/Run%20your%20own%20identity%20server

I was able to shoehorn openid-selector
(http://code.google.com/p/openid-selector/) into the login page on
test.code.wireshark.org. If you have an account at one of the top
providers listed at http://meta.stackoverflow.com/a/147872/139350
(including Stack Exchange itself) logging in should be trivial.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-23 Thread Gerald Combs
On 12/21/13 2:39 AM, Joerg Mayer wrote:
 On Wed, Dec 18, 2013 at 04:12:20PM -0800, Gerald Combs wrote:
 I'm assuming everyone has had a chance to test the Gerrit installation
 at test.code.wireshark.org If you haven't, now might be a good time.
 Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific
 idea I'm going to start the process of migrating from Subversion. The
 timeline looks roughly like this:

 Preparation (next few days, early January):

 1. Create a Gerrit instance at code.wireshark.org.
 
 I failed at this step. I neither have nor will I have a google/yahoo/whatever
 ID.  Is there another way to provide authentication?

Do you have an account with *any* OpenID provider? There are plenty of
options aside from Google or Yahoo, including hosting your own:

https://help.launchpad.net/YourAccount/OpenID
https://fedoraproject.org/wiki/OpenID
https://sourceforge.net/apps/trac/sourceforge/wiki/OpenID
http://wiki.openid.net/w/page/12995226/Run%20your%20own%20identity%20server

Aside from OpenID Gerrit allows for HTTP or LDAP authentication but
OpenID is the easiest to use and manage by far from both a user and
sysadmin perspective.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-23 Thread Guy Harris

On Dec 21, 2013, at 2:39 AM, Joerg Mayer jma...@loplof.de wrote:

 On Wed, Dec 18, 2013 at 04:12:20PM -0800, Gerald Combs wrote:
 I'm assuming everyone has had a chance to test the Gerrit installation
 at test.code.wireshark.org If you haven't, now might be a good time.
 Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific
 idea I'm going to start the process of migrating from Subversion. The
 timeline looks roughly like this:
 
 Preparation (next few days, early January):
 
 1. Create a Gerrit instance at code.wireshark.org.
 
 I failed at this step. I neither have nor will I have a google/yahoo/whatever
 ID.  Is there another way to provide authentication?

OK, I'm confused - which of the steps in those lists are things *Gerald* has to 
do, and which are things that all developers who want to use Git+Gerrit have to 
do?  I'd assumed all those steps were just things Gerald was going to be doing.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-21 Thread Joerg Mayer
On Wed, Dec 18, 2013 at 04:12:20PM -0800, Gerald Combs wrote:
 I'm assuming everyone has had a chance to test the Gerrit installation
 at test.code.wireshark.org If you haven't, now might be a good time.
 Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific
 idea I'm going to start the process of migrating from Subversion. The
 timeline looks roughly like this:
 
 Preparation (next few days, early January):
 
 1. Create a Gerrit instance at code.wireshark.org.

I failed at this step. I neither have nor will I have a google/yahoo/whatever
ID.  Is there another way to provide authentication?

Thanks
   Jörg

-- 
Joerg Mayer   jma...@loplof.de
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-20 Thread Dario Lombardo
On Thu, Dec 19, 2013 at 8:51 PM, Gerald Combs ger...@wireshark.org wrote:

 BTW, I *might* be able to have Gerrit's SSH daemon listen on port 22
 instead of 29418. Would this be useful?


In testing/lab/home networks access to outside is normally open (or can be
opened). That means that port 80, 22, 443 or XXX is allowed. In corporate
networks web access is always granted through proxies, while other traffic
is not allowed. My opinion is that ssh port doesn't make the difference.
The difference is made by the http write access, that is the most common
channel.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-19 Thread Dario Lombardo
On Thu, Dec 19, 2013 at 4:57 AM, Evan Huus eapa...@gmail.com wrote:

 - handy quick-start instructions from Marc:
 https://www.wireshark.org/lists/wireshark-dev/201309/msg00191.html


I had a look at the instructions above. Seems that only ssh is supported.
Will it be so in the production git too, or http in write mode will be
available? In some networks direct ssh is not possible, while proxied http
is.
Dario.
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-19 Thread Gerald Combs
On 12/19/13 1:17 AM, Dario Lombardo wrote:
 On Thu, Dec 19, 2013 at 4:57 AM, Evan Huus eapa...@gmail.com
 mailto:eapa...@gmail.com wrote:
 
 - handy quick-start instructions from Marc:
 https://www.wireshark.org/lists/wireshark-dev/201309/msg00191.html
 
 
 I had a look at the instructions above. Seems that only ssh is
 supported. Will it be so in the production git too, or http in write
 mode will be available? In some networks direct ssh is not possible,
 while proxied http is.

HTTP/HTTPS access will be supported as well. The Wireshark project page at

http://test.code.wireshark.org/review/#/admin/projects/wireshark-review-sandbox

provides Anonymous HTTP, SSH, and HTTP access for signed-in users. You
can generate an HTTP password via Settings→HTTP Password.

BTW, I *might* be able to have Gerrit's SSH daemon listen on port 22
instead of 29418. Would this be useful?
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Git + Gerrit: next steps

2013-12-18 Thread Gerald Combs
I'm assuming everyone has had a chance to test the Gerrit installation
at test.code.wireshark.org If you haven't, now might be a good time.
Unless anyone thinks that moving to Git+Gerrit is an absolutely horrific
idea I'm going to start the process of migrating from Subversion. The
timeline looks roughly like this:

Preparation (next few days, early January):

1. Create a Gerrit instance at code.wireshark.org.
2. Create a read-only Git repository at code.wireshark.org/wireshark.
3. Install, configure and test Buildbot, Bugzilla, and Github
   integration.

Flag day (mid to late January):

1. Make the read-write Subversion repository read-only.
2. Sync Subversion to Git one last time.
3. Enable write access on code.wireshark.org/wireshark.

We've been using Subversion for nearly ten years[1]. I realize this is a
big change and I'll do my best to make the transition as smooth as possible.

[1] http://www.wireshark.org/lists/ethereal-dev/200407/msg00263.html
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-18 Thread Ed Beroset

Gerald Combs wrote:

I'm assuming everyone has had a chance to test the Gerrit installation
at test.code.wireshark.org If you haven't, now might be a good time.


Had the chance to, perhaps, but haven't yet.  I'm not sure I saved the 
old emails about it, and http://www.wireshark.org/develop.html just 
points to a svn and a git clone repository.


For those of us who were sleeping that day in class, what's the best way 
to get up to speed on this?


Ed
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] Git + Gerrit: next steps

2013-12-18 Thread Evan Huus
On Wed, Dec 18, 2013 at 9:08 PM, Ed Beroset bero...@mindspring.com wrote:
 Gerald Combs wrote:

 I'm assuming everyone has had a chance to test the Gerrit installation
 at test.code.wireshark.org If you haven't, now might be a good time.


 Had the chance to, perhaps, but haven't yet.  I'm not sure I saved the old
 emails about it, and http://www.wireshark.org/develop.html just points to a
 svn and a git clone repository.

 For those of us who were sleeping that day in class, what's the best way to
 get up to speed on this?

The two relevant emails I've been (more-or-less) following are:
- the initial announce from Gerald:
https://www.wireshark.org/lists/wireshark-dev/201309/msg00188.html
- handy quick-start instructions from Marc:
https://www.wireshark.org/lists/wireshark-dev/201309/msg00191.html
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe