Re: Ubuntu derivative package naming guidelines
hi to all > As such, I would like to discuss some package naming guidelines for > Ubuntu based derivatives. maybe we should have a dedicated mailing list (ubuntu-derivatives-devel :-) ) but anyway coming to the point of discussion, I think I would: - build my own repository - build my package - creating mydistro-desktop based on ubuntu desktop forcing the add of the new created package point is, if i rebuild gaim, how can i version it? i want my "gaim package release" to be taken/upgraded only from my repository and not from the officials... cheers! -- Fabrizio Balliano CREALABS SNC Via G. F. Medail, 32 - 10144 Torino - Italy Tel. (+39) 011.094.41.10 - Fax (+39) 178.227.63.81 http://www.crealabs.it - [EMAIL PROTECTED] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Open Port Indicator?
On Thu, 2007-15-03 at 14:14 +0100, Soren Hansen wrote:
> I asked for a use case where it made sense to allow access without any
> form of authentication.
>
> If no one comes up with a proper use case I'll just hack together a patch
> that makes it impossible.
There are at least four use cases, each of which requires a different
level of authentication/access.
UC1:Jen needs remote access to her machine. Remote authentication
should be (at least) the same as local authentication, i.e.,
userid and password. This should be the default option when
enabling Remote Desktop (e.g., "Enable remote desktop for known
users, or for known user X, userid and password required").
By default, this setting would persist across sessions. This
could be disabled, making it one time only (that is, until
logout or reboot).
As an improvement, there could be a time filter ("during these
hours only"), a domain filter (yes, spoofable, but perhaps of
value), an IP or Mac filter (ditto), etc.
UC2:Bif needs assistance with a problem and invites a remote friend
to connect and "drive", so Bif can watch and learn. In this
case, Remote Desktop could prompt the current local user to
enable the connection from the remote friend (e.g., an "Enable
remote assistance" option, where each connection is vetted by
the current local user ("Someone is accessing your machine from
A.B.C.D - do you wish to permit this connection?") "No" or no
answer within X seconds means no; yes means yes; a third option
could be yes, for Y minutes (max value 30, after 30, prompt
again).
When the current sessions ends (logout, reboot, etc.), Remote
Desktop returns to its default, disabled. In other words, if
Bif had previously enabled UC1, he must reenable explicitly
after using UC2.
UC3:Fritz is setting up a classroom or other contained environment,
and wishes to be able to access all local machines quickly and
easily (for whatever reason). He selects "Enable Remote Desktop
without authentication", is warned this is potentially risky,
and is then prompted to enter the shutoff time/period, i.e.,
the time/period after which Remote Access will be disabled and
will return to the default of no access.
Remote Access reverts to disabled after logout/reboot.
UC4:Barbara is a security researcher setting up a honeypot. She
wants to enable Remote Access without authentication. This is
a special case of UC3: No authentication, no time limit. She
selects no time/period, is asked to confirm this is what she
really meant, perhaps even twice, three times, whatever makes
us comfortable.
UC1 and UC2 would require no additional authentication (userid and
password in UC1, local confirmation in UC2). UC3 and UC4 could require
root privileges, e.g., require the use of gksudo. This would reduce the
likelihood of just some person taking advantage of an unlocked local
keyboard.
Alternatively, UC[1234] could require the user to authenticate
themselves when enabling the option, further reducing this risk.
pww
signature.asc
Description: This is a digitally signed message part
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Open Port Indicator?
On 16/03/07, Peter Whittaker <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-15-03 at 14:14 +0100, Soren Hansen wrote:
> > I asked for a use case where it made sense to allow access without any
> > form of authentication.
> >
> > If no one comes up with a proper use case I'll just hack together a patch
> > that makes it impossible.
>
> There are at least four use cases, each of which requires a different
> level of authentication/access.
>
> UC1:Jen needs remote access to her machine. Remote authentication
> should be (at least) the same as local authentication, i.e.,
> userid and password. This should be the default option when
> enabling Remote Desktop (e.g., "Enable remote desktop for known
> users, or for known user X, userid and password required").
>
> By default, this setting would persist across sessions. This
> could be disabled, making it one time only (that is, until
> logout or reboot).
>
> As an improvement, there could be a time filter ("during these
> hours only"), a domain filter (yes, spoofable, but perhaps of
> value), an IP or Mac filter (ditto), etc.
>
> UC2:Bif needs assistance with a problem and invites a remote friend
> to connect and "drive", so Bif can watch and learn. In this
> case, Remote Desktop could prompt the current local user to
> enable the connection from the remote friend (e.g., an "Enable
> remote assistance" option, where each connection is vetted by
> the current local user ("Someone is accessing your machine from
> A.B.C.D - do you wish to permit this connection?") "No" or no
> answer within X seconds means no; yes means yes; a third option
> could be yes, for Y minutes (max value 30, after 30, prompt
> again).
>
> When the current sessions ends (logout, reboot, etc.), Remote
> Desktop returns to its default, disabled. In other words, if
> Bif had previously enabled UC1, he must reenable explicitly
> after using UC2.
>
> UC3:Fritz is setting up a classroom or other contained environment,
> and wishes to be able to access all local machines quickly and
> easily (for whatever reason). He selects "Enable Remote Desktop
> without authentication", is warned this is potentially risky,
> and is then prompted to enter the shutoff time/period, i.e.,
> the time/period after which Remote Access will be disabled and
> will return to the default of no access.
>
> Remote Access reverts to disabled after logout/reboot.
>
> UC4:Barbara is a security researcher setting up a honeypot. She
> wants to enable Remote Access without authentication. This is
> a special case of UC3: No authentication, no time limit. She
> selects no time/period, is asked to confirm this is what she
> really meant, perhaps even twice, three times, whatever makes
> us comfortable.
>
> UC1 and UC2 would require no additional authentication (userid and
> password in UC1, local confirmation in UC2). UC3 and UC4 could require
> root privileges, e.g., require the use of gksudo. This would reduce the
> likelihood of just some person taking advantage of an unlocked local
> keyboard.
>
> Alternatively, UC[1234] could require the user to authenticate
> themselves when enabling the option, further reducing this risk.
>
I fail to see why UC[34] would require unauthenticated access.
Passwords do not take long to enter. I can enter my secure password in
around 1sec, no more than 2sec. And a simple password of say '123',
while not in any means secure is at least better than no
authentication at all. So speed of access is not a problem.
You are going to have to come up with a better reason, other that
"people don't want to enter password because they are too lazy", to
convince me that allowing unauthenticated access is a good idea.
Arwyn
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Open Port Indicator?
>> >> UC3:Fritz is setting up a classroom or other contained environment, >> and wishes to be able to access all local machines quickly and >> easily (for whatever reason). He selects "Enable Remote Desktop >> without authentication", is warned this is potentially risky, >> and is then prompted to enter the shutoff time/period, i.e., >> the time/period after which Remote Access will be disabled and >> will return to the default of no access. >> >> Remote Access reverts to disabled after logout/reboot. >> > > I fail to see why UC[34] would require unauthenticated access. > Passwords do not take long to enter. I can enter my secure password in > around 1sec, no more than 2sec. And a simple password of say '123', > while not in any means secure is at least better than no > authentication at all. So speed of access is not a problem. I think that the problem of Fritz is the fact that it is a priori not clear that there is a same account with the same pass on each machine. Maybe Fritz has configured the computers in such a way that the pass of the first is "314", the pass of the second is "159", the third "265" ... Fritz wants not to memorize 25 different passwords ! Of course, I think that the right solution is to set up the same pass on all the computers. Laurent -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Summer of Code student applications now open
Scott, I have a few projects up on the Ubuntu SoC project wiki page. I've already had a student contact me with interest in one of them (the revision-controlled home directories one). I told him I'd be happy to mentor him on that project, but that I need to figure out what is required for someone to be a mentor on behalf of Ubuntu. Am I eligible to do that? If so, what do I need to do before that's possible? Feel free to point me at a web page where I can RTFM the answers for myself. :) Thanks Scott. Wes On Mar 16, 2007, at 5:59 AM, Scott James Remnant wrote: > Join the Google Summer of Code with Ubuntu! > > Students Applications are open from now until March 23rd. > > We are looking for good, capable, eligible students to apply with > projects of their own desire, or those selected from our ideas page: > > http://wiki.ubuntu.com/GoogleSoC2007 > > (We are also looking for anyone with good ideas for SoC projects to > add > a description to that page.) > > > Google Summer of Code: > http://code.google.com/soc/ > > Summer of Code FAQ: > http://code.google.com/support/bin/topic.py?topic=10442 > > How to use the SoC web-app to register: > http://groups.google.com/group/google-summer-of-code-announce/web/ > guide-to-the-gsoc-web-app-for-student-applicants > > > > Feel free to contact Scott James Remnant or Matthias Klose, if you > require any further information. Please email > [EMAIL PROTECTED] > > Scott > -- > Scott James Remnant > Ubuntu Development Manager > [EMAIL PROTECTED] > -- > ubuntu-devel-announce mailing list > ubuntu-devel-announce@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
