What’s the current best practice for auth on ToolForge?
I have a passphrase on my public ssh key. I’ll be accessing toolforge from my
MacBook which is protected with Apple’s Touch ID fingerprint scanner. I’ll be
nailing up a tmux session.
So, most of the time, there will be an active ssh sess
On Sat, Sep 30, 2017 at 9:28 AM, Roy Smith wrote:
> What’s the current best practice for auth on ToolForge?
>
> I have a passphrase on my public ssh key. I’ll be accessing toolforge from
> my MacBook which is protected with Apple’s Touch ID fingerprint scanner.
> I’ll be nailing up a tmux sess
Biometry in general may be acceptable, but fingerprints should be considered
weak protection, because you share that key with your environment all day, every
day. Getting someone's fingerprint is *really* easy. If your phone gets stolen,
chances are, the fingerprint needed to unlock it is right on
2017-09-30 21:00 GMT+02:00 Daniel Kinzler :
> Biometry in general may be acceptable, but fingerprints should be
> considered
> weak protection, because you share that key with your environment all day,
> every
> day. Getting someone's fingerprint is *really* easy. If your phone gets
> stolen,
> ch
> On Sep 30, 2017, at 3:49 PM, Michael Schönitzer
> wrote:
>
> I agree and even worse: if your password gets stolen you can change it but
> you cant change your fingerprint.
Actually, that’s not true. The problem is, I can only change it 9 times :-)
__
Am 30.09.2017 um 23:09 schrieb Roy Smith:
>> On Sep 30, 2017, at 3:49 PM, Michael Schönitzer
>> mailto:michael.schoenit...@wikimedia.de>>
>> wrote:
>>
>> I agree and even worse: if your password gets stolen you can change it but
>> you
>> cant change your fingerprint.
>
> Actually, that’s not tru
I’ve been exploring the enwiki database. I can find the page row for [[Iron]]
> MariaDB [enwiki_p]> select page_title from page where page_id = 14734;
> ++
> | page_title |
> ++
> | Iron |
> ++
It looks like it has the right number of revisions:
> Maria
The MediaWiki schema description is only valid for the underlying
database, you do not have access to that as a labs user - you just
have security-sanitised views. rev_text_ids are not useful to you as
you cannot access revision texts via the DBs - you must go through the
API.
On 1 October 2017 at
May I ask you, where you could find a database schema?
Regards, Martin
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 01.10.2017, 06:10, Alex Monk schrieb:
The MediaWiki schema description is only valid for the underlying
database, you do not have access to th
You mean, pages like MediaWiki has but modified for use in Labs? I
don't think there's MediaWiki-style documentation on that, I'd just
use the 'list databases', 'list tables' and 'describe $view' commands.
You can use 'show create view $view' to see some restrictions (e.g. it
selects NULL in place
Sorry - that was supposed to be 'show databases' and 'show tables'.
On 1 October 2017 at 05:26, Alex Monk wrote:
> You mean, pages like MediaWiki has but modified for use in Labs? I
> don't think there's MediaWiki-style documentation on that, I'd just
> use the 'list databases', 'list tables' and
Hmmm, interesting. I did read [[Help:Toolforge/Database]] where it says:
> Tool and Tools users are granted access to replicas of the production
> databases. Private user data has been redacted from these replicas (some rows
> are elided and/or some columns are made NULL depending on the table)
I'm talking about something like this: https://upload.wikimedia.org/wikipedia/commons/f/f7/MediaWiki_1.24.1_database_schema.svg , a graphical database schema, but I guess that it is outdated and needs to be updated.
Martin
Gesendet: Sonntag, 01. Oktober 2017 um 04:26 Uhr
Von: "Alex Monk
Yep, that is the MediaWiki API documentation.
On 1 October 2017 at 06:13, Roy Smith wrote:
> Hmmm, interesting. I did read [[Help:Toolforge/Database]] where it says:
>
> Tool and Tools users are granted access to replicas of the production
> databases. Private user data has been redacted from th
14 matches
Mail list logo
