[PATCH]URL is unavailable

[PATCH]URL is unavailable

[Leonard Tse]

I found this URL "http://userweb.kernel.org/~akpm/stuff/tpp.txt" which in

Documentation/HOWTO

at Line 115
at Line 582

is just unavailable.

There are still instances of that living in :
Documentation/SubmittingPatches
Documentation/zh_CN/HOWTO
Documentation/zh_CN/SubmittingPatches
Documentation/ko_KR/HOWTO
Documentation/ja_JP/HOWTO
Documentation/ja_JP/SubmittingPatches
Relevant maintainers CC'ed

Please update or delete it.

Reference: https://lkml.org/lkml/2008/10/10/450

Re: [PATCH]URL is unavailable

[Borislav Petkov]

On Wed, Sep 12, 2012 at 11:51:35PM +0800, Leonard Tse wrote:
> I found this URL "http://userweb.kernel.org/~akpm/stuff/tpp.txt" which in
> 
> Documentation/HOWTO
> 
> at Line 115
> at Line 582
> 
> is just unavailable.

Dear KORG admins, what are the chances of userweb.kernel.org coming back
online?

Thanks.

-- 
Regards/Gruss,
Boris.

Re: [PATCH]URL is unavailable

[Leonard Tse]

2012/9/13 Borislav Petkov <bp@alien8.de>:
> On Wed, Sep 12, 2012 at 11:51:35PM +0800, Leonard Tse wrote:
>> I found this URL "http://userweb.kernel.org/~akpm/stuff/tpp.txt" which in
>>
>> Documentation/HOWTO
>>
>> at Line 115
>> at Line 582
>>
>> is just unavailable.
>
> Dear KORG admins, what are the chances of userweb.kernel.org coming back
> online?
>
> Thanks.
>
> --
> Regards/Gruss,
> Boris.

More unavailable URLs :

grep "userweb.kernel.org" . -r
./drivers/input/mouse/Kconfig:
http://userweb.kernel.org/~dtor/synaptics-no-abspressure.patch
./drivers/input/evdev.c:
"http://userweb.kernel.org/~dtor/eviocgbit-bug.html\n",
./Documentation/HOWTO:          http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/HOWTO:      http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/ja_JP/HOWTO:
http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/ja_JP/HOWTO:      http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/ja_JP/SubmittingPatches:http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz
./Documentation/ja_JP/SubmittingPatches:
<http://userweb.kernel.org/~akpm/stuff/tpp.txt>
./Documentation/SubmittingPatches:http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz
./Documentation/SubmittingPatches:
<http://userweb.kernel.org/~akpm/stuff/tpp.txt>
./Documentation/zh_CN/HOWTO:
http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/zh_CN/HOWTO:     http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/zh_CN/SubmittingPatches:http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz
./Documentation/zh_CN/SubmittingPatches:
<http://userweb.kernel.org/~akpm/stuff/tpp.txt>
./Documentation/ko_KR/HOWTO:
http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/ko_KR/HOWTO:    http://userweb.kernel.org/~akpm/stuff/tpp.txt
./Documentation/development-process/2.Process:
http://userweb.kernel.org/~akpm/mmotm/

Please check and update them, thanks.

Re: [PATCH]URL is unavailable

[Konstantin Ryabitsev]

[-- Attachment #1: Type: text/plain, Size: 731 bytes --]

On 12/09/12 12:03 PM, Borislav Petkov wrote:
> Dear KORG admins, what are the chances of userweb.kernel.org coming back
> online?

Hello:

There is no ETA on that service being available. It may not ever come
back, at least not in the way it was before.

That being said, I'm perfectly willing to set up a few redirects in
place if broken URLs are causing problems. I just cannot use any of the
existing backups of userweb data, as it is under a strict "do not use,
ever" quarantine.

If someone can provide me with trusted backups of that data, I will
provide hosting and redirects to unbreak the URLs.

Best,
-- 
Konstantin Ryabitsev
Systems Administrator
Linux Foundation, kernel.org
Montréal, Québec


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 726 bytes --]

Re: [PATCH]URL is unavailable

[Borislav Petkov]

On Wed, Sep 12, 2012 at 09:13:50PM -0400, Konstantin Ryabitsev wrote:
> On 12/09/12 12:03 PM, Borislav Petkov wrote:
> > Dear KORG admins, what are the chances of userweb.kernel.org coming back
> > online?
> 
> Hello:
> 
> There is no ETA on that service being available. It may not ever come
> back, at least not in the way it was before.
> 
> That being said, I'm perfectly willing to set up a few redirects in
> place if broken URLs are causing problems. I just cannot use any of the
> existing backups of userweb data, as it is under a strict "do not use,
> ever" quarantine.
> 
> If someone can provide me with trusted backups of that data, I will
> provide hosting and redirects to unbreak the URLs.

