On 04/08/2018 05:51 PM, Eli Schwartz via aur-general wrote:
> On 04/08/2018 07:49 AM, Florian Pritz via aur-general wrote:
>> On 08.04.2018 05:01, Eli Schwartz via aur-general wrote:
>>> If you're really afraid of someone running as either your user, or some
>>> user with the power to hijack your
On 04/08/2018 07:49 AM, Florian Pritz via aur-general wrote:
> On 08.04.2018 05:01, Eli Schwartz via aur-general wrote:
>> If you're really afraid of someone running as either your user, or some
>> user with the power to hijack your SSH session, while you're trying to
>> sign something, then they
Morten Linderud writes:
> What i have done now is to launch a second gpg-agent that only
> provides an -extra socket with no caching what so ever.
I thought of something along those lines. Can you detail the commands
so that we can put that on the wiki?
--
Pierre
On Sun, Apr 08, 2018 at 06:09:27PM +0530, Pierre Neidhardt wrote:
>
> > Use the `ignore-cache-for-signing` option in gpg-agent. Unsure if you can
> > enable
> > this only for connections to soyuz.
>
> But that's only for signing, so that won't do if I have subkeys used for
> other purposes
> Use the `ignore-cache-for-signing` option in gpg-agent. Unsure if you can
> enable
> this only for connections to soyuz.
But that's only for signing, so that won't do if I have subkeys used for
other purposes under the same master key, right?
--
Pierre Neidhardt
signature.asc
Description:
On Sun, Apr 08, 2018 at 05:58:11PM +0530, Pierre Neidhardt via aur-general
wrote:
>
> What's the best practice to disable password caching? Set the timeout
> to zero?
>
> Does anyone know if it's possible to have have a zero-timeout when on
> soyuz while having another timeout time locally?
What's the best practice to disable password caching? Set the timeout
to zero?
Does anyone know if it's possible to have have a zero-timeout when on
soyuz while having another timeout time locally?
--
Pierre Neidhardt
signature.asc
Description: PGP signature
On 08.04.2018 05:01, Eli Schwartz via aur-general wrote:
> If you're really afraid of someone running as either your user, or some
> user with the power to hijack your SSH session, while you're trying to
> sign something, then they could just switch out your built files anyway.
> There's literally
On Sun, Apr 8, 2018 at 9:51 AM, Albert Graef wrote:
> Thanks, Eli! I'll give it another go immediately.
Worked, thanks again!
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
WWW:https://plus.google.com/+AlbertGraef
On Sun, Apr 8, 2018 at 9:40 AM, Eli Schwartz via aur-general
wrote:
> I've removed it manually, we're looking at a more permanent solution.
Thanks, Eli! I'll give it another go immediately.
Albert
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
LoneVVolf wrote:
> AUR has llvm33 , llvm38, llvm39, llvm4 and llvm 5 . Maybe your packages
> can use one of those ?
LLVM 3.5 is the last version which still has the old JIT backend,
which is what Pure still needs right now. LLVM 3.4 would work just as
well, but that's not available in the AUR,
On 04/08/2018 03:29 AM, Albert Graef via aur-general wrote:
> On Sun, Apr 8, 2018 at 5:56 AM, Eli Schwartz via aur-general
> wrote:
>> Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg
>> sets it from the first element of pkgname, and this is why
On Sun, Apr 8, 2018 at 5:56 AM, Eli Schwartz via aur-general
wrote:
> Explicitly contrary to the PKGBUILD spec; if pkgbase is unset, makepkg
> sets it from the first element of pkgname, and this is why the .SRCINFO
> still shows it.
I can add an explicit pkgbase=llvm35
13 matches
Mail list logo