Got myself a shiny new Nokia 6820 from AT&T Wireless. One of the attractions was the possibility of Internet access using Bluetooth from my PowerBook to the phone and GPRS/EDGE from the phone to the big I. It took some poking around but it works and seems fairly speedy. This page has a set of instructions for a different phone that apply pretty well. I'm using the same "Nokia GPRS CID1" script that he's using. In the PPP setup I left Account Name and Password blank and put "proxy" into the Telephone Number field. "proxy" is the default APN for AT&T Wireless.
Saturday, November 06, 2004
Wednesday, July 21, 2004
Notes to myself about how to use GPG:
Export my own key for sending to others:
gpg --armor --export [my name]
Import another person's key:
gpg --import [key file]
or
gpg --keyserver [server] --search [their name]
Then sign their key and indicate that I trust it (GPG will prompt for degrees of trust):
gpg --edit-key [their name]
sign
trust
save
Export my own key for sending to others:
gpg --armor --export [my name]
Import another person's key:
gpg --import [key file]
or
gpg --keyserver [server] --search [their name]
Then sign their key and indicate that I trust it (GPG will prompt for degrees of trust):
gpg --edit-key [their name]
sign
trust
save
Wednesday, October 01, 2003
Have you upgraded OpenSSH to 3.7.1p2 because of the security problems, do you have sshd configured to use PAM, and now your Windows clients can't connect? Hey, what a coincidence, me too.
If you look a little closer at the dialog box that the Windows client pops up when you do a Quick Connect, you'll notice that there is a pull down menu at the bottom labeled Authentication Method. It defaults to Password. Try switching it to Keyboard Interactive and you should be able to log in.
It seems that the best fix for this is to edit the Quick Connect profile and add Keyboard Interactive to the acceptable authentication methods. Then in the Quick Connect dialog box choose <Profile Settings> for the Authentication Method. Connect and then choose Save Settings.
If you look a little closer at the dialog box that the Windows client pops up when you do a Quick Connect, you'll notice that there is a pull down menu at the bottom labeled Authentication Method. It defaults to Password. Try switching it to Keyboard Interactive and you should be able to log in.
It seems that the best fix for this is to edit the Quick Connect profile and add Keyboard Interactive to the acceptable authentication methods. Then in the Quick Connect dialog box choose <Profile Settings> for the Authentication Method. Connect and then choose Save Settings.
Monday, August 25, 2003
Want to make sendmail's -bP flag work? What's -bP do, you ask? It prints the size of your mail queue (rather like the last line of mailq (aka sendmail -bp)) without printing all of the entries in the mail queue.
First make sure your sendmail was compiled with shared memory support. Run 'sendmail -bv -d0.12 root' and look for SM_CONF_SHM. (Documented here)
Then add the following to your sendmail.m4:
define(`confSHARED_MEMORY_KEY', `42')
The value is arbitrary, it just can't be 0 (zero). If you happen to be running more than one copy of sendmail on your box with different queues, each sendmail config file should use a different value. (Documented (vaguely) here) Rebuild your sendmail.cf, restart sendmail, and -bP should work.
First make sure your sendmail was compiled with shared memory support. Run 'sendmail -bv -d0.12 root' and look for SM_CONF_SHM. (Documented here)
Then add the following to your sendmail.m4:
define(`confSHARED_MEMORY_KEY', `42')
The value is arbitrary, it just can't be 0 (zero). If you happen to be running more than one copy of sendmail on your box with different queues, each sendmail config file should use a different value. (Documented (vaguely) here) Rebuild your sendmail.cf, restart sendmail, and -bP should work.
Subscribe to:
Posts (Atom)