* Authentication Rejected when pairing stereo headset
@ 2012-12-20 7:41 Andrey Voropaev
2012-12-20 8:04 ` Johan Hedberg
0 siblings, 1 reply; 10+ messages in thread
From: Andrey Voropaev @ 2012-12-20 7:41 UTC (permalink / raw)
To: linux-bluetooth
Hi! I'm trying to pair my bluetooth headset BTH220. In PC I have USB dongle
# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:5B:00:1C:7B ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:12771 acl:0 sco:0 events:221 errors:0
TX bytes:1431 acl:0 sco:0 commands:96 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'vandal-0'
Class: 0x420100
Service Classes: Networking, Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.1 (0x4) Revision: 0x149c
LMP Version: 2.1 (0x4) Subversion: 0x149c
Manufacturer: Cambridge Silicon Radio (10)
But when I try 'simple-agent hci0 XX:XX:XX' I always get error
Creating device failed: org.bluez.Error.AuthenticationRejected:
Authentication Rejected
I'm doing everything as root, so what could be the reason for
"Authentication Rejected"? Incompatible hardware? Wrong configuration?
In which direction should I be searching?
Thank you
Andrei Voropaev
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 7:41 Authentication Rejected when pairing stereo headset Andrey Voropaev
@ 2012-12-20 8:04 ` Johan Hedberg
2012-12-20 9:02 ` Andrey Voropaev
0 siblings, 1 reply; 10+ messages in thread
From: Johan Hedberg @ 2012-12-20 8:04 UTC (permalink / raw)
To: Andrey Voropaev; +Cc: linux-bluetooth
Hi Andrey,
On Thu, Dec 20, 2012, Andrey Voropaev wrote:
> when I try 'simple-agent hci0 XX:XX:XX' I always get error
>
> Creating device failed: org.bluez.Error.AuthenticationRejected:
> Authentication Rejected
>
> I'm doing everything as root, so what could be the reason for
> "Authentication Rejected"? Incompatible hardware? Wrong configuration?
>
> In which direction should I be searching?
The bluetoothd debug logs (run with -d switch) would be interesting as
well as the HCI level trace (for which you can use e.g. hcidump).
Johan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 8:04 ` Johan Hedberg
@ 2012-12-20 9:02 ` Andrey Voropaev
2012-12-20 9:19 ` Johan Hedberg
0 siblings, 1 reply; 10+ messages in thread
From: Andrey Voropaev @ 2012-12-20 9:02 UTC (permalink / raw)
To: linux-bluetooth
I've copied the output from hcidump -w to http://vandal.sdf-eu.org/hcidump.file
So far, I'm not sure how to add -d switch to bluetoothd. It is started
via dbus and this monster is not familiar to me. Can you please tell
me, which file should I edit to add the switch?
Andrey
On Thu, Dec 20, 2012 at 9:04 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> Hi Andrey,
>
> On Thu, Dec 20, 2012, Andrey Voropaev wrote:
>> when I try 'simple-agent hci0 XX:XX:XX' I always get error
>>
>> Creating device failed: org.bluez.Error.AuthenticationRejected:
>> Authentication Rejected
>>
>> I'm doing everything as root, so what could be the reason for
>> "Authentication Rejected"? Incompatible hardware? Wrong configuration?
>>
>> In which direction should I be searching?
>
> The bluetoothd debug logs (run with -d switch) would be interesting as
> well as the HCI level trace (for which you can use e.g. hcidump).
>
> Johan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 9:02 ` Andrey Voropaev
@ 2012-12-20 9:19 ` Johan Hedberg
2012-12-20 9:27 ` Andrey Voropaev
0 siblings, 1 reply; 10+ messages in thread
From: Johan Hedberg @ 2012-12-20 9:19 UTC (permalink / raw)
To: Andrey Voropaev; +Cc: linux-bluetooth
Hi Andrey,
First of all, please don't do top posting. It messes up the thread,
especially when mixed with inline quoting.
On Thu, Dec 20, 2012, Andrey Voropaev wrote:
> I've copied the output from hcidump -w to http://vandal.sdf-eu.org/hcidump.file
>
> So far, I'm not sure how to add -d switch to bluetoothd. It is started
> via dbus and this monster is not familiar to me. Can you please tell
> me, which file should I edit to add the switch?
Actually the hcidump helped a lot. It shows an issue on the kernel side:
< HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
bdaddr 00:1A:7D:25:2C:A4 capability 0x04 oob 0x00 auth 0x03
Capability: Reserved (OOB data not present)
Authentication: Dedicated Bonding (MITM Protection)
> HCI Event: Command Complete (0x0e) plen 10
IO Capability Request Reply (0x01|0x002b) ncmd 1
status 0x12 bdaddr 00:1A:7D:25:2C:A4
Error: Invalid HCI Command Parameters
The IO capability value 0x04 that the kernel is responding with is
invalid and shouldn't be sent to the controller. This was already fixed
quite long time ago (about 1 year ago) by the following patch from
Hemant Gupta: "Bluetooth: Send correct response to IO Capability Request"
It adds the following code to the IO capability handling to avoid 0x04
from being sent:
/* Change the IO capability from KeyboardDisplay
* to DisplayYesNo as it is not supported by BT spec. */
cp.capability = (conn->io_capability == 0x04) ?
0x01 : conn->io_capability;
It seems however that your kernel is missing this patch and the right
way forward would be to include it.
Johan
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 9:19 ` Johan Hedberg
@ 2012-12-20 9:27 ` Andrey Voropaev
2012-12-20 9:37 ` Johan Hedberg
2012-12-20 9:38 ` Andrei Emeltchenko
0 siblings, 2 replies; 10+ messages in thread
From: Andrey Voropaev @ 2012-12-20 9:27 UTC (permalink / raw)
To: Andrey Voropaev, linux-bluetooth
On Thu, Dec 20, 2012 at 10:19 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> First of all, please don't do top posting. It messes up the thread,
> especially when mixed with inline quoting.
Sorry. First time replying to list from gmail. Didn't pay attention to
that little mark at the bottom of the editor :)
> Actually the hcidump helped a lot. It shows an issue on the kernel side:
>
> < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
> bdaddr 00:1A:7D:25:2C:A4 capability 0x04 oob 0x00 auth 0x03
> Capability: Reserved (OOB data not present)
> Authentication: Dedicated Bonding (MITM Protection)
> > HCI Event: Command Complete (0x0e) plen 10
> IO Capability Request Reply (0x01|0x002b) ncmd 1
> status 0x12 bdaddr 00:1A:7D:25:2C:A4
> Error: Invalid HCI Command Parameters
>
> The IO capability value 0x04 that the kernel is responding with is
> invalid and shouldn't be sent to the controller. This was already fixed
> quite long time ago (about 1 year ago) by the following patch from
> Hemant Gupta: "Bluetooth: Send correct response to IO Capability Request"
>
> It adds the following code to the IO capability handling to avoid 0x04
> from being sent:
>
> /* Change the IO capability from KeyboardDisplay
> * to DisplayYesNo as it is not supported by BT spec. */
> cp.capability = (conn->io_capability == 0x04) ?
> 0x01 : conn->io_capability;
>
> It seems however that your kernel is missing this patch and the right
> way forward would be to include it.
I'm using Gentoo with "stable" version 3.5.7. Can you please tell me
which file shall contain this patch? I'll try to find "development"
version of kernel that contains it.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 9:27 ` Andrey Voropaev
@ 2012-12-20 9:37 ` Johan Hedberg
2012-12-20 10:22 ` Andrey Voropaev
2012-12-20 9:38 ` Andrei Emeltchenko
1 sibling, 1 reply; 10+ messages in thread
From: Johan Hedberg @ 2012-12-20 9:37 UTC (permalink / raw)
To: Andrey Voropaev; +Cc: linux-bluetooth
[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]
Hi Andrey,
On Thu, Dec 20, 2012, Andrey Voropaev wrote:
> > Actually the hcidump helped a lot. It shows an issue on the kernel side:
> >
> > < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
> > bdaddr 00:1A:7D:25:2C:A4 capability 0x04 oob 0x00 auth 0x03
> > Capability: Reserved (OOB data not present)
> > Authentication: Dedicated Bonding (MITM Protection)
> > > HCI Event: Command Complete (0x0e) plen 10
> > IO Capability Request Reply (0x01|0x002b) ncmd 1
> > status 0x12 bdaddr 00:1A:7D:25:2C:A4
> > Error: Invalid HCI Command Parameters
> >
> > The IO capability value 0x04 that the kernel is responding with is
> > invalid and shouldn't be sent to the controller. This was already fixed
> > quite long time ago (about 1 year ago) by the following patch from
> > Hemant Gupta: "Bluetooth: Send correct response to IO Capability Request"
> >
> > It adds the following code to the IO capability handling to avoid 0x04
> > from being sent:
> >
> > /* Change the IO capability from KeyboardDisplay
> > * to DisplayYesNo as it is not supported by BT spec. */
> > cp.capability = (conn->io_capability == 0x04) ?
> > 0x01 : conn->io_capability;
> >
> > It seems however that your kernel is missing this patch and the right
> > way forward would be to include it.
>
> I'm using Gentoo with "stable" version 3.5.7. Can you please tell me
> which file shall contain this patch? I'll try to find "development"
> version of kernel that contains it.
The file involved is net/bluetooth/hci_event.c. I've attached the patch
to this email.
An quicker way for you to overcome the issue is to change the user space
side pairing call to pass "DisplayYesNo" instead of "KeyboardDisplay" to
BlueZ. I.e. edit the simple-agent script, find the (two) occurrences of
"KeyboardDisplay" and change them to "DisplayYesNo" and try to pair
again.
Johan
[-- Attachment #2: 0001-Bluetooth-Send-correct-response-to-IO-Capability-Req.patch --]
[-- Type: text/plain, Size: 1459 bytes --]
>From 7a7f1e7c857959f5298020969741e389f21edbae Mon Sep 17 00:00:00 2001
From: Hemant Gupta <hemant.gupta@stericsson.com>
Date: Mon, 16 Jan 2012 13:34:29 +0530
Subject: [PATCH] Bluetooth: Send correct response to IO Capability Request
This patch sends correct IO Capability response to remote device
in case Local Device supports KeyBoardDisplay IO Capability as
this capability is not valid as per BT spec for IO capability
Request Reply Command.
This capability is mapped to DisplayYesNo which is in accordance
with BT spec.
Signed-off-by: Hemant Gupta <hemant.gupta@stericsson.com>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
---
net/bluetooth/hci_event.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
index 6fb9016..041a35e 100644
--- a/net/bluetooth/hci_event.c
+++ b/net/bluetooth/hci_event.c
@@ -2965,7 +2965,10 @@ static inline void hci_io_capa_request_evt(struct hci_dev *hdev, struct sk_buff
struct hci_cp_io_capability_reply cp;
bacpy(&cp.bdaddr, &ev->bdaddr);
- cp.capability = conn->io_capability;
+ /* Change the IO capability from KeyboardDisplay
+ * to DisplayYesNo as it is not supported by BT spec. */
+ cp.capability = (conn->io_capability == 0x04) ?
+ 0x01 : conn->io_capability;
conn->auth_type = hci_get_auth_req(conn);
cp.authentication = conn->auth_type;
--
1.8.0.2
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 9:27 ` Andrey Voropaev
2012-12-20 9:37 ` Johan Hedberg
@ 2012-12-20 9:38 ` Andrei Emeltchenko
2012-12-20 10:51 ` Andrey Voropaev
1 sibling, 1 reply; 10+ messages in thread
From: Andrei Emeltchenko @ 2012-12-20 9:38 UTC (permalink / raw)
To: Andrey Voropaev; +Cc: linux-bluetooth
Hi Andrey,
On Thu, Dec 20, 2012 at 10:27:15AM +0100, Andrey Voropaev wrote:
> On Thu, Dec 20, 2012 at 10:19 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> > First of all, please don't do top posting. It messes up the thread,
> > especially when mixed with inline quoting.
>
> Sorry. First time replying to list from gmail. Didn't pay attention to
> that little mark at the bottom of the editor :)
>
> > Actually the hcidump helped a lot. It shows an issue on the kernel side:
> >
> > < HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9
> > bdaddr 00:1A:7D:25:2C:A4 capability 0x04 oob 0x00 auth 0x03
> > Capability: Reserved (OOB data not present)
> > Authentication: Dedicated Bonding (MITM Protection)
> > > HCI Event: Command Complete (0x0e) plen 10
> > IO Capability Request Reply (0x01|0x002b) ncmd 1
> > status 0x12 bdaddr 00:1A:7D:25:2C:A4
> > Error: Invalid HCI Command Parameters
> >
> > The IO capability value 0x04 that the kernel is responding with is
> > invalid and shouldn't be sent to the controller. This was already fixed
> > quite long time ago (about 1 year ago) by the following patch from
> > Hemant Gupta: "Bluetooth: Send correct response to IO Capability Request"
> >
> > It adds the following code to the IO capability handling to avoid 0x04
> > from being sent:
> >
> > /* Change the IO capability from KeyboardDisplay
> > * to DisplayYesNo as it is not supported by BT spec. */
> > cp.capability = (conn->io_capability == 0x04) ?
> > 0x01 : conn->io_capability;
> >
> > It seems however that your kernel is missing this patch and the right
> > way forward would be to include it.
>
> I'm using Gentoo with "stable" version 3.5.7. Can you please tell me
> which file shall contain this patch? I'll try to find "development"
> version of kernel that contains it.
The patch is below:
commit 7a7f1e7c857959f5298020969741e389f21edbae
Author: Hemant Gupta <hemant.gupta@stericsson.com>
Date: Mon Jan 16 13:34:29 2012 +0530
Bluetooth: Send correct response to IO Capability Request
This patch sends correct IO Capability response to remote device
in case Local Device supports KeyBoardDisplay IO Capability as
this capability is not valid as per BT spec for IO capability
Request Reply Command.
This capability is mapped to DisplayYesNo which is in accordance
with BT spec.
Signed-off-by: Hemant Gupta <hemant.gupta@stericsson.com>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
index 6fb9016..041a35e 100644
--- a/net/bluetooth/hci_event.c
+++ b/net/bluetooth/hci_event.c
@@ -2965,7 +2965,10 @@ static inline void hci_io_capa_request_evt(struct
hci_dev *hdev, struct sk_buff
struct hci_cp_io_capability_reply cp;
bacpy(&cp.bdaddr, &ev->bdaddr);
- cp.capability = conn->io_capability;
+ /* Change the IO capability from KeyboardDisplay
+ * to DisplayYesNo as it is not supported by BT spec. */
+ cp.capability = (conn->io_capability == 0x04) ?
+ 0x01 :
conn->io_capability;
conn->auth_type = hci_get_auth_req(conn);
cp.authentication = conn->auth_type;
Best regards
Andrei Emeltchenko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 9:37 ` Johan Hedberg
@ 2012-12-20 10:22 ` Andrey Voropaev
2012-12-20 11:06 ` Andrey Voropaev
0 siblings, 1 reply; 10+ messages in thread
From: Andrey Voropaev @ 2012-12-20 10:22 UTC (permalink / raw)
To: linux-bluetooth
On Thu, Dec 20, 2012 at 10:37 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> An quicker way for you to overcome the issue is to change the user space
> side pairing call to pass "DisplayYesNo" instead of "KeyboardDisplay" to
> BlueZ. I.e. edit the simple-agent script, find the (two) occurrences of
> "KeyboardDisplay" and change them to "DisplayYesNo" and try to pair
> again.
Thanks. This trick worked (though there was only 1 KeyboardDisplay).
I've paired the device and now hcitool con reports
Connections:
< ACL 00:1A:7D:25:2C:A4 handle 43 state 1 lm MASTER AUTH ENCRYPT
And I get
hcitool info 00:1A:7D:25:2C:A4
Requesting information ...
BD Address: 00:1A:7D:25:2C:A4
OUI Company: cyber-blue(HK)Ltd (00-1A-7D)
Device Name: BTH220
LMP Version: 2.1 (0x4) LMP Subversion: 0x14fa
Manufacturer: Cambridge Silicon Radio (10)
Features page 0: 0xff 0xfe 0x0f 0xc6 0x8b 0xef 0x59 0x83
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO> <EDR ACL 2 Mbps>
<EDR ACL 3 Mbps> <inquiry with RSSI> <extended SCO>
<EV4 packets> <EV5 packets> <AFH cap. slave> <3-slot EDR ACL>
<5-slot EDR ACL> <sniff subrating> <pause encryption>
<AFH cap. master> <EDR eSCO 2 Mbps> <EDR eSCO 3 Mbps>
<3-slot EDR eSCO> <extended inquiry> <simple pairing>
<encapsulated PDU> <non-flush flag> <LSTO> <inquiry TX power>
<extended features>
Features page 1: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
But seems like Alsa still does not see it. I've added
pcm.bluetooth {
type bluetooth
device 00:1A:7D:25:2C:A4
profile "auto"
}
to /etc/asound.conf, restarted alsasound, but bluetooth does not show
up among available outputs. Well, I'm almost there. The Skype has
"bluetooth" in the list of devices and it works. Just mplayer does not
want to work with option
-ao alsa:device=bluetooth
Probably there's some capabilities problem. Any advice here? :) Sorry ...
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 9:38 ` Andrei Emeltchenko
@ 2012-12-20 10:51 ` Andrey Voropaev
0 siblings, 0 replies; 10+ messages in thread
From: Andrey Voropaev @ 2012-12-20 10:51 UTC (permalink / raw)
To: linux-bluetooth
On Thu, Dec 20, 2012 at 10:38 AM, Andrei Emeltchenko
<andrei.emeltchenko.news@gmail.com> wrote:
>
> The patch is below:
>
> commit 7a7f1e7c857959f5298020969741e389f21edbae
> Author: Hemant Gupta <hemant.gupta@stericsson.com>
> Date: Mon Jan 16 13:34:29 2012 +0530
>
> Bluetooth: Send correct response to IO Capability Request
>
> This patch sends correct IO Capability response to remote device
> in case Local Device supports KeyBoardDisplay IO Capability as
> this capability is not valid as per BT spec for IO capability
> Request Reply Command.
> This capability is mapped to DisplayYesNo which is in accordance
> with BT spec.
>
> Signed-off-by: Hemant Gupta <hemant.gupta@stericsson.com>
> Acked-by: Marcel Holtmann <marcel@holtmann.org>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
>
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 6fb9016..041a35e 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -2965,7 +2965,10 @@ static inline void hci_io_capa_request_evt(struct
> hci_dev *hdev, struct sk_buff
> struct hci_cp_io_capability_reply cp;
>
> bacpy(&cp.bdaddr, &ev->bdaddr);
> - cp.capability = conn->io_capability;
> + /* Change the IO capability from KeyboardDisplay
> + * to DisplayYesNo as it is not supported by BT spec. */
> + cp.capability = (conn->io_capability == 0x04) ?
> + 0x01 :
> conn->io_capability;
> conn->auth_type = hci_get_auth_req(conn);
> cp.authentication = conn->auth_type;
Interesting. This patch is present in the sources for 3.5.7 kernel
that I have. But somehow it does not work. Fixing simple-agent did
work though.
Andrei
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Authentication Rejected when pairing stereo headset
2012-12-20 10:22 ` Andrey Voropaev
@ 2012-12-20 11:06 ` Andrey Voropaev
0 siblings, 0 replies; 10+ messages in thread
From: Andrey Voropaev @ 2012-12-20 11:06 UTC (permalink / raw)
To: linux-bluetooth
On Thu, Dec 20, 2012 at 11:22 AM, Andrey Voropaev
<voropaev.andrey@gmail.com> wrote:
> But seems like Alsa still does not see it. I've added
>
> pcm.bluetooth {
> type bluetooth
> device 00:1A:7D:25:2C:A4
> profile "auto"
> }
>
>
> to /etc/asound.conf, restarted alsasound, but bluetooth does not show
> up among available outputs. Well, I'm almost there. The Skype has
> "bluetooth" in the list of devices and it works. Just mplayer does not
> want to work with option
>
> -ao alsa:device=bluetooth
Sorry. I've found the solution.
https://wiki.archlinux.org/index.php/Bluetooth gives different
configuration for Alsa
pcm.btheadset {
type plug
slave {
pcm {
type bluetooth
device XX:XX:XX:XX:XX:XX
profile "auto"
}
}
hint {
show on
description "BT Headset"
}
}
ctl.btheadset {
type bluetooth
}
With this configuration the headset becomes visible in aplay -L.
So, the issue is resolved. Thank you for help!
Andrei
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2012-12-20 11:06 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-20 7:41 Authentication Rejected when pairing stereo headset Andrey Voropaev
2012-12-20 8:04 ` Johan Hedberg
2012-12-20 9:02 ` Andrey Voropaev
2012-12-20 9:19 ` Johan Hedberg
2012-12-20 9:27 ` Andrey Voropaev
2012-12-20 9:37 ` Johan Hedberg
2012-12-20 10:22 ` Andrey Voropaev
2012-12-20 11:06 ` Andrey Voropaev
2012-12-20 9:38 ` Andrei Emeltchenko
2012-12-20 10:51 ` Andrey Voropaev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).