Re: Secure voice app: FEATURE REQUEST: RECORD IPs
>On Mon, Jan 27, 2003 at 08:23:15AM -0800, Major Variola (ret) wrote: >> The versions of all the secure phones I've evaluated needed this feature: >> a minimal answering machine. With just the ability to record IPs of While it's nice to have it built into the phone's user interface, you can always do the tool-based thing and use a separate sniffer program to watch who's calling you, and it's also helpful if somebody's trying to call you with a program your phone doesn't grok. If you're on a Unix system, tcpdump is ok, or you can use newer solutions like snort, or pick your favorite Windows equivalent. Either way, if you know the range of ports on your system they're calling, set up the sniffer to record those and output them in some friendly manner; otherwise sniff everything and grep out the familiar ones that you know aren't phone calls.
Re: Re: Secure voice app: FEATURE REQUEST: RECORD IPs
- Original Message - From: "Harmon Seaver" <[EMAIL PROTECTED]> > On Mon, Jan 27, 2003 at 08:23:15AM -0800, Major Variola (ret) wrote: > > The versions of all the secure phones I've evaluated needed this > > feature: > > a minimal answering machine. With just the ability to record IPs of > > hosts that > > tried to call. > > > > (A local table can map these to your friends or their faces. > > Of course, this table should be encrypted when not in use.) > >Pretty hard to do if people are using dialup. Or even dsl, unless they run a > linux box they don't ever reboot -- although I've found my dsl ip changing > sometimes on it's own, and with no rhyme or reason. Cable is a little more > stable, when I had a cable modem it didn't change ip unless I shut off the modem > for awhile, and not even always then. The obvious solution is then to take it one step further, rebuild the protocol so that there is a cryptographic identifier (probably a public key, hopefully for ECC to save space). In a fully developed system that identifier could also be used to make the call in the first place. Admittedly this is unlikely to happen for quite some time, but if people start asking for it, they'll start considering it. Joe Trust Laboratories http://www.trustlaboratories.com
Re: Secure voice app: FEATURE REQUEST: RECORD IPs
Harmon Seaver <[EMAIL PROTECTED]> > On Mon, Jan 27, 2003 at 07:06:24PM +0100, Thomas Shaddack wrote: > > DSL lease timeout. A feature of DHCP-based dynamic IP addresses over > > permanent connections. Similar for cable, though the differences yo > > observed seem to be rather implementation-dependent than principial. > >No, not really. It's far too irregular for that, sometimes goes for over a > month, then sometimes 2-3 times in a week. More like them doing work on the > system. > That's about what I've seen. > Not really dhcp anyway, it's Eoppp. Cable is usally dhcp, and is better > because it authenticates on the mac address of the cable modem. And dhcp can be > set up to always give the same ip to a certain mac address, but I don't think > the eoppp can, or at least they don't -- it always has to negotiate a > challange/passwd response which can be quite problematic -- sometimes the only > way to get it to work again is to unplug the modem for 30 seconds or so, which, > of course, frustrates any script you have to automagically reset dns for your > domainname, or even just keep you online. > >Harmon Seaver > There's probably an X10 module that would let your Linux box cycle the power on your modem/router/switch. try $50 : http://www.x10.com/automation/x10_ck11a.htm If you're not using a domain name then your script could publish your IP address on your home page ( in the clear or not as you choose ). Mike
Re: Secure voice app: FEATURE REQUEST: RECORD IPs
On Mon, Jan 27, 2003 at 07:06:24PM +0100, Thomas Shaddack wrote: > > >Pretty hard to do if people are using dialup. Or even dsl, unless they run a > > linux box they don't ever reboot -- although I've found my dsl ip changing > > sometimes on it's own, and with no rhyme or reason. > > DSL lease timeout. A feature of DHCP-based dynamic IP addresses over > permanent connections. Similar for cable, though the differences yo > observed seem to be rather implementation-dependent than principial. No, not really. It's far too irregular for that, sometimes goes for over a month, then sometimes 2-3 times in a week. More like them doing work on the system. Not really dhcp anyway, it's Eoppp. Cable is usally dhcp, and is better because it authenticates on the mac address of the cable modem. And dhcp can be set up to always give the same ip to a certain mac address, but I don't think the eoppp can, or at least they don't -- it always has to negotiate a challange/passwd response which can be quite problematic -- sometimes the only way to get it to work again is to unplug the modem for 30 seconds or so, which, of course, frustrates any script you have to automagically reset dns for your domainname, or even just keep you online. > > > Cable is a little more stable, when I had a cable modem it didn't > > change ip unless I shut off the modem for awhile, and not even always > > then. > > Idea: What about a caller ID system, based on eg. SSL certificates or PGP > signed challenge-response? This would probably work okay, even ssh works despite ip changes, although it stops to ask. -- Harmon Seaver CyberShamanix http://www.cybershamanix.com
Re: Secure voice app: FEATURE REQUEST: RECORD IPs
>Pretty hard to do if people are using dialup. Or even dsl, unless they run a > linux box they don't ever reboot -- although I've found my dsl ip changing > sometimes on it's own, and with no rhyme or reason. DSL lease timeout. A feature of DHCP-based dynamic IP addresses over permanent connections. Similar for cable, though the differences yo observed seem to be rather implementation-dependent than principial. > Cable is a little more stable, when I had a cable modem it didn't > change ip unless I shut off the modem for awhile, and not even always > then. Idea: What about a caller ID system, based on eg. SSL certificates or PGP signed challenge-response?
Re: Secure voice app: FEATURE REQUEST: RECORD IPs
On Mon, Jan 27, 2003 at 08:23:15AM -0800, Major Variola (ret) wrote: > >I am elated that the development of Speak Freely is continuing. I think > it > > The versions of all the secure phones I've evaluated needed this > feature: > a minimal answering machine. With just the ability to record IPs of > hosts that > tried to call. > > (A local table can map these to your friends or their faces. > Of course, this table should be encrypted when not in use.) Pretty hard to do if people are using dialup. Or even dsl, unless they run a linux box they don't ever reboot -- although I've found my dsl ip changing sometimes on it's own, and with no rhyme or reason. Cable is a little more stable, when I had a cable modem it didn't change ip unless I shut off the modem for awhile, and not even always then. (snip) -- Harmon Seaver CyberShamanix http://www.cybershamanix.com
