Messages

I've tried Debian before.  I didn't work as smoothly as Ubuntu right away, and since I didn't have any reason to try it other than curiosity, I gave up on it rather quickly.  I'm sure it's just as nice in most ways, though. :)

If that's an issue, he can safely take Slackware off of his list.

If you are torn between Slackware and Ubuntu, my recommendation is Debian. In fact, if you want to run Linux at all, my recommendation is Debian.

Is this idea dead?

[svn]

I always used to install svn. I'd host one server on my LAN, and then install the client on all other machines I frequented. I used to have 4 or 5 machines that I'd switch between, so it eliminated redundancies. I would log in to desktop A as tmp, hack around for an hour or two on a variety of different things. Then I'd commit to the server repository and log out. svn would automatically tabulate all of the files modified during the session and store them for me. I could leave for lunch, log in via laptop from the restaurant, check a copy of my home directory out, and be exactly where I left off; down to the wall paper and xmms volume. Rinse, repeat. I was always surprised how few people it seemed exploited this functionality.

Another is vtund, but depending on which version of the kernel you selected you may not have the necessary module.

http://www.nufw.org/

andrew@roflbirds:~$ perl -pi -e 'tr/a-mn-zA-MN-Z/n-za-mN-ZA-M/;'
newbys mom
arjolf zbz
has got it goin on
unf tbg vg tbva ba

hm, quote > code ^^

You can drop the -i flag because you're not editing a file in place.

[perl]

perl can be a powerful stream editor. Most of you are probably familiar with perl command line execution a la the  -e flag.  Combine it with -p and -i and you get a worthy sed alternative! The -p flag tells perl to iterate the command given by -e over every command line arg (in this case, a filename, hopefully). If there are no command line args, it'll read from STDIN. The -i flag writes the output of the -p iteration back to the argument (writing the file).

Examples:

tmp@tmp:~$ perl -e 'print "test"x10;'

-Print 'test' to STDOUT 10 times. For those of you who are behind on the times ;P

tmp@tmp:~$ perl -pe 's/^(\s+)?(telnet|shell|login|exec)/# $2/' /etc/inetd.conf

-Comment out any uncommented (running) instances of telnet, shell, login, exec in inetd.conf. Note: this will only print to STDOUT, it will not edit the file.

tmp@tmp:~$ perl -pi -e 's/bgcolor=#ffffff/bgcolor=#000000/i' *.html

-Change the background colour on any html page in the directory from black to white. The i after the substitution regex is needed to negate case sensitivity. WARNING: The previous command does WRITE to all of the files specified as command line args.

Most of you can probably infer the empowering implications of this little morsel of scripting prestidigitation.

[EDIT]

x86/64] link=topic=9405.msg119622#msg119622 date=1179721691]
The doctor's fax number, you mean?

EDIT -
Actually, you're right. If he said it out loud over the phone, anyone in the room (with a good ear, he may have said it quietly) could have penned it down and used it later I guess. But I think caller ID and voice are pretty strong credentials.

What really worries me is how easy it would be to "wiretap" a cell phone. That'd make an interesting blog, iago. How is the data transmitted, and it's it cyphered or not?

Caller ID is not something you want to rely on for authentication.  Easily spoofable, to say the least.  We do some VoIP stuff here at work, and you can pretty much pick the number that shows up for caller ID for a particular call, to give you an idea.

See orange boxing. Years ago orange boxes were hardware devices that had to be constructed, but soon after software was written to emulate the devices. Many common users don't realize that your CID is determined by an analog signal the routing unit propagates (similar to the sounds the buttons make), so essentially all an orange box does is translate input into necessary tones. One popular method for 'social engineering' with said devices was to call store departments with the CID of another intercom line and request information. Usually if you can access the phone, the local # is located on the receiver. If you take the branches' (or stores') external number and sub the desired local you'll get the direct line if it's available.

http://www.artofhacking.com/orange.htm

This was a post tmp made, (tmp: come back and give me new challenges), which I plan to retry and finish within the week. Don't give me hints or tell me how.  :P

Challenge:

Using bash, make it so that when you boot into X Windows with your default user (krazed or whichever login you use) it always starts up a terminal (of your choice) that is running with UID 0 (root). This is assuming that your default user is not UID 0.

I used to have it so that whenever I booted X, xfterm4 popped up already tailing my logfiles (which required privs), so I've had to do this before. Let's see how similar our methodology is.

Let me know if you need any clarification/hints.

I'm curious to see what you come up with here. Nice work thus far. I'll spend some time this weekend trying to recall some cool tricks for you =)

  Additionally, it does not use a viral license like that of the GPL (our license is not an open source license for obvious reasons). 

What're the obvious reasons that it is not an open source license?

http://www.javaop.com/~tmp/index.htm

I haven't been terribly active as of late... is the updated battle.net logon closed information?

If you want to learn to reverse engineer/hack, then all you really need to do is learn how to read assembly, not write it. If you're interested in learning how to read assembly a bit, touch base with me on the weekend and I can show you some simple functions that I generally save for teaching people.

Could you make a thread out of it? It'd save you several reiterations, and I'm sure there're a few of us interested. I think you'd draw more interest (and save some time and redundant, derivative subject matter) if you assumed an amateur audience, as opposed to novice. I may have some information to include that would be considered useful.

Haha, good read. Anything I ever wrote was always horrible. Try looking at the ncurses code for slackchat (if i recall correctly, the pscr() function to be specific) ;P

Evening, gents. I'm installing Slackware 10.2 on a PC and I've run into a strange network problem. I'm wondering if anyone has any ideas.

Some background: It's an ethernet network. When I plug the exact same cable into my Windows computer, it works fine. It's a standard DHCP network with a Linksys router. It's a fresh install of Linux. When I lspci, I can see my ethernet card. The loopback device is setup and I can ping localhost. I have run netconfig, setting the interface as DHCP. I can use ifconfig to bring the interface up.

The problem: I can't seem to get dhcpcd to grab a network address. I cannot ping any other nodes on the network (including the gateway). I have setup dhcpcd to dump output to syslog, and when I inspect my dhcpcd.log there is one message along the lines of: "dhcpcd timed out awaiting response".

Ideas?

Thanks in advance
tmp