Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 20:15, schrieb Mike Noyes: > On 12/19/2012 10:35 AM, KP Kirchdoerfer wrote: > -snip- >> Another flaw is that I sometimes get the option to "Log In" but none to >> "Log out". If I get the option to logout via menu I'll end up in >> "sourceforge.net" but not in the same space I logged out. > > Everyone, > There is a little drop-down menu in the upper right hand corner labeled > "Me" that you can use to logout and a couple of other things. On logout > you do get redirected to the SF home page, and the upper right hand > corner changes to "Log In". > Sorry, forgot to mention: IF I log out, I'd like to stay on the page, and not redirected. I guess this is a reasonable request, cause only members/admins can login and consequently logout, and more often they will have a users view of their page than redirected to SF home. kp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 20:15, schrieb Mike Noyes: > On 12/19/2012 10:35 AM, KP Kirchdoerfer wrote: > -snip- >> Another flaw is that I sometimes get the option to "Log In" but none to >> "Log out". If I get the option to logout via menu I'll end up in >> "sourceforge.net" but not in the same space I logged out. > > Everyone, > There is a little drop-down menu in the upper right hand corner labeled > "Me" that you can use to logout and a couple of other things. On logout > you do get redirected to the SF home page, and the upper right hand > corner changes to "Log In". > I'm aware of it. And I do see this some times - but sometimes I only see "Log In" which isn't the dropdown menu but only a link to https://sourceforge.net/account/login.php So it's non consistent. BTW I'm using he latest stable FF. kp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 10:35 AM, KP Kirchdoerfer wrote: -snip- > Another flaw is that I sometimes get the option to "Log In" but none to > "Log out". If I get the option to logout via menu I'll end up in > "sourceforge.net" but not in the same space I logged out. Everyone, There is a little drop-down menu in the upper right hand corner labeled "Me" that you can use to logout and a couple of other things. On logout you do get redirected to the SF home page, and the upper right hand corner changes to "Log In". -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 10:35 AM, KP Kirchdoerfer wrote: > the allura git browser is a pain. > > I've checked again, and now, regardless if logged in or out, I do have > the same issues as above when I click "History". > > Another flaw is that I sometimes get the option to "Log In" but none to > "Log out". If I get the option to logout via menu I'll end up in > "sourceforge.net" but not in the same space I logged out. > > And even more worse, I've seen today it almostly worked, but either it's > a UI issue and I can't find it, or it fails too often. > Either way it really needs some hands on to be on par with the old cgi > page. > > With the working commit-mailinglist and a local git browser it should be > possible to work around the issues. Shurely not your fault, but > hopefully your contacts to SF team will help to solve the remaining issues. KP, I forwarded your comments to Rich Bowen a.k.a. DrBacchus on irc. -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 15:27, schrieb KP Kirchdoerfer:
> Am 19.12.2012 14:47, schrieb Mike Noyes:
>> On 12/19/2012 01:36 AM, KP Kirchdoerfer wrote:
>>> Am 17.12.2012 14:58, schrieb Mike Noyes:
On 12/17/2012 03:17 AM, Yves Blusseau wrote:
> Hi all,
>
> i see some commits that has been done in the old git repository:
>
> $ git cherry -v origin/master old/master
> + 7127babead986725fc128e9acc7b1c5a08fa44d8 kernel update to 3.2.35
> + b3b98c475e6392a92951c3b29445d3db86c9a7f6 add verification with gpgv
>
> I have merge the changes in the new git repository but don't forget to
> change the URL of the new git repository with a command like this:
>
> git remote set-url origin
> ssh://yourn...@git.code.sf.net/p/leaf/bering-uclibc
Yves,
Thanks for catching this issue.
>>>
>>> Hi;
>>>
>>> does this mean
>>>
>>> http://leaf.git.sourceforge.net/git/gitweb.cgi?p=leaf/bering-uclibc;a=summary
>>>
>>> is outdated?
>>
>> KP,
>> Yes.
>>
>>> And the new URL to browse the git repository is this one?
>>> http://sourceforge.net/p/leaf/bering-uclibc/commit_browser
>>
>> Correct.
>>
>>> In that case it seems not to be updated, the latest commits by Yves are
>>> not shown.
>>
>> I see three commits [ce11cc], [18e8f8] and, [17fa94]) from Yves two days
>> ago.
>
> My fault.
>
>> I also see the two [5edf97], and [25b53c] from you today.
>
> When logged in and trying to follow the links I get an error message
> from SF ("Oops, looks like something went wrong"). It works if I'm not
> logged in.
Hi Mike;
the allura git browser is a pain.
I've checked again, and now, regardless if logged in or out, I do have
the same issues as above when I click "History".
Another flaw is that I sometimes get the option to "Log In" but none to
"Log out". If I get the option to logout via menu I'll end up in
"sourceforge.net" but not in the same space I logged out.
And even more worse, I've seen today it almostly worked, but either it's
a UI issue and I can't find it, or it fails too often.
Either way it really needs some hands on to be on par with the old cgi
page.
With the working commit-mailinglist and a local git browser it should be
possible to work around the issues. Shurely not your fault, but
hopefully your contacts to SF team will help to solve the remaining issues.
kp
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] proposing a timeframe and features for 5.0-alpha2
Hi Gents; I'd like to make a proposal for the timeframe and features of the second alpha version of 5.0. First of all, I think it should still be an alpha version - so neither the kernel nor the uClibc are fixed. Also the major goal for 5.0 to support other cpu architectures misses at least one image/example. We saw over 100 downloads of alpha1 and received no complaints so far, so I consider for X86_32 even an alpha1 version was not bad. Along with usual Package updates and fixes, the new features for the second alpha could be a X86_64 image and to "enable" zram support at least, and eventually offering signed packages. As far as I'm aware a X86_64 version currently needs - a patch for vsftpd - a solution for the uClibc loader (lib/ld-uClibc-0.9.33.2.so vs lib/ld64-uClibc-0.9.33.2.so - and images (AFAIR it worked without changes) About zram support, I've lost track about it's status. I know some changes has been made in master (like swap support in the kernel), others seems to be merged into next branch (like changes to conf/images/common/leaf.cfg) - don't know what other changes ended in which repository..., and finally it lacks any documentation how to enable and to make use of it. While I hope for everyone to have a good time at beaches in the sun like Curacao, it may happen that you are still at home over the the next weeks and probably have some time - so a timeframe for alpha2 might be 6th of January. Just ideas YMMV kp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 16:25, schrieb Mike Noyes: > On 12/19/2012 07:14 AM, KP Kirchdoerfer wrote: >> Am 19.12.2012 16:01, schrieb Mike Noyes: >>> On 12/19/2012 06:40 AM, Mike Noyes wrote: On 12/19/2012 06:27 AM, KP Kirchdoerfer wrote: > Am 19.12.2012 14:47, schrieb Mike Noyes: -snip- >>> Also the commit message has some small errors, like refering to "UNNAMED >>> Project". >> >> Where are you seeing this? > > In the mails sent to leaf-cimmit mailinglist. KP, Verified. Thanks. This is a problem with the git mailing list commit config. I'm looking into the problem now. >>> >>> KP, >>> Fixed. Allura git migration failed to copy description files. Thanks for >>> catching that. >>> >> >> I see- thanks. Almost perfect, what about a capital first letter for >> Bering-uClibc :) > > KP, > Done. I just copied the exact text from my backup prior to migration. I > guess that minor issue is in every prior commit message. Anyway, fixed now. > I saw myself after sending the message, thx for taking care of even such minor issues. kp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 07:14 AM, KP Kirchdoerfer wrote: > Am 19.12.2012 16:01, schrieb Mike Noyes: >> On 12/19/2012 06:40 AM, Mike Noyes wrote: >>> On 12/19/2012 06:27 AM, KP Kirchdoerfer wrote: Am 19.12.2012 14:47, schrieb Mike Noyes: >>> -snip- >> Also the commit message has some small errors, like refering to "UNNAMED >> Project". > > Where are you seeing this? In the mails sent to leaf-cimmit mailinglist. >>> >>> KP, >>> Verified. Thanks. This is a problem with the git mailing list commit >>> config. I'm looking into the problem now. >> >> KP, >> Fixed. Allura git migration failed to copy description files. Thanks for >> catching that. >> > > I see- thanks. Almost perfect, what about a capital first letter for > Bering-uClibc :) KP, Done. I just copied the exact text from my backup prior to migration. I guess that minor issue is in every prior commit message. Anyway, fixed now. -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 16:01, schrieb Mike Noyes: > On 12/19/2012 06:40 AM, Mike Noyes wrote: >> On 12/19/2012 06:27 AM, KP Kirchdoerfer wrote: >>> Am 19.12.2012 14:47, schrieb Mike Noyes: >> -snip- > Also the commit message has some small errors, like refering to "UNNAMED > Project". Where are you seeing this? >>> >>> In the mails sent to leaf-cimmit mailinglist. >> >> KP, >> Verified. Thanks. This is a problem with the git mailing list commit >> config. I'm looking into the problem now. > > KP, > Fixed. Allura git migration failed to copy description files. Thanks for > catching that. > I see- thanks. Almost perfect, what about a capital first letter for Bering-uClibc :) kp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 06:40 AM, Mike Noyes wrote: > On 12/19/2012 06:27 AM, KP Kirchdoerfer wrote: >> Am 19.12.2012 14:47, schrieb Mike Noyes: > -snip- Also the commit message has some small errors, like refering to "UNNAMED Project". >>> >>> Where are you seeing this? >> >> In the mails sent to leaf-cimmit mailinglist. > > KP, > Verified. Thanks. This is a problem with the git mailing list commit > config. I'm looking into the problem now. KP, Fixed. Allura git migration failed to copy description files. Thanks for catching that. -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 06:27 AM, KP Kirchdoerfer wrote: > Am 19.12.2012 14:47, schrieb Mike Noyes: -snip- >>> Also the commit message has some small errors, like refering to "UNNAMED >>> Project". >> >> Where are you seeing this? > > In the mails sent to leaf-cimmit mailinglist. KP, Verified. Thanks. This is a problem with the git mailing list commit config. I'm looking into the problem now. -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 15:28, schrieb Mike Noyes: > On 12/19/2012 05:46 AM, Yves Blusseau wrote: >> Le 19 déc. 2012 à 10:36, KP Kirchdoerfer a >> écrit : >>> And the new URL to browse the git repository is this one? >>> http://sourceforge.net/p/leaf/bering-uclibc/commit_browser >>> >> >> Using this url: >> https://sourceforge.net/p/leaf/bering-uclibc/ci/master/log/?path= seems good > > Everyone, > I'm seeing some issues with the Allura 'Browse Commits' page for our > bering-uclibc repository. > > https://sourceforge.net/p/leaf/bering-uclibc/commit_browser > > Intermittent failure to return with commit details. Can anyone else > verify this issue? > > Loading commit details... Yes, I have this pb also. kp > For comparison see: > > https://sourceforge.net/p/leaf/code/commit_browser > https://sourceforge.net/p/leaf/packages/commit_browser > -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 05:46 AM, Yves Blusseau wrote: > Le 19 déc. 2012 à 10:36, KP Kirchdoerfer a > écrit : >> And the new URL to browse the git repository is this one? >> http://sourceforge.net/p/leaf/bering-uclibc/commit_browser >> > > Using this url: > https://sourceforge.net/p/leaf/bering-uclibc/ci/master/log/?path= seems good Everyone, I'm seeing some issues with the Allura 'Browse Commits' page for our bering-uclibc repository. https://sourceforge.net/p/leaf/bering-uclibc/commit_browser Intermittent failure to return with commit details. Can anyone else verify this issue? Loading commit details... For comparison see: https://sourceforge.net/p/leaf/code/commit_browser https://sourceforge.net/p/leaf/packages/commit_browser -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 19.12.2012 14:47, schrieb Mike Noyes:
> On 12/19/2012 01:36 AM, KP Kirchdoerfer wrote:
>> Am 17.12.2012 14:58, schrieb Mike Noyes:
>>> On 12/17/2012 03:17 AM, Yves Blusseau wrote:
Hi all,
i see some commits that has been done in the old git repository:
$ git cherry -v origin/master old/master
+ 7127babead986725fc128e9acc7b1c5a08fa44d8 kernel update to 3.2.35
+ b3b98c475e6392a92951c3b29445d3db86c9a7f6 add verification with gpgv
I have merge the changes in the new git repository but don't forget to
change the URL of the new git repository with a command like this:
git remote set-url origin
ssh://yourn...@git.code.sf.net/p/leaf/bering-uclibc
>>>
>>> Yves,
>>> Thanks for catching this issue.
>>>
>>
>> Hi;
>>
>> does this mean
>>
>> http://leaf.git.sourceforge.net/git/gitweb.cgi?p=leaf/bering-uclibc;a=summary
>>
>> is outdated?
>
> KP,
> Yes.
>
>> And the new URL to browse the git repository is this one?
>> http://sourceforge.net/p/leaf/bering-uclibc/commit_browser
>
> Correct.
>
>> In that case it seems not to be updated, the latest commits by Yves are
>> not shown.
>
> I see three commits [ce11cc], [18e8f8] and, [17fa94]) from Yves two days
> ago.
My fault.
> I also see the two [5edf97], and [25b53c] from you today.
When logged in and trying to follow the links I get an error message
from SF ("Oops, looks like something went wrong"). It works if I'm not
logged in.
>
>> Also the commit message has some small errors, like refering to "UNNAMED
>> Project".
>
> Where are you seeing this?
In the mails sent to leaf-cimmit mailinglist.
kp
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
On 12/19/2012 01:36 AM, KP Kirchdoerfer wrote: > Am 17.12.2012 14:58, schrieb Mike Noyes: >> On 12/17/2012 03:17 AM, Yves Blusseau wrote: >>> Hi all, >>> >>> i see some commits that has been done in the old git repository: >>> >>> $ git cherry -v origin/master old/master >>> + 7127babead986725fc128e9acc7b1c5a08fa44d8 kernel update to 3.2.35 >>> + b3b98c475e6392a92951c3b29445d3db86c9a7f6 add verification with gpgv >>> >>> I have merge the changes in the new git repository but don't forget to >>> change the URL of the new git repository with a command like this: >>> >>> git remote set-url origin >>> ssh://yourn...@git.code.sf.net/p/leaf/bering-uclibc >> >> Yves, >> Thanks for catching this issue. >> > > Hi; > > does this mean > > http://leaf.git.sourceforge.net/git/gitweb.cgi?p=leaf/bering-uclibc;a=summary > > is outdated? KP, Yes. > And the new URL to browse the git repository is this one? > http://sourceforge.net/p/leaf/bering-uclibc/commit_browser Correct. > In that case it seems not to be updated, the latest commits by Yves are > not shown. I see three commits [ce11cc], [18e8f8] and, [17fa94]) from Yves two days ago. I also see the two [5edf97], and [25b53c] from you today. > Also the commit message has some small errors, like refering to "UNNAMED > Project". Where are you seeing this? -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Le 19 déc. 2012 à 10:36, KP Kirchdoerfer a écrit : > Am 17.12.2012 14:58, schrieb Mike Noyes: >> On 12/17/2012 03:17 AM, Yves Blusseau wrote: >>> Hi all, >>> >>> i see some commits that has been done in the old git repository: >>> >>> $ git cherry -v origin/master old/master >>> + 7127babead986725fc128e9acc7b1c5a08fa44d8 kernel update to 3.2.35 >>> + b3b98c475e6392a92951c3b29445d3db86c9a7f6 add verification with gpgv >>> >>> I have merge the changes in the new git repository but don't forget to >>> change the URL of the new git repository with a command like this: >>> >>> git remote set-url origin >>> ssh://yourn...@git.code.sf.net/p/leaf/bering-uclibc >> >> Yves, >> Thanks for catching this issue. >> > > Hi; > > does this mean > > http://leaf.git.sourceforge.net/git/gitweb.cgi?p=leaf/bering-uclibc;a=summary > > is outdated? > Yes i think. Mike ? > And the new URL to browse the git repository is this one? > http://sourceforge.net/p/leaf/bering-uclibc/commit_browser > Using this url: https://sourceforge.net/p/leaf/bering-uclibc/ci/master/log/?path= seems good Regards, Yves -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF ticket 57
Hi Erich; Am 19.12.2012 00:47, schrieb Erich Titl: > Hi KP > > I am writing this in a warm evening breeze on the island of Curaçao, so > if anything is fuzzy blame it on the local rhum. Sounds good, I've catched a flu instead, so blame the fevered mind :) > Am 18.12.2012 15:07, schrieb KP Kirchdoerfer: >> Hi Erich; >> >> Am 16.12.2012 19:50, schrieb Erich Titl: >>> Hi KP >>> >>> Am 16.12.2012 11:12, schrieb KP Kirchdoerfer: Am 15.12.2012 23:14, schrieb Erich Titl: > Hi KP > > Am 15.12.2012 19:54, schrieb KP Kirchdoerfer: >> Hi; >> >> I did some work on Trac ticket 57 "add gpg signing of packages", and >> like to discuss, what I've done so far. > > Will it still be possible to load unsigned packages? Yes. Currently verify is not integrated into the install or update commands. The user *can* download a gpg signature file for a given lrp and verify the package before he installs/updates it. It's recommended, but everything else will work as before. >>> >>> I have a few more doubts >>> >>> If the verify mechanism is built into config.lrp then it is easy to >>> circumvent it, by just disabling it there. This is even easier than in >>> in initrd. >> >> The idea is to follow this route: >> http://www.apache.org/dev/release-signing.html > > I have not read it all and probably understood less. > > It depends on what we want to achieve with signing the package > > 1) We want tomake sure, the package has been created by someone in > possession of the signing key Yes, that's the current goal! As a (small) step to improve security. Maybe a step forward to 2) in the long run, but as you outline, this will be very hard if not impossible. E.g. if a hacker get's access to your box, he should be able to add his own key along with malicious packages..., There is simply a point where the user has to take responsibility for his box. kp > 2) We want to make sure only signed packages with a known key are loaded > > The first is very easy to achieve, the second IMHO is very hard. > > 1) verifying the signature and thus verifying that packages come from a > certified source is easy > 2) making sure only signed packages can be loaded is hard, as it > requires the package loader to be hardened against an attack. > > The actual cryptographic routines are standard and are available on the net. > > The problems come from the format of the packages. As long as they are > simple gzipped tar files one can do almost anything with it, the easiest > to get around the signing stuff is to use an old config.lrp :-( > > The organizational structure around the trust is important, but IMHO not > the most important at this time. > > I have not looked into the recent version of the package loader andd I > am not proficient enough to suggest a safe way to make sure only > official versions of the package loader would be accepted. It might need > compiled_in kernel function to make sure only a qualified package loader > can be used. > > But all this is only needed if we want to protect the software against > the wiry hacker, just for verifying the packages this is not needed. > > cheers > > Erich > > > -- > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > ___ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel > -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Don't forget to change your git configuration
Am 17.12.2012 14:58, schrieb Mike Noyes: > On 12/17/2012 03:17 AM, Yves Blusseau wrote: >> Hi all, >> >> i see some commits that has been done in the old git repository: >> >> $ git cherry -v origin/master old/master >> + 7127babead986725fc128e9acc7b1c5a08fa44d8 kernel update to 3.2.35 >> + b3b98c475e6392a92951c3b29445d3db86c9a7f6 add verification with gpgv >> >> I have merge the changes in the new git repository but don't forget to >> change the URL of the new git repository with a command like this: >> >> git remote set-url origin ssh://yourn...@git.code.sf.net/p/leaf/bering-uclibc > > Yves, > Thanks for catching this issue. > Hi; does this mean http://leaf.git.sourceforge.net/git/gitweb.cgi?p=leaf/bering-uclibc;a=summary is outdated? And the new URL to browse the git repository is this one? http://sourceforge.net/p/leaf/bering-uclibc/commit_browser In that case it seems not to be updated, the latest commits by Yves are not shown. Also the commit message has some small errors, like refering to "UNNAMED Project". kp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
