| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20040104021336.A32017@stackheap.org> From: attica at stackheap.org (S . f . Stover) Subject: TiVo Network Security On 04 Jan 04 12:25:48AM Randal L. Schwartz[merlyn@...nehenge.com] wrote: : Well, if you're running WEP for the sole purpose of hiding TiVo data, : and then you run strong crypto over that for your normal data traffic, : and the only result of breaking wep is that someone can connect to : 204.176.49/24, I really don't see the point of worrying too hard about : rotating the WEP key. : : Let'em crack it! True. I was thinking more along the lines where you wouldn't be able to run a VPN because TiVo can't understand it. In "production" wireless environments, I prefer to tunnel all traffic over ssh via squid proxy, but it doesn't sound like TiVo would integrate into that environment. However, if you keep moving through WEP keys, you could drop the ssh-tunnelling, integrate TiVo, and still remain reasonably secure... : Plus, the user interface for changing the WEP key on the TiVo requires : far too many up-down-left-right pushes for me. ;-) -- aka Dolph Longhorn GPG Key ID: 0xF8F859D0 http://pgp.mit.edu:11371/pks/lookup?search=0xF8F859D0&op=index "There is no such thing as right and wrong, there's just popular opinion." -Jeffrey Goines -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040104/fbee9414/attachment.bin
Powered by blists - more mailing lists