Looks like someone in charge noticed and had it pulled. Their attention was probably drawn by the horrendus slashdotting it received. Well, maybe it'll be back later. Either way, the source is out and it's sure to follow the path of Gnutella. And, as someone mentioned previously, they were acquired back in May of 1999, so it's almost certain that this (along with the source), is just a shot back at AOL.
Um, yes it does. It encrypts IM traffic with other Trillian users through both the AIM and ICQ protocols. They call it SecureIM. Next time, check your facts before you just dismiss someone like that.
Doesn't hotwiring just refer to crossing the ignition wires, thereby bypassing the whole key system?
What you've just described is more akin to having to cut a new key to steal a car.
That said, you certainly may be right in saying that you can't bypass the authentication system. Perhaps with a Segway there are no wires available to cross.
It just seems wrong to refer to it as hotwiring. Hotwiring should be quick, crude, and easy.
they didn't fall into the drm/encrypted crap... You can save a page as html, print it up, do what you want to without having to go through draconian security measures. Yes, but have you noticed the unique ID and javascript that's embedded in there? Try downloading a few pages and sharing it with your friends. Or, downloading it and trying to view it when you are offline. Each time, it contacts the safari server and logs your id. That said, it's nothing like DRM. Simple to view with a non-js browser, or edit out the unique id, but it's a basic measure to inhibit people from downloading and sharing - or at least let them know how often casual sharing happens.
Most nerds I know are into science as well as computers. If you don't want science stories, turn them off, or find a computers only news site. Personally, I enjoy the science stories.
So you really want to enter your name, address, date of birth, social security number, and income information into a piece of software you got from who knows where? And who did you say cracked it, again? Someone you can trust with that information, I assume?
They ran ExtractStream. Video extraction is expressly prohibited by the TiVo terms of service. In order to run this app, they had to crack open the TiVo and install custom software. With the series2 TiVo's, this is definitely a hack, breaking the encryption and hash verification they have on the kernel and binaries (well, not breaking, really just avoiding - aka "circumventing" - this protection by inserting shell code into the boot parameters as a BASH_ENV variable). With the series1, you have to modify the prom to do this, unless you have a very old TiVo that you have prevented TiVo from updating the boot code for, again "circumventing" the code TiVo has in place to prevent this sort of activity.
I would consider heavy reverse engineering of an unpublished disk format, installing custom software by circumventing the measures they have in place to prevent that, and violating the Terms of Service to extract video equivalent to "cracking" or "hacking" - no matter how you define those terms.
And they say they didn't have to crack anything...
Simple. Free testing of their ix86 based code. Rumor has it that they are keeping that option open should PPC architecture fall far behind that of ix86. Making this release just allows them to have it publicly tested and improved.
It's a back burner project anyway, but having to make these releases makes it a bit more formal and forces them to achive certain usability goals. Plus, it helps ix86 development keep up with their main Darwin core.
Re:Could someone post the link from New Scientist
on
Ready, Steady, Evolve
·
· Score: 1
There *is* a link, it's the one right on the homepage with a photo of the latest issue.
What? It leads to the subscribe page?
Yup. Like most magazines, they have back issues and other articles online, but for the latest issue, you have to subscribe. It's worth it, really. I've read issues borrowed from a friend for the last few months, and finally signed up for a subscription myself.
If you want the article for a class, visit a newsstand.
Great. Their "Macintosh Updater" link on that page links to one of those stupid "Under Construction" images. Those should be banned. If it's not up there yet, don't link to it. So, download the.exe updater and try to figure out how to boot it on an iMac. Put it in the floppy drive? Uh, no floppy. Run an.exe? Wrong arch. Doesn't really matter. I can't afford the standard DVD media, nevermind the 2x and 4x versions.
I hate replying to my own comments, but I missed the obvious.
This means these tools are available to users of distributions other than RedHat.
Perhaps they've made some enhancements specific to RedHat - better integration with other toolsets perhaps, but there's no reason you couldn't use it on Debian, Gentoo, etc...
I know you're all too lazy to read the entire release notes, so jump directly to the source of these tools. RedHat's release notes say:
This beta contains a kernel providing EA and ACL support for the ext3 filesystem based on the patches and user-level tools from http://acl.bestbits.at/
So, check them out directly. They have more information than the RELEASE-NOTES, and some useful examples.
I agree with you. Your question though, was overly general. There's really three (or more) different separate data issues that you have to deal with.
Like most, I have many accounts, and just manage them on the fly. My data is retrieved manually when I need it. SSH (and scp), VNC, etc. This usually does the job.
Not the easiest way to do it. Especially when I recently changed jobs and had to setup new data and profiles - I thought, there must be a better way to do it.
So, here's a breakdown of the problems, and suggested fixes.
Break it down into 3 separate sets of data: 1. Profile data - Your shell scripts,.bashrc, environment, ssh directory, pgp keys, etc. 2. Daily Documents - My Documents folder, data directory. Limit this to stuff you need in ALL locations (though you could have a personal and a work version...) and on a regular basis. 3. Archived files - Infrequently used, but you occasionally need to access them from various places.
Then, the problem becomes much simpler. Instead of a grand scheme to manage all three of these at once, you have three smaller, simpler problems.
Here's my suggestions: 1. Profile info - Wasn't originally my idea, but the best thing I've found is to use CVS to manage the files. You'll also have to setup your shell scripts to detect the OS / machine you are on and run OS / machine specific versions. For example:.bashrc Detects OS, runs ~/.profile.d/linux, ~/.profile.d/win32, ~/.profile.d/macosx, etc. Detects hostname, runs ~/.profile.d/hostname. Put core stuff in the.bashrc, put specific things in the separate files.
The rest, usually doesn't change.
Add it all to CVS on a personal server. Then just checkout to each account you have. cvs update will keep it up to date if you change the master copy. You might need a special.cvsignore to make sure it only manages the files you want it to. Then, you have the same profile files on all of your machines. Got a new.emacs macro, or shell prompt tweak? Edit one account, cvs commit, cvs update the rest.
2. Daily use Documents. This is a mix. Perhaps you could use a separate CVS repository. Or, use rsync and rdiff type backup sync programs. The key here is to keep this to a minimum. How much to you really need, and how much *must* be in sync between all your machines at all times. Again, this is fairly easy for a small number of documents, so don't let it get out of hand. If you don't use the file all the time, and don't need to maintain changes, then push it to archives. This is the issue that most other posts address, so I won't get into too much detail. All those solutions are much easier with a small number of documents.
3. Archived files. This is probably what you were really asking about with regards to NFS and sharing files. These are the files you need every so often, stuff like your mp3 collection, downloaded software, extended (non category 2) documents, and the like. For these, it depends on your setup and level of network access (the speed is important too). rsync might work if you need a locally cached copy, but this is much easier if you leave it in one place. Setup a gateway on your home network with IPSec or PPTP. Or, find WebDAV or some internet accessible filesystem you can use (NFS or SMB even, depends on your security needs). Then, connect to the central repository when you need these files. This can be large, but keep it so that you don't need to synchronize frequently, and preferably only in one direction. You listen to your mp3's, but you don't change them frequently. Same with your downloaded tar/zip files of software you've collected. (Face it, having a single directory with cygwin, mozilla, etc - all the software you have installed at each location - is much easier than finding and downloading them all from their various sites each time.) Or, for these files, if you really don't need them all the time, leave them on the central server, and scp them when you need them.
--
So, that pretty much covers it. I hope these suggestions are useful. There comes a time where managing it on the fly just gets too cumbersome. (You'll know that time - it usually happens right after you wipe out some vitally important data because you didn't synchronize the files.)
Beyond this, you can always add all kinds of stuff. Some examples: ACAP (a configuration file server, I use it with mulberry, my IMAP client. It lets me set preferences), Kerberos for common authentication, LDAP for an address book or netscape roaming profiles, the list goes on and on.
What would be nice is a set of scripts to help manage this. Imagine, getting a new account and typing "pullprofile", and having your environment and data all retrieved, pulled from your central server. Then you could have login and logout scripts to synchronize the data, or just manually (possibly remotely if you forgot to sync before you left work) run them. A cron job to synchronize the big data store overnight.
I'll keep dreaming, and keep looking on freshmeat and sourceforge for a project like this. Maybe one day I'll get up the energy to start it myself, but don't count on it.
Slashdot Mirror
In the borderline stupid category, but I find this quite useful.
When grepping the output from ps, bracket the first character.
ps ax | grep [s]sh
If you don't, the grep command may show up in the results.
If you want to actually use the phone to talk to someone, then go somewhere with a lot of bugs, and wait for them to all run away.
Oooh... bugs are gone. I must be getting a call...
Simple. The Explorer has the most room for improvement, and therefore can show more significant advances.
.05% efficiency out of an already efficient vehicle.
It's not very impressive squeaking an extra 2 mpg or
This project shows that an Explorer doesn't have to be quite so... excessive.
Looks like someone in charge noticed and had it pulled. Their attention was probably drawn by the horrendus slashdotting it received.
Well, maybe it'll be back later. Either way, the source is out and it's sure to follow the path of Gnutella.
And, as someone mentioned previously, they were acquired back in May of 1999, so it's almost certain that this (along with the source), is just a shot back at AOL.
Um, yes it does. It encrypts IM traffic with other Trillian users through both the AIM and ICQ protocols. They call it SecureIM.
Next time, check your facts before you just dismiss someone like that.
Doesn't hotwiring just refer to crossing the ignition wires, thereby bypassing the whole key system?
What you've just described is more akin to having to cut a new key to steal a car.
That said, you certainly may be right in saying that you can't bypass the authentication system. Perhaps with a Segway there are no wires available to cross.
It just seems wrong to refer to it as hotwiring. Hotwiring should be quick, crude, and easy.
Hmmm. Someone has never seen http://apple.slashdot.org/ before.
Don't worry. It's just you.
(It's just apple stories, nothing has changed)
they didn't fall into the drm/encrypted crap ... You can save a page as html, print it up, do what you want to without having to go through draconian security measures.
Yes, but have you noticed the unique ID and javascript that's embedded in there? Try downloading a few pages and sharing it with your friends. Or, downloading it and trying to view it when you are offline. Each time, it contacts the safari server and logs your id.
That said, it's nothing like DRM. Simple to view with a non-js browser, or edit out the unique id, but it's a basic measure to inhibit people from downloading and sharing - or at least let them know how often casual sharing happens.
Most nerds I know are into science as well as computers. If you don't want science stories, turn them off, or find a computers only news site. Personally, I enjoy the science stories.
So you really want to enter your name, address, date of birth, social security number, and income information into a piece of software you got from who knows where?
And who did you say cracked it, again? Someone you can trust with that information, I assume?
They ran ExtractStream. Video extraction is expressly prohibited by the TiVo terms of service. In order to run this app, they had to crack open the TiVo and install custom software. With the series2 TiVo's, this is definitely a hack, breaking the encryption and hash verification they have on the kernel and binaries (well, not breaking, really just avoiding - aka "circumventing" - this protection by inserting shell code into the boot parameters as a BASH_ENV variable). With the series1, you have to modify the prom to do this, unless you have a very old TiVo that you have prevented TiVo from updating the boot code for, again "circumventing" the code TiVo has in place to prevent this sort of activity.
I would consider heavy reverse engineering of an unpublished disk format, installing custom software by circumventing the measures they have in place to prevent that, and violating the Terms of Service to extract video equivalent to "cracking" or "hacking" - no matter how you define those terms.
And they say they didn't have to crack anything...
Now you'll be charged with violating the DMCA for releasing the details of their super-secret pricing code.
He's sold off an additional 6 million over the last week too. Think he knew bad things were coming?
http://biz.yahoo.com/t/m/msft.html
Simple. Free testing of their ix86 based code. Rumor has it that they are keeping that option open should PPC architecture fall far behind that of ix86. Making this release just allows them to have it publicly tested and improved.
It's a back burner project anyway, but having to make these releases makes it a bit more formal and forces them to achive certain usability goals. Plus, it helps ix86 development keep up with their main Darwin core.
Slashdot it into oblivion.
There *is* a link, it's the one right on the homepage with a photo of the latest issue.
What? It leads to the subscribe page?
Yup. Like most magazines, they have back issues and other articles online, but for the latest issue, you have to subscribe. It's worth it, really. I've read issues borrowed from a friend for the last few months, and finally signed up for a subscription myself.
If you want the article for a class, visit a newsstand.
Great. Their "Macintosh Updater" link on that page links to one of those stupid "Under Construction" images. .exe updater and try to figure out how to boot it on an iMac. Put it in the floppy drive? Uh, no floppy. Run an .exe? Wrong arch.
Those should be banned. If it's not up there yet, don't link to it.
So, download the
Doesn't really matter. I can't afford the standard DVD media, nevermind the 2x and 4x versions.
I hate replying to my own comments, but I missed the obvious.
This means these tools are available to users of distributions other than RedHat.
Perhaps they've made some enhancements specific to RedHat - better integration with other toolsets perhaps, but there's no reason you couldn't use it on Debian, Gentoo, etc...
I know you're all too lazy to read the entire release notes, so jump directly to the source of these tools. RedHat's release notes say:
This beta contains a kernel providing EA and ACL support for the ext3 filesystem based on the patches and user-level tools from http://acl.bestbits.at/
So, check them out directly. They have more information than the RELEASE-NOTES, and some useful examples.
I agree with you. Your question though, was overly general.
.bashrc, environment, ssh directory, pgp keys, etc.
.bashrc .bashrc, put specific things in the separate files.
.cvsignore to make sure it only manages the files you want it to. .emacs macro, or shell prompt tweak? Edit one account, cvs commit, cvs update the rest.
There's really three (or more) different separate data issues that you have to deal with.
Like most, I have many accounts, and just manage them on the fly. My data is retrieved manually when I need it. SSH (and scp), VNC, etc. This usually does the job.
Not the easiest way to do it. Especially when I recently changed jobs and had to setup new data and profiles - I thought, there must be a better way to do it.
So, here's a breakdown of the problems, and suggested fixes.
Break it down into 3 separate sets of data:
1. Profile data - Your shell scripts,
2. Daily Documents - My Documents folder, data directory. Limit this to stuff you need in ALL locations (though you could have a personal and a work version...) and on a regular basis.
3. Archived files - Infrequently used, but you occasionally need to access them from various places.
Then, the problem becomes much simpler. Instead of a grand scheme to manage all three of these at once, you have three smaller, simpler problems.
Here's my suggestions:
1. Profile info - Wasn't originally my idea, but the best thing I've found is to use CVS to manage the files. You'll also have to setup your shell scripts to detect the OS / machine you are on and run OS / machine specific versions.
For example:
Detects OS, runs ~/.profile.d/linux, ~/.profile.d/win32, ~/.profile.d/macosx, etc.
Detects hostname, runs ~/.profile.d/hostname.
Put core stuff in the
The rest, usually doesn't change.
Add it all to CVS on a personal server. Then just checkout to each account you have. cvs update will keep it up to date if you change the master copy. You might need a special
Then, you have the same profile files on all of your machines. Got a new
2. Daily use Documents. This is a mix. Perhaps you could use a separate CVS repository. Or, use rsync and rdiff type backup sync programs. The key here is to keep this to a minimum. How much to you really need, and how much *must* be in sync between all your machines at all times. Again, this is fairly easy for a small number of documents, so don't let it get out of hand. If you don't use the file all the time, and don't need to maintain changes, then push it to archives.
This is the issue that most other posts address, so I won't get into too much detail. All those solutions are much easier with a small number of documents.
3. Archived files. This is probably what you were really asking about with regards to NFS and sharing files. These are the files you need every so often, stuff like your mp3 collection, downloaded software, extended (non category 2) documents, and the like.
For these, it depends on your setup and level of network access (the speed is important too). rsync might work if you need a locally cached copy, but this is much easier if you leave it in one place. Setup a gateway on your home network with IPSec or PPTP. Or, find WebDAV or some internet accessible filesystem you can use (NFS or SMB even, depends on your security needs). Then, connect to the central repository when you need these files.
This can be large, but keep it so that you don't need to synchronize frequently, and preferably only in one direction. You listen to your mp3's, but you don't change them frequently. Same with your downloaded tar/zip files of software you've collected. (Face it, having a single directory with cygwin, mozilla, etc - all the software you have installed at each location - is much easier than finding and downloading them all from their various sites each time.)
Or, for these files, if you really don't need them all the time, leave them on the central server, and scp them when you need them.
--
So, that pretty much covers it. I hope these suggestions are useful. There comes a time where managing it on the fly just gets too cumbersome. (You'll know that time - it usually happens right after you wipe out some vitally important data because you didn't synchronize the files.)
Beyond this, you can always add all kinds of stuff. Some examples: ACAP (a configuration file server, I use it with mulberry, my IMAP client. It lets me set preferences), Kerberos for common authentication, LDAP for an address book or netscape roaming profiles, the list goes on and on.
What would be nice is a set of scripts to help manage this.
Imagine, getting a new account and typing "pullprofile", and having your environment and data all retrieved, pulled from your central server. Then you could have login and logout scripts to synchronize the data, or just manually (possibly remotely if you forgot to sync before you left work) run them. A cron job to synchronize the big data store overnight.
I'll keep dreaming, and keep looking on freshmeat and sourceforge for a project like this. Maybe one day I'll get up the energy to start it myself, but don't count on it.
;-)
~Jonathan