On Dec 3, 2007 7:40 AM, James Graves <ansible@...> wrote: > Mark Miller wrote: > > Is wiki.erights.org down? > > Yes it was. Rebooted now. I've really got to get going on that newer > hardware. Hi James, wiki.erights.org seems to be down again. If you need someone to volunteer hosting services, donate hardware, or whatever, please ask on e-lang. -- -- Text by me above is hereby placed in the public domain Cheers, --MarkM
Mark Miller wrote: > Hi James, wiki.erights.org seems to be down again. If you need someone > to volunteer hosting services, donate hardware, or whatever, please > ask on e-lang. Yes, it is down. I'm at home right now, so I can't restart it (lots of snow today). I should be able to drive into work later today and give it a kick. Hmmm... you know, I was planning on upgrading the OS and software... but I haven't had the time / gumption to get it set up and running. I apoligize for this. The quickest short-term solution would be to just copy the drive onto a new system. I'll try to do that ASAP. If someone else who has more time and energy would like to take over hosting the wiki, that would be fine too. Best regards, James
On Jan 27, 2008, at 14:32, John Carlson wrote: > On Jan 27, 2008, at 5:50 AM, Kevin Reid wrote: >> On Jan 27, 2008, at 4:16, John Carlson wrote: >>> Sigh. I guess if you want security, you need to install by hand? I >>> am looking at the pure java version. >> >> I find this comment confusing. Could you expand? >> >> What is the alternative to "wanting security" that you see? >> (Installing something else? Installing E by some other means?) >> What is significant about the pure java version? > > Well in the days of MSI, executable jars, .dmgs, ./configure, fink, > macports, apt-get etc, I don't expect to see a bunch of steps to > get software installed. (I'm moving this discussion to e-lang since it's specific to E.) A good point. I think I'll look into improving the situation. Could you point out where, in your view, the process becomes "a bunch of steps"? That is, did you run into a list of steps on the web site, or after you unpacked the download, or ...? Also, are you on Mac OS X? -- -- Kevin Reid <http://homepage.mac.com/kpreid/>
Hi all, The wiki is up and running on a slightly newer, slightly faster box. Ideally, we'd still upgrade to the latest OS, MediaWiki, etc. software, but that'll have to wait for another weekend. Next I'll work on that catchpa stuff next. I'm not going to promise a specific date though. ------------------------------------------------------------------- What do we want the policy to be with users and editing anyway? First, we tried just plain open (anonymous users can edit), and got some spam that way. We would revert the changes and also block that IP address. Next, we tried to require a user account to edit pages. And we got some spam that way (a lot). So we'd (*) ban the user, and revert the changes. However, with the current MediaWiki software, you don't easily see the IP address the user signed up with, because ideally we'd also just ban that IP as well. So I forget the details with the catchpa software... did we want to use that for signing up new accounts. Or for making any edits? Or for making only anonymous edits and allowing anonymous edits again? ---------------------------------------------------------------- Another option is to only allow account creation by the sysops. Right(Continue reading)
On Feb 2, 2008, at 17:37, James Graves wrote: > So I forget the details with the catchpa software... did we want to > use > that for signing up new accounts. Or for making any edits? Or for > making only anonymous edits and allowing anonymous edits again? I would suggest captchas for both account creation and anonymous editing; I'm not sure whether to allow anonymous editing. > Another option is to only allow account creation by the sysops. I think this is slightly too much of a barrier to entry, because it requires contacting a sysop. -- -- Kevin Reid <http://homepage.mac.com/kpreid/>
James Graves wrote: > > Next I'll work on that catchpa stuff next. I'm not going to promise a > specific date though. > You should use recaptcha (http://recaptcha.net/) instead. It gives the same protection as captchas and helps digitize books. I would require them for setting up an account and making anonymous edits. That way somone who doesn't edit often doesn't have to bother setting up an account. ________________________ Alan Karp Principal Scientist Virus Safe Computing Initiative Hewlett-Packard Laboratories 1501 Page Mill Road Palo Alto, CA 94304 (650) 857-3967, fax (650) 857-7029 http://www.hpl.hp.com/personal/Alan_Karp
Kevin Reid wrote: > I would suggest captchas for both account creation and anonymous > editing; I'm not sure whether to allow anonymous editing. With the current capability of the MediaWiki software we're using, I'm inclined to turn back on anonymous edits, just so that we can ban based on IPs again. >> Another option is to only allow account creation by the sysops. > > I think this is slightly too much of a barrier to entry, because it > requires contacting a sysop. This is definitely a concern. I'm still worried that even requiring an account to edit is too much a barrier to entry. But I have no way to easily measure that. James
ansible@... (James Graves) on Saturday, February 2, 2008 wrote: >> I think this is slightly too much of a barrier to entry, because it >> requires contacting a sysop. > >This is definitely a concern. I'm still worried that even requiring an >account to edit is too much a barrier to entry. But I have no way to >easily measure that. I can testify that it is a barrier to contribution. I promised almost a year ago to have a go at the KeyKOS entry in Widipedia. I kind of think that if I make major contributions, I should do it under some stable name, which means an account. On the other hand, I haven't set up an account for reasons that aren't justifiable, or even admitting to description, although I assure you they are quite real. Cheers - Bill ----------------------------------------------------------------------- Bill Frantz | I like the farmers' market | Periwinkle (408)356-8506 | because I can get fruits and | 16345 Englewood Ave www.pwpconsult.com | vegetables without stickers. | Los Gatos, CA 95032
Bill Frantz wrote: > ansible@... (James Graves) wrote: > >> This is definitely a concern. I'm still worried that even requiring an >> account to edit is too much a barrier to entry. But I have no way to >> easily measure that. > > I can testify that it is a barrier to contribution. I promised > almost a year ago to have a go at the KeyKOS entry in Widipedia. I > kind of think that if I make major contributions, I should do it > under some stable name, which means an account. On the other hand, > I haven't set up an account for reasons that aren't justifiable, or > even admitting to description, although I assure you they are quite > real. I think it in part has to do with managing yet another username / password. Since we are all good netizens, we will use a different password for distinct sites to prevent someone who breaks into one site from accessing our other accounts. So if you 'get around' to the extent that I do, it wouldn't be unusual to have over 100 of them. Most of these aren't terribly security critical, like my New York Times login. Conferences, blogs, developer sites, stupid little routers, wiki passwords (I have at least 6 of these), etc. They do tend to accumulate. Ah, but how to keep track of them? The thought of adding yet another is a little bit depressing to many people I suspect. I can only keep about(Continue reading)
On Mon, 2008-02-04 at 09:05 -0600, James Graves wrote: > Since we are all good netizens, we will use a different password for > distinct sites to prevent someone who breaks into one site from > accessing our other accounts. > > So if you 'get around' to the extent that I do, it wouldn't be unusual > to have over 100 of them. You want PassPet mate. http://www.passpet.org Speaking of which, does anyone on e-lang know when / if we're likely to see a PassPet release? I've been eagerly awaiting it since I read the SOUPS paper. In the meantime, you may be able to get mileage with Alan Karp's Password Safe, which appears to be a less feature-ful predecessor of PassPet. http://www.hpl.hp.co.uk/personal/Alan_Karp/site_password/index.html > P.S. Isn't obj-cap security supposed to fix all this?Instead of writing down 100 different passwords, you'll have 100 different bookmarked YURLs... But each site will probably then implement a YURL-recovery scheme for when you reinstall your machine and lose all of your bookmarks that's based on username/password ;)
RSS Feed2 | |
|---|---|
2 | |
2 | |
7 | |
52 | |
22 | |
4 | |
2 | |
1 | |
5 | |
4 | |
1 | |
6 | |
3 | |
8 | |
13 | |
16 | |
7 | |
9 | |
17 | |
10 | |
63 | |
9 | |
33 | |
36 | |
27 | |
15 | |
32 | |
13 | |
6 | |
13 | |
20 | |
36 | |
34 | |
40 | |
43 | |
50 | |
46 | |
7 | |
23 | |
54 | |
30 | |
33 | |
10 | |
39 | |
45 | |
71 | |
39 | |
26 | |
4 | |
16 | |
19 | |
47 | |
58 | |
42 | |
26 | |
44 | |
16 | |
167 | |
68 | |
38 | |
24 | |
52 | |
45 | |
62 | |
55 | |
30 | |
38 | |
49 | |
71 | |
73 | |
60 | |
99 | |
105 | |
81 | |
30 | |
23 | |
58 | |
91 | |
56 | |
121 | |
21 | |
31 | |
70 | |
18 | |
13 | |
13 | |
1 | |
19 | |
90 | |
102 | |
124 | |
93 | |
49 | |
32 | |
44 | |
121 | |
194 | |
30 | |
33 | |
47 | |
101 | |
65 | |
18 | |
24 | |
127 | |
76 | |
114 | |
89 | |
100 | |
93 | |
18 |
