News for hackers. Stuff that matters.
Re:Cryptkeeper sets the same password “p” independently of u... by raverbashing on Monday January 30, 2017 @08:05AM (#13520778)
Thinking a bit about this problem, I'm a bit torn

In one side, a CLI offers a "better" way of using the product (as with a library it's easier to misuse something)

On another, issues like this

(But I guess in this specific case the issue is that encfs is not doing a minimal validity check of the password being provided)

It would be good if CLIs would/could be more consistent, but in the Unix/Gnu options world, probably it won't

Re:Cryptkeeper sets the same password “p” independently of u... by JoshTriplett on Monday January 30, 2017 @08:50AM (#13521100)
> In one side, a CLI offers a "better" way of using the product (as with a library it's easier to misuse something)

A CLI provides a better interactive interface, but a terrible programmatic interface.

Re:Cryptkeeper sets the same password “p” independently of u... by raverbashing on Monday January 30, 2017 @09:40AM (#13521504)
Yes, it is awful in the programmatic sense, I don't want to assemble command lines by hand or parse error messages

It is nice in the conceptual sense, because it usually fits the common use cases