no way to specify the password

Bug #566075 reported by Rolf Leggewie on 2010-04-18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linphone (Ubuntu)

Bug Description

Binary package hint: linphone

I don't see a way for the current lucid linphone 3.2.1-1ubuntu4 to specify a password for a SIP account. Registration with the SIP server naturally fails.

Tommy Trussell (tommy-trussell) wrote :

I am using an earlier version -- linphone 3.1.2 on Ubuntu 9.10 Karmic, and when I use a SIP account for the first time, linphone prompts for the password and apparently saves it. There is an "Erase all passwords" button on the manage SIP Accounts page. The later version may be failing in trying to use the system keyring. (This is speculation on my part; I don't know.)

UNFORTUNATELY I have not been able to get linphone 3.2.1 to work at all on Ubuntu 10.4 Lucid (crashes on startup -- see Bug #582268).

I have found linphone to work really well on my Karmic machine.

DiagonalArg (diagonalarg) wrote :

I'm still seeing this bug in 3.3.2-4 under Ubuntu 12.04. It never asks for a password and in the debug log, registration fails.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linphone (Ubuntu):
status: New → Confirmed
Rolf Leggewie (r0lf) on 2016-07-19
Changed in linphone (Ubuntu):
importance: Undecided → Critical
Colin Sindle (csindle) wrote :

IIRC, some SIP providers "successfully" register all attempts as a security/DOS protection technique (obviously, later, when an [unauthorised] call is attempted, it fails.).

Perhaps, because there is never a SIP password authentication challenge, this is why Linphone never prompts for a password.

It seems that persisting an account's password should be decoupled from the future possibility of any provider needing it. I.e. the password is a property of the account, not the provider's implementation (SIP stack's behaviour) at some arbitrary point in the future.

Simon Vall (simon.vall) on 2017-01-24
Changed in linphone (Ubuntu):
assignee: nobody → Simon Vall (simon.vall)
assignee: Simon Vall (simon.vall) → nobody
Armando Padilla (1+ar08) on 2017-02-25
Changed in linphone (Ubuntu):
status: Confirmed → Fix Committed
Rolf Leggewie (r0lf) on 2017-02-26
Changed in linphone (Ubuntu):
status: Fix Committed → Confirmed
Changed in linphone (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Confirmed
mannjunath (manjunathcn) wrote :

I'm still seeing this bug in 3.3.2-4 under Ubuntu 12.04. It never asks for a password and in the debug log, registration fails.

Changed in linphone (Ubuntu):
assignee: nobody → mannjunath (manjunathcn)
Rolf Leggewie (r0lf) on 2017-05-02
Changed in linphone (Ubuntu):
assignee: mannjunath (manjunathcn) → nobody
T (mightyowl) wrote :

I have a Dell XPS 15 and connect over USB C to a display port hub to a HDMI external monitor.

Sometime in the past few months I ran into this issue. When I would lock my screen (xflock4) or go into standby the computer would lock up on resume and I had plenty of the following in the logs.

drm:intel_wait_ddi_buf_idle [i915_bpo]] *ERROR* Timeout waiting for DDI BUF B idle bit

It was fine on startup, as long as it didn't lock the screen.

I had been running kernel 4.4.0 on Xubuntu 16.04

I upgraded to kernel to 4.10.0 and my issue is now fixed.

T (mightyowl) wrote :

Oops, updated the wrong bug

Luisa Casey (luisa.casey) wrote :

Adding a property or field for passwords seems to be a very plausible thing to do anyway. Has anyone captured the traffic for debugging purposes btw?

Luisa Casey
mail: <email address hidden>
phone: 04 67 33 67 33


information type: Public → Public Security
Changed in linphone (Ubuntu):
status: Confirmed → New
status: New → Confirmed
To post a comment you must log in.
This report contains Public Security information  Edit
Everyone can see this security related information.

Other bug subscribers