My memory is hazy on this, but after the move, what's the policy on
enabling users.kernel.org or userweb.kernel org or some other user web
serving thing? I vaguely remember that we don't want to do this anymore
but I'm not sure.

In any case, if we do, it would probably be better to have a whole
different machine for such stuff and let users upload their stuff again
without touching the old backups at all...

Hmm.

-- 
Regards/Gruss,
    Boris.

Re: [PATCH]URL is unavailable

[Konstantin Ryabitsev]

[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]

On 13/09/12 05:32 AM, Borislav Petkov wrote:
> My memory is hazy on this, but after the move, what's the policy on
> enabling users.kernel.org or userweb.kernel org or some other user web
> serving thing? I vaguely remember that we don't want to do this anymore
> but I'm not sure.

Well, as such system would be the largest security risk, it's
understandable that we're, err... reticent to have it up anywhere near
the rest of the infrastructure. :) We do have ssh enabled on two systems
that require git and release management, but anyone ssh'ing in never
gets a real shell and is severely locked down with SELinux.

> In any case, if we do, it would probably be better to have a whole
> different machine for such stuff and let users upload their stuff again
> without touching the old backups at all...

A better question is -- what is the problem we are trying to solve? We
are not in the business of providing free web hosting -- our aim is to
facilitate kernel development. We already provide a mechanism for git
trees and release tarballs. What is lacking is a simple way to publish
documentation -- it can be currently done with kup, but it's poorly
suited for uploading and managing many small files.

We already have a skeleton implementation of pulling such docs from git
trees (e.g. git docs are published that way). It's on my list of things
to extend this to a more universal and versatile system that would make
it easy for anyone to publish arbitrary documentation via their git
access -- perhaps on a subdomain like docs.kernel.org/treename/[etc]. We
can even require the use of "git tag -s" -- this will give us both
adequate security and history of changes.

I think this would be a better approach than allowing unfettered ssh
access and upload of arbitrary files.

Regards,
-- 
Konstantin Ryabitsev
Systems Administrator
Linux Foundation, kernel.org
Montréal, Québec


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 726 bytes --]

Re: [PATCH]URL is unavailable

[Borislav Petkov]

On Thu, Sep 13, 2012 at 09:35:43AM -0400, Konstantin Ryabitsev wrote:
> On 13/09/12 05:32 AM, Borislav Petkov wrote:
> > My memory is hazy on this, but after the move, what's the policy on
> > enabling users.kernel.org or userweb.kernel org or some other user web
> > serving thing? I vaguely remember that we don't want to do this anymore
> > but I'm not sure.
> 
> Well, as such system would be the largest security risk, it's
> understandable that we're, err... reticent to have it up anywhere near
> the rest of the infrastructure. :) We do have ssh enabled on two systems
> that require git and release management, but anyone ssh'ing in never
> gets a real shell and is severely locked down with SELinux.
> 
> > In any case, if we do, it would probably be better to have a whole
> > different machine for such stuff and let users upload their stuff again
> > without touching the old backups at all...
> 
> A better question is -- what is the problem we are trying to solve? We
> are not in the business of providing free web hosting -- our aim is to
> facilitate kernel development. We already provide a mechanism for git
> trees and release tarballs. What is lacking is a simple way to publish
> documentation -- it can be currently done with kup, but it's poorly
> suited for uploading and managing many small files.
> 
> We already have a skeleton implementation of pulling such docs from git
> trees (e.g. git docs are published that way). It's on my list of things
> to extend this to a more universal and versatile system that would make
> it easy for anyone to publish arbitrary documentation via their git
> access -- perhaps on a subdomain like docs.kernel.org/treename/[etc]. We
> can even require the use of "git tag -s" -- this will give us both
> adequate security and history of changes.
> 
> I think this would be a better approach than allowing unfettered ssh
> access and upload of arbitrary files.

You're right, I agree with all that but what happens if someone wants
to really upload an arbitrary file - say a tarball of stuff he's been
working on but it is not ready for a repo yet. Or a microcode blob or
whatever. Or even a doctored picture of Alan Cox celebrating the queen
:-)

I think this was the main reason behind userweb but I guess we're better
off finding different storage for stuff like that now.

Thanks.

-- 
Regards/Gruss,
Boris.