🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #619973

Re: Making Computers Secure

#619973
From: Quadibloc
Date: Thu, 01 Feb 2018 17:44
24 lines
2541 bytes
On Wednesday, January 31, 2018 at 8:14:09 AM UTC-7, Lynn Wheeler wrote:

> late 90s, EU had FINREAD standard which assumed insecure, compromised
> and/or "public" PCs that couldn't be trusted and provided for end-to-end
> trust.

This sounds like what it would have to be built around is:

- a secret key in the card plugged into your computer, so that "man-in-the-
middle" attacks couldn't be performed; and

- a keypad on that card, so you enter your PIN there, not on your computer that 
could be keylogged.

For the first point: instead of using the secret key in the card routinely, a 
second-level key that you go to the bank, stick your card in a terminal there, 
and refresh on the card might be what is directly used to get around man-in-the-
middle.

It certainly is possible to design a system of this general nature that is 
secure. This, however, concerns a different issue entirely than the one I was 
talking about.

John Savard
Technical Details
Message-ID: <cf0a6440-bfc0-4a55-81c1-b56f08570568@googlegroups.com>
Path: mbox-mo1.pugleaf.net!g8ni1487qtk.0!nntp.google.com!i22no5441541qta.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
References: <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <slrnp7145r.eu5.grahn+nntp@frailea.sa.invalid> <029e0b21-d4b4-4fda-b06d-4841f45f814d@googlegroups.com> <hkc27dp8vgo6kgui055d256j53lnh0baqa@4ax.com> <87abb16b-6d9f-48aa-8578-487835169555@googlegroups.com> <87lgget60y.fsf@garlic.com>

Show Full Headers
Complete Article Headers
X-Received: by 10.200.49.149 with SMTP id h21mr24808346qte.60.1517507096427;        Thu, 01 Feb 2018 09:44:56 -0800 (PST)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.55.129.198 with SMTP id c189ls908016qkd.8.gmail; Thu, 01 Feb 2018 09:44:54 -0800 (PST)
X-Received: by 10.200.53.213 with SMTP id l21mr26449562qtb.47.1517507094971;        Thu, 01 Feb 2018 09:44:54 -0800 (PST)
X-Received: by 10.31.136.139 with SMTP id k133mr2951737vkd.8.1517507094418; Thu, 01 Feb 2018 09:44:54 -0800 (PST)
Path: mbox-mo1.pugleaf.net!g8ni1487qtk.0!nntp.google.com!i22no5441541qta.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: alt.folklore.computers
Date: Thu, 1 Feb 2018 09:44:54 -0800 (PST)
In-Reply-To: <87lgget60y.fsf@garlic.com>
Complaints-To: groups...@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=72.143.233.47; posting-account=1nOeKQkAAABD2jxp4Pzmx9Hx5g9miO8y
NNTP-Posting-Host: 72.143.233.47
References: <3b1840a6-2ad7-4360-9c87-e3e8ad601ee2@googlegroups.com> <slrnp7145r.eu5.grahn+nntp@frailea.sa.invalid> <029e0b21-d4b4-4fda-b06d-4841f45f814d@googlegroups.com> <hkc27dp8vgo6kgui055d256j53lnh0baqa@4ax.com> <87abb16b-6d9f-48aa-8578-487835169555@googlegroups.com> <87lgget60y.fsf@garlic.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <cf0a6440-bfc0-4a55-81c1-b56f08570568@googlegroups.com>
Subject: Re: Making Computers Secure
From: Quadibloc <jsa...@ecn.ab.ca>
Injection-Date: Thu, 01 Feb 2018 17:44:54 +0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit