Am Donnerstag, 21. September 2017, 19:48:34 CEST schrieb Matthias Apitz:
> > Unfortunately their hardware dos not seem to support Ubuntu any more. I
> > found the "Ubuntu Edition" under "obsolete models", even a cyanogen
> > edition, but all their current models run on Android. The rest of their
Am Freitag, 22. September 2017, 10:36:45 CEST schrieb Franck Routier:
> Hi, Jolla did an official port of SailfishOS to Sony Xperia X hardware.
> The only point is the the image is not yet available for purchase,
> but it should be a matter of days...
>
> See https://blog.jolla.com/sailfishx/
On Tue, 26 Sep 2017 13:07, andr...@andrewg.com said:
> The gpg command itself should cryptographically verify signatures when
> performing --list-sigs, so that at least it can throw a warning when an
Actually --list-sigs is more of a debug command than a command users
should use to verify a key.
On Tue, 26 Sep 2017 15:14:38 +0200, Kristian Fiskerstrand wrote:
> On 09/26/2017 03:05 PM, Stefan Claas wrote:
> > I'm no expert like all you guys, but my dream would be if Werner
> > and his team could
> > work together with the keybase team, so that we could have WKD
> > support for keybase.
>
On 09/26/2017 03:51 PM, Andrew Gallagher wrote:
> Not getting into an OS flame war here, but not everyone uses Android.
That doesn't mean it doesn't exist, it just means different user
preferences as represented by the weigths in the decision matrix when
purchasing a new device.
--
Hello,
Does anyone has idea how to implement this.
As I have urgent business need to do it ASAP.
Thanks,
Sandhya
From: SHARMA Sandhya (MORPHO)
Sent: Friday, September 22, 2017 6:21 PM
To: 'gnupg-users@gnupg.org'
Subject: Use of Passphrase Callback
Hello,
I am Using
On 26/09/17 14:39, Kristian Fiskerstrand wrote:
> On 09/26/2017 03:38 PM, Andrew Gallagher wrote:
>> Yes. Unfortunately it's tricky to implement that on a smartphone. We
>> don't have card+phone working in gnupg yet either. We *barely* have
>> gnupg working on phones at all. But that's for another
On 09/26/2017 03:38 PM, Andrew Gallagher wrote:
> Yes. Unfortunately it's tricky to implement that on a smartphone. We
> don't have card+phone working in gnupg yet either. We *barely* have
> gnupg working on phones at all. But that's for another day.
Sure we do, youbikey 3 neo on NFC works quite
On 26/09/17 13:49, Kristian Fiskerstrand wrote:
>
> The users shoudn't browse keyservers at all, so it shouldn't really be
> an issue. Linking to get operation to get the public keyblock is just a
> convenience.
Users shouldn't do it. And yet they still do it, precisely because it is
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17-09-26 09:15 AM, Andrew Gallagher wrote:
> On 26/09/17 12:30, Kristian Fiskerstrand wrote:
>> On 09/26/2017 01:07 PM, Andrew Gallagher wrote:
>>> So SKS should just say "unverified signature from
>>> ". It should not repeat the purported
On 09/26/2017 02:15 PM, Andrew Gallagher wrote:
> Absolutely. None of this is an argument against users having to do
> things right. But the way to get users to do things right is to train
> them to do things right from the start - and you do that by railroading
> them down the straight and narrow
On 26/09/17 12:30, Kristian Fiskerstrand wrote:
> On 09/26/2017 01:07 PM, Andrew Gallagher wrote:
>> So SKS should just say "unverified signature from ". It
>> should not repeat the purported user ID, nor provide a search link that
>> returns completely unrelated keys that happen to have the same
On 09/26/2017 01:07 PM, Andrew Gallagher wrote:
> So SKS should just say "unverified signature from ". It
> should not repeat the purported user ID, nor provide a search link that
> returns completely unrelated keys that happen to have the same purported ID.
No, that is also wrong, as it implies
13 matches
Mail list logo