[Discussion] passwords

Cheng Eu Chew renedox at gmail.com
Wed Feb 22 17:14:28 NZDT 2012


Not so much about security unless you are talking about the security in
knowing that there will be a computer for use which people haven't screwed
around with. But that's symantics.
On Feb 22, 2012 5:09 PM, "Abhishek Reddy" <mail at abhishek.geek.nz> wrote:

> Yes. I like this solution because it knocks out two birds at once:
>
>  * There is always a computer that's available for read-only use. This is
> important for equitable access, since not all of us are always interested
> in, or able to, fix up a computer system that's been fooled with.
>  * There is always a computer that's available for tinkering. To me, it
> wouldn't be a hackerspace if this wasn't possible, even for casual members
> or visitors. I believe the self-repair manifesto hanging on the wall
> applies directly to our common tools and resources, and especially suits
> computers.
>
> In general, I'm sceptical of any security theatre though. If we were doing
> this in the name of security, we could be on a slippery slope.
>
> Cheers
>
> On Wed, Feb 22, 2012 at 4:25 PM, Cheng Eu Chew <renedox at gmail.com> wrote:
>
>> I believe that is the current plan - once we do actually get the
>> computer from Abhishek. As I understood it anyway.
>>
>> One computer for general web surfing and use - relatively locked down
>> but kept at a usable state and "guaranteed" internet connectivity.
>> Another computer, also free access, for people to do other things like
>> dev and other crap - which also includes web surfing.
>>
>> Cheng Eu Chew
>> _________________________________________________
>> Email : renedox at gmail.com
>> Mobile : +64220810098
>>
>>
>>
>> On 22 February 2012 16:21, Robin Paulson <robin at bumblepuppy.org> wrote:
>> >  On Wed, 22 Feb 2012 15:53:00 +1300, Jaco van der Merwe - Workshop
>> >  Enterprises Ltd. wrote:
>> >> Sounds like a sensible approach - that machine was due for a scratch
>> >> anyway.
>> >>
>> >> So, set up an unprivileged  guest account (named "guest")  for
>> >> general
>> >> use & other users with real logins?
>> >
>> >  for the general use machine?
>> >
>> >  the suggestion was to have one account, no root access. then alan has
>> >  root access and maintains it in a 'good' state
>> >
>> >  the likelihood of people switching account for their use is pretty low,
>> >  it generally gets used by each person for a web search or two/website
>> >  update for maybe 10 minutes max. - but i might be wrong. also, I
>> >  personally wouldn't be prepared to do too much administration on it,
>> >  there's far more interesting stuff to do at tangle ball.
>> >
>> >  for the 'dev' machine from abhishek? maybe one account, with sudo
>> >  access, password written on the front. use it for anything, be prepared
>> >  to re-format and install again in 6 months.
>> >
>> > --
>> >  robin
>> >
>> >  http://fu.ac.nz - Auckland's Free University
>> > _______________________________________________
>> > Discussion mailing list
>> > Discussion at tangleball.org.nz
>> > http://www.tangleball.org.nz/mailman/listinfo/discussion
>> _______________________________________________
>> Discussion mailing list
>> Discussion at tangleball.org.nz
>> http://www.tangleball.org.nz/mailman/listinfo/discussion
>>
>
>
>
> --
> Abhishek Reddy
> http://abhishek.geek.nz
>
>
> _______________________________________________
> Discussion mailing list
> Discussion at tangleball.org.nz
> http://www.tangleball.org.nz/mailman/listinfo/discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tangleball.org.nz/pipermail/discussion/attachments/20120222/07eae68b/attachment.htm 


More information about the Discussion mailing list