|
Grex > Coop13 > #365: The Staff and Board Alert Item | |
|
| Author |
Message |
| 8 new of 92 responses total. |
slynne
|
|
response 85 of 92:
|
Oct 14 15:01 UTC 2006 |
resp:83 Cross, that is great! What do you want to do and what do you
need to do it? I cant promise anything to you other than to bring it up
with the board but you'll need board approval if you need root anyways.
resp:84 Ok then. It would be a big help to have the staff describe the
specific aspects of their grex work and determine which work is high
priority. It would be an even bigger help to find a volunteer who is
willing to learn at least the high-priority items. Setting up the
meeting and the training timetable is a nice touch too. If you are
willing to do that stuff, I would LOVE it. It would be good for Grex and
I am most willing to ask the board to authorize you to do it.
|
gelinas
|
|
response 86 of 92:
|
Oct 15 00:29 UTC 2006 |
(He wants to change the password-hashing algorithm, at least as a start,
Lynne. ;)
|
cross
|
|
response 87 of 92:
|
Oct 15 00:41 UTC 2006 |
Joe's right, I do want to change that. I'm pretty disappointed that
discussion about it has stopped in garage (and I would assume the staff
conference and mailing list, too). But I also want to update grexsrc and
work on getting a local grexdoc that's mirrorable to remote systems via some
standard protocol (cvsup, cvsync, etc). Ultimately, a merge of grexdoc and
grexsoft would be nice. Getting an updated newuser running would be nice; I
found - and fixed - lots of bugs in my private version derived from the
sources running on grex. Removing unused code and support for absolutely
ancient operating systems (4.2BSD [ca. 1983], Ultrix, AIX version 3,
NeXTstep) and just focusing on POSIX+a simple system dependent library as a
target environment reduced line counts by a third; I figure I can strip out
another 1,000 or so lines by simplifying and correcting some of the logic.
There's at least one faily major security hole lurking in newuser which,
only due to a misconfiguration, isn't exploitable on grex at the moment. I
think working towards a viable replacement for Picospan is a worthy goal.
Like Cyklone, I think process is important and it would be well to impose
some on grex.
Yes, root access would be required for a lot of this.
|
tod
|
|
response 88 of 92:
|
Oct 15 00:49 UTC 2006 |
3DES..then the hard stuff
|
slynne
|
|
response 89 of 92:
|
Oct 15 02:25 UTC 2006 |
resp:87 Ok, I'll admit that I dont understand most of that. But, I will
print it out and will bring it up at the next board meeting where I am
sure at least some of my fellow board members will know what it means. I
will let you know the outcome of that discussion shortly after the
meeting which is in just under two weeks.
|
cyklone
|
|
response 90 of 92:
|
Oct 15 03:53 UTC 2006 |
"I'll admit that I dont understand most of that." Now you now how I feel ;)
I'm glad you're bringing it up for discussion. IMNSHO, that's exactly the kind
of thing the board should be looking at. Thanks.
|
naftee
|
|
response 91 of 92:
|
Oct 15 18:06 UTC 2006 |
re 88
not alcohol, silly !
|
cross
|
|
response 92 of 92:
|
Oct 16 02:34 UTC 2006 |
Regarding #89; Okay, Thanks.
|