Maybe you're thinking of this? It's not hosted at UC Berkeley, but it does sound like what you're talking about. I found a reference to it at Wikipedia.
Thanks for the interesting reply, but scan down on the page you ref'ed to the question "Q: Does the rule apply to residents of rental property?" It answers: "A: Yes. Effective January 22, 1999, renters may install antennas within their leasehold, which means inside the dwelling or on outdoor areas that are part of the tenant's leased space and which are under the exclusive use or control of the tenant...." So, renters are covered as well as they may 'control' their balconies, patios, etc.
Was wondering if you spoke with your the Paypal tech about how login information can be extracted from browser cookies. I thought these are just randomly generated strings used to identify the browser instance to the server, where the personal information is kept. I suppose it's possible for a perpetrator to hijack a browser session, through sniffing packets, or physical access to the user's computer, but that doesn't sound like cookie information extraction.
here. It's built for security, but I think it serves up only straight HTML, no CGI or SSL. I haven't personally used it, but I thought it'd be a useful link to pass along.
Slashdot Mirror
Maybe you're thinking of this? It's not hosted at UC Berkeley, but it does sound like what you're talking about. I found a reference to it at Wikipedia.
Thanks for the interesting reply, but scan down on the page you ref'ed to the question "Q: Does the rule apply to residents of rental property?" It answers: "A: Yes. Effective January 22, 1999, renters may install antennas within their leasehold, which means inside the dwelling or on outdoor areas that are part of the tenant's leased space and which are under the exclusive use or control of the tenant. ..." So, renters are covered as well as they may 'control' their balconies, patios, etc.
Was wondering if you spoke with your the Paypal tech about how login information can be extracted from browser cookies. I thought these are just randomly generated strings used to identify the browser instance to the server, where the personal information is kept. I suppose it's possible for a perpetrator to hijack a browser session, through sniffing packets, or physical access to the user's computer, but that doesn't sound like cookie information extraction.
here. It's built for security, but I think it serves up only straight HTML, no CGI or SSL. I haven't personally used it, but I thought it'd be a useful link to pass along.