On Tue, Mar 26, 2013 at 04:09:08PM +0100, Martin Bähr wrote: > well, i was thinking exactly that. packaging keys even if i have to. > or a script to download keys. or the script could generate keys and then > email me the public one. > > > If it's not really general, you could put it in your own repository. > > That's not really that hard to host. > > well, i was thinking of using my repo on foresight for now.
My question was aimed at whether you were trying to keep access private. Personal conary repositories hosted by foresight should be used only for publicly-accessible content, not for private, restricted content, and the intent was that all repositories hosted by foresight would have full read-only access for anonymous users. If you want a repository with restricted access, you should host it yourself. As long as it's OK to have anonymous access to it and it's generally legal to post then it makes sense to put into your own repository. Does that make sense? _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
