Re: [josm-dev] OAuth secure ?
Am 29.04.2010 15:40, colliar: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ævar Arnfjörð Bjarmason schrieb: On Thu, Apr 29, 2010 at 12:04, colliarcolliar4e...@aol.com wrote: I thought at least with semi-automatic use OAuth was transfering with encryption ( and should also now with https) , but there is still a warning about no secure possibility on the wiki. Am I wrong or do we need to change this page. The wiki is wrong and needs to be brought up to date. Does that mean OAuth is now encrypted no matter which methode is used ? If so, we should lead the user to use OAuth and to not use the normal login at all, anymore. No, OAuth is not about encryption at all. The inital OAuth setup call still allows to be listened into and the login+password to be retrieved. All subsequent API calls won't transmit username+PW but the token instead, but still the content is transferred unencrypted. btw. which wiki (article) are you referring to? Claudius ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Open offer to convert JOSM to Git
Re: Git -my personal bias is to retain SVN because Git is not yet Windows-friendly, although there is at least one implementation that works somewhat on Windows. What you'd do is: 1. check out the repository on the mirror branch (default) 2. Add git-svn metadata: http://trac.parrot.org/parrot/wiki/git-svn-tutorial 3. branch from the mirror branch: git checkout mirror git checkout -b some/silly-branch-name 3. *hack on the train* 4. Use git-rebase to apply only your commits (none of the mirror stuff) to master 5. git svn dcommit ... So git-svn makes things a lot harder, since you're always speaking in a foreign language and translating between two fundamentally incompatible systems. If these steps are just lines in a shell command, it's all part of the pull - dev - push process.The JOSM development process normally doesn't include the killer advantage of distributed version control over SVN: branching and merging. The JOSM development hasn't typically branched, although there could be a small development on the v5 branch now if there are new killer bugs. ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Open offer to convert JOSM to Git
On 4/30/10 7:40 AM, Mike N. wrote: Re: Git -my personal bias is to retain SVN because Git is not yet Windows-friendly, although there is at least one implementation that works somewhat on Windows. by way of context, i'm not a josm developer, but i have about 10 years of java experience, and used git for version control in a consulting stint at Bank of America, which entailed developing on Windows XP while delivering to Solaris. what exactly is does not yet Windows-friendly mean exactly? the following is from my direct experience at the bank: 1) the git command line interface worked perfectly from cygwin. 2) secure access to our solaris git server worked perfectly over ssh 3) the gui tool gitk (built out on gtk, i believe) worked extremely well for viewing git development trees and commits, i used it quite heavily. 4) the git-gui tool (another gtk based app) seemed to work well for bread-and-butter git operations, although i generally just used the command line for the most part. so there are gui tools, is it that they're not native, and if so why does that disqualify them from being Windows-friendly? richard ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Open offer to convert JOSM to Git
Am 30.04.2010 14:55, Richard Welty: On 4/30/10 7:40 AM, Mike N. wrote: Re: Git -my personal bias is to retain SVN because Git is not yet Windows-friendly, although there is at least one implementation that works somewhat on Windows. by way of context, i'm not a josm developer, but i have about 10 years of java experience, and used git for version control in a consulting stint at Bank of America, which entailed developing on Windows XP while delivering to Solaris. what exactly is does not yet Windows-friendly mean exactly? the following is from my direct experience at the bank: (...) Not to forget a neat Windows explorer-integration based on TortoiseSVN called... *drumroll* TortoiseGIT: http://code.google.com/p/tortoisegit/ Claudius ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
