I for-see what @revi stated above as a pretty plausible scenario, even the looking over someones shoulder is a plausible scenario.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 16 2015
Ah sorry, I thought Almanac wasn't a prototype but Drydock was. I was mistaken though.
Nov 15 2015
On another note, why doesn't Almanac use Passphrase for key storage?
Fixed in rARC66ab1c955d27ff7875f62eb51a0bd6c4770a7ae3.
Here is the version of phabricator and libphutil I use:
I definitely get that it's a prototype and I know not to file bugs against prototypes, but this interaction wasn't directly with Almanac but with a core Diffusion feature. Diffusion shouldn't use Almanac unless explicitly set to use it.
Nov 14 2015
I'm partly just guessing here but I think It's almost certainly my fault.
Thanks, I spent ~10 minutes on it but couldn't figure it out.
File should be getting attached to the paste, but isn't. I think I accidentally caused a side effect here when changing how the transaction works.
Actually something weird is going on... I can't edit pastes either, even if the Edit Policy is set to "All Users".
I'm not sure how to fix this without adding pastePHID to PhabricatorFile, which doesn't feel like the best approach.
I started looking at this. It seems like the file attached to the Paste has a view policy of no-one, whereas it should probably inherit the view policy of the parent Paste.
In general, I'd like better error messages for these kinds of situations. Even better would be some prescriptive text like "Go here, add this, click that".
Are you at HEAD? I don't expect Almanac to be needed during repo creation.
In T4245#144469, @joshuaspence wrote:This is the only thing that is blocking me from migrating all of our repositories from Gitlab to Phabricator. Is there a clear path forward here? If so, I could potentially work on this.
Not sure if this is a possible/practical scenario... but
+1. I agree that conflicting rules are un-resolvable (and thus a configuration issue), but in this case, even consistent rules cause an issue.
Nov 13 2015
In the general case, this is impossible to resolve. Suppose that you had conflicting linter rules, such as one whiche enforced that files end with a newline character and another which enforces that files do not end with a newline character.
MySQL version is 5.6.27-0ubuntu1.
> time ./bin/storage upgrade --namespace testT9773 --force --no-adjust Loading quickstart template... Applying patch 'phabricator:db.xhpast'... Applying patch 'phabricator:20150906.mailinglist.sql'... Applying patch 'phabricator:20150930.drydock.log.1.sql'... Applying patch 'phabricator:20151001.drydock.rname.1.sql'... Applying patch 'phabricator:20151002.dashboard.status.1.sql'... Applying patch 'phabricator:20151002.harbormaster.bparam.1.sql'... Applying patch 'phabricator:20151009.drydock.auth.1.sql'... Applying patch 'phabricator:20151010.drydock.auth.2.sql'... Applying patch 'phabricator:20151013.drydock.op.1.sql'... Applying patch 'phabricator:20151023.harborpolicy.1.sql'... Applying patch 'phabricator:20151023.harborpolicy.2.php'... Applying patch 'phabricator:20151023.patchduration.sql'... Applying patch 'phabricator:20151030.harbormaster.initiator.sql'... Applying patch 'phabricator:20151106.editengine.1.table.sql'... Applying patch 'phabricator:20151106.editengine.2.xactions.sql'... Applying patch 'phabricator:20151106.phame.post.mailkey.1.sql'... Applying patch 'phabricator:20151106.phame.post.mailkey.2.php'... Applying patch 'phabricator:20151107.phame.blog.mailkey.1.sql'... Applying patch 'phabricator:20151107.phame.blog.mailkey.2.php'... Applying patch 'phabricator:20151108.phame.blog.joinpolicy.sql'... Applying patch 'phabricator:20151108.xhpast.stderr.sql'... Applying patch 'phabricator:20151109.phame.post.comments.1.sql'... Applying patch 'phabricator:20151109.repository.coverage.1.sql'... Applying patch 'phabricator:20151109.xhpast.db.1.sql'... Applying patch 'phabricator:20151109.xhpast.db.2.sql'... Applying patch 'phabricator:20151110.daemonenvhash.sql'... Storage is up to date. Use 'storage status' for details. Declining to apply storage adjustments.
This is the only thing that is blocking me from migrating all of our repositories from Gitlab to Phabricator. Is there a clear path forward here? If so, I could potentially work on this.
If a Phurl doesn't have a name, should we still show the empty name property on the object view?
In T2543#144462, @jsturgeon wrote:Any way to bump the priority of this up?
Any way to bump the priority of this up?
(HTTP over public wireless has those properties, but using MFA and not using HTTPS is silly and the lack of HTTPS is a far greater problem than the larger MFA vulnerability window.)
could MITM the connection between the verifier and prover
Now that I think about this for a bit more there is a security concern here: In given two-factor authentication context, an attacker could MITM the connection between the verifier and prover, obtain the authentication credentials & a single OTP value, and then log in with these credentials within the current time step. This would allow for a second authenticated login, in sudo mode. I initially didn't think of this concern since the attacker can race, but in this case the new connection is created silently.
There are some attacks that could be performed on such MFA schemes but that are not applicable in phabricator's security model.
I filed this as a correctness bug, not as a security bug. There are some attacks that could be performed on such MFA schemes but that are not applicable in phabricator's security model.
I think the RFC should be followed.
So I just did some googling and came across the RFC for MFA, and this is
taken from the RFC:
I can't reproduce this either, nor does it reproduce on this install.
I'd like to understand the reason behind this before moving forward.
I don't want to introduce this level of complexity into Herald.