Domain: drijf.net
Stories and comments across the archive that link to drijf.net.
Comments · 7
-
Re:Umm.. No?
I was actually hoping that Apple would release the server side items necessary to allow independent hosting companies to host
.mac-like services. Apple would still be able to sell iWeb as the means for easy desktop publishing and still have it's own .mac accounts.
As far as I know, much of .Mac is just a WebDAV server with Apple's own additional authentication added onto it. These instructions tell how you can spoof your Mac (with your own IP for mac.com) into thinking that your own webdav server is .Mac.
I ended up setting up an 'rdiff-backup'-based backup system instead, so I never bothered to do the .Mac thing, but it looks pretty do-able. I just wish that Apple would make the setting of your own WebDav/.Mac server an easy configuration. Those of us who already paying for our own hardware aren't going to fork over more $$ for .Mac, so just let us do our own thing without hassle.
- Adam -
Re:Erm...
/etc/hosts is only used very early in the boot process on Mac OS X. So you can't actually use it to block addresses. You have to use netinfo instead
Then how in the hell is this iDisk emulation hack working between my iBook and my Linux server?
http://www.drijf.net/dototto/wwwmac.html -
Re:The ol' Hardware MonopolyI don't have
.Mac, so I don't know what all it does. But I do know some of it is built on WebDAV, and people are trying to do .Mac stuff without .MacRunning Apple's Backup Without a
.Mac AccountiSync without
.Mac (incomplete) -
*ack!*Not good. Reading the drijf.net article reveals that iTools backs up in the clear across the 'net. Furthermore, authentication can be spoofed as backup doesn't check the authentication of the server cert. Scary
...Thanks for the links, BTW!
-
Re:Previous article
Yes, the previous article is (IMHO) much more informative, as it tells you how to set up a fake
.MAC server.
The current article tells you what you can do with it ... kinda. The language is rather obtuse in some sections, and all of those tips rely on the server being an OS X machine. What if I want my central server to run Linux? BSD?
The useful articles are this one which explains how to set up a fake .Mac server, and use Apple's Backup with it, and this one about making an iSync server.
-
We need more fake servers
I like this idea. So we can emulate
.Mac servers, BNETD servers, advertising servers, Cydoor servers, and even :CueCat servers. Setting up independent servers has the obvious advantage of being independent from an ultimate authority, decentralizing the service and making it more useful to the Internet community. So I ask Slashdot, what commericial or otherwise propertiary server will be reverse-engineered and cloned next? My vote is in for an Oscar/TOC server so one could use AOL-IM to communicate with one's LAN. -
iSync only wants to talk to Apple serverI found out that
- iSync does not use WebDAV, but a different protocol (at least for registering).
- iSync contacts the server using https. The server is authenticated properly. I tried to fool iSync like I did with Backup but that didn't work, because iSync does not accept the server certificate.