Comment by zeznania roczne July 22, Reply. Comment by edeklaracje gov July 25, Reply. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Email Address:. Pidgin Client Installation for Windows and Configuration for Lync Pidgin merupakan aplikasi instan messenger multiplatform windoz, linux,Mac OS dan juga multi client banyak chat network yang didukung dan juga mendukung multi ID, kita bisa mengaktifkan 2 atau lebih ID yahoo secara bersamaan misalnya Detil: Pidgin is an easy to use and free chat client used by millions.
Run Pidgin. Pada Add Account window, masukan Informasi Account : a. Have to check my logs on that one. I do see presence notifications in the debug log though, although they don't change the status icon in Pidgin because they are all basic-status open. I've added a bool checkbox to indicate we want to use Kerberos. Not sure if this is the "correct" or "preferred" way of doing things, but ItWorksForMe?
If not, I'll check your commit out and convert the gaim references, check back in, then add my Kerberos stuff. Don't worry about your code for now; I think it's more important to get this working, and then it can be cleaned up if necessary. Did you remember to 'cg push'? I tested the latest changes. Looks good. I will test the another changes and I will move the good changes to the stable branch in the GIT repository fixer.
You must have the Use Proxy box checked and specify your OCS server in the proxy section of the account advanced page for it to even sort of work. But now I have, and I tested it. I'm working on it.
Remember my plugin works only if you are using a Proxy Server. I mean if the server backs the " Proxy Authenticated message". If you are not using a proxy my plugin will connect, but after every transaction with the server will be rejected. If you server are using a proxy depend of the LCS administrator. Is very common to use a proxy but sometimes could change.
I only compile my plugin for Linux. I don't use Windows. I know some people have compiled for Windows but I don't have it. May if they sedn me the module I will up in the SF project. I have in my own server the first releases, but I think is better to have the modules in the SF Server.
My server is unstable sometimes ;. I will release the new version 1. I think in 3 or 4 days. I'm unable to with OCS From what I can tell, we need to be signing all messages we send to the server after we authenticate. Do you agree? See my comment for the pointer to the Microsoft docs where they make it clear this is needed.
It's a pretty complicated API that I'm trying to wrap my head around, without much luck so far in getting anything to work. If anybody has advice or help, it'd be quite appreciated.
So we're now in the same position with Kerberos as we were with NTLM - we can authenticate and send messages by reauthenticating for each one, but we can't respond to messages because you can't reauthenticate when you respond, you have to use existing auth and sign the message. Hi all, finally after a lot of tests, debug and reverse enginering I was able to sign my sip messages.
I've implemented successfully even the presence protocol. All others messages are signed using a session key. Unfortunately I've no time to enhance the sipe plugin, however I'm happy to share my kwnoledge. Essentially these are the steps needed:.
No difference with sipe implementation. Don't ask me why. Please, send me the code, I can do the merge with the Git server. I appreciate so much if you send the code. The Sipe users and me need this changes,. Ok, thank you, but I appreciate so much if you send the code. I remains your name with all rights inside the code. Your changes are free, don't you? Can you please attach your patch to this bug?
Sorry for the late in the answeer. I'm working on proprietary stack, not sipe or pidgin related. Unfortunately I can't share it completely. I've to continue here or in private by email? You are the three people with this restriction to share the code so far. The problem with this project is the lack time. We have the talent and the skills, but we don't have time to complete the protocol because is just a free time project. How you wish. Our plugin is completely free, then if you attach a file or send an email, the code will be free and whatever can see it.
Very interested problem is the propietary world. They take code from open sources projects but they don't share the new code added. However I understand your problem. I work too in a propietary company ;. I prefere to continue here. I like also to clarify my position.
My company use a proprietary SIP stack, derived from a commercial one not pidgin or open source related. My big problem is the time. I would like to improve directly sipe code but I've no time to write and test code.
I'll do my best. Franco, what do you use for the RC4 key for signing messages? Is it the value we put into the gssapi-data attribute? Have you gotten verification of the rspauth attribute the server sets working? Thanks for your help! Trivial question: is it possible to download latest sources including your path? Clicking on the link I see only the diff files.
Before signing however weneed to improve the NTLM authentication. Respect the sipe original files:. Any advice would be appreciated, I'm running out of ideas of how to test this. I got the NTLM signing working! I just pushed my changes and test code. To all you great people working on the solution.
I wish I had the knowledge and skills to accomplish what you are doing. Great work. Incoming messages' signatures are being checked, and outgoing messages are being signed. There is plenty of work left to make everything work smoothly, but the biggest hurdles are now behind us!
Does this plug-in only work with Pidgin? Will it work with Adium? If not, is there already one for Adium or is there one under development? I just pulled the mob branch and gave it a quick test. This behavior is approximately equivalent to what I was experiencing earlier, before the recent work. The old problem with the authentication has gone.
Now sipe are using signing support instead the trick. I had a code very similar to your code in my machine, but the help comming from Kiraly was amazing. I needed too how the message was formed and other things. I think is a problem with the certificates and the TLS support crashed on the sipe. I'm searching the problem. To follow bugs will be hard now. I will release the sipe version 1. Happy to see my contribute has been appreciated.
Sorry again for my slow answeers, as I said it's a busy period. About sipe, what's the current point? The signing has been completely solved? I've to start giving some trick about presence? I pushed another patch to fix the bug when Pidgin retrieve the contacts from the server. May be it fixed the problems describe by other users. I fixed it because I had that problem. Now I can connect to the server n-times without error. Gabriel, are you planning to work in them?
I said to avoid duplicate effort. First of all: Thank you for your effort! Are your changes specific to LCS ? I've implemented only OCS My goal was only to publish my presence status, so I've implemented only that part of standard.
First point to define is the epid-UUID relation. I verified some strange behaviour using only epid header. Exactly I was not able to publish the presence status of a new user just created. Using both epid-UUID the presence status works fine in all scenario.
There are some relationship to be respected. Based on my tests the epid should be always the same for a client and UUID consequently.
A good technique could be to relate epid to mac address. In call transactions I use only epid header. Hi, I downloaded a tar of the mob branch last night and have been able to successfully build and use sipe to connect to my TLS-enabled LCS system here.
Authentication seems to work, although it looks like any attempts by me to add contacts or send or receive messages causes the socket to get aborted tho Pidgin still thinks my status is Available.. I can provide my debugging output if it's of any use to further development efforts.
In my settings, I made sure to:. I just pushed some more changes, getting closer to 2-way IM. Anyway, getting extremely close. Communicator even pops up a little notification saying the Pidgin user is inviting you to chat. I got one of our designers here at Novell to whip up an icon for pidgin-sipe. Any objections to this? Also, what about renaming it in the user-facing strings to "Communication Server" or something? I'm not sure anybody would know to find the functionality they're looking for under "SIPE".
I wanted to thank you all for your effort on this plugin, I too am in this situation since in my company they retired jabber and implemented OCS Could you make a capture with wireshark? I've no experience with IM.
I had your scenario using only NTLM authentication whitout signing. In outcoming call from my terminal the invite was authenticated, but ACK rejected because not signed. I just pushed my changes including the new icon. It handles the remote user closing their conversation window, the local user closing their, etc - if either later wants to send an IM to the other, it should seamlessly do the INVITE handshake properly. I'd like to try this out with AdiumX.
Although I've checked out Adium's sources and made very minor changes before, I'm not sure what else might be required. The icon is cool too. Because the name Microsoft LCS are very ugly for me. How do you see? If are agree, I will change the name in SourceForge? By the way, anybody running openSUSE Yes I do. I'm able to successfully connect to the OCS server, and obtain a list of contacts. One other thing, the contacts are all shown as 'offline', until I receive an IM from one.
What version of Pidgin do you have? I have 2. Can you figure out what's causing it with gdb or printf? I'm running 2. Any suggestions about the contacts all showing as 'offline'?
Seems as if the plugin isn't querying contact status' on initial connect? Here's the backtrace with gdb:. I think I have some corrupt entries in my LCS server-based contact list and when Pidgin tries to setup my contact list it gets non-standard read non UTF8 characters in the list it gets back from the server. I almost have a good function but I have a question to Franco.
Franco, What is the namespace ID? But I always a got a error but I have a functions to generate this. Tonight I will finish this I think I am very close. You can ignore my comment above about UTF8. My problem was that the number of groups in the buddy list was hard-coded at 10 in sipe.
I had like I'll try to work on making that dynamic. Yes, I see is the same implementation taken from the same place. Thank you very much. I pushed the changes taken your code. Works great, the server doesn't give a error with the changes. Saw your change to allow setting the User Agent - have you found that to be necessary in some circumstances? Good job on the uuid stuff, guys. Fixxxer, what's left to do with presence?
Yes, i was unable to connect successfully until i changed the User-Agent to the one used by OC Might be a special of our server configuration. If you want to look into it i can provide a dump next week. Replying to DanielBeichl :. Daniel- what is the User-Agent used by OC ? Does anyone else experience this?
I can set up an OCS at home and test if necessary. I'm getting a segfault before SIPE even tries to connect since this commit. Here's some output from gdb:. With the error segmentation fault is very strange.
Please send a gdb output more complete. The last change tries to get the Mac Address from your network interface. But of course only works under Linux. Shouldn't it be using the epid value instead?
Could probably generate them in the login callback? Also, when you run the code you committed, does it crash when you try to login? I'm getting the same crash that djflux and Rondom see:. Any interest in chatting in pidgin-sipe on freenode? I'll idle there in case somebody wants to chat.
Perhaps i can elaborate on this problem I have pushed a corrected version. Please test if it fixes this error. Regarding the user-agent Warning: lcs. Did you mean to make nmac 13 bytes instead of 12? And should the default be 12 or 13 bytes long instead of the current 8 ? If we want to use the macaddress as the epid and represent it as a string we need 13 bytes. As the epid appears to be just a random ascii string the fallback to a 8 byte value seems fine to me.
Yes, it worked on my machine always without error. But I see the code had a little problem. The use of the MacAddress? We can use 8 byte, 10 byte, whatever how EPID. Of course the idea is to have an unique value by client then 12 bytes are not bad idea instead 8 so maybe never would be repeat. Below is an example where I see " Malformed Contact" servername and username replaced. This is with OCS Let me know if you need any more output.
Could you give some details about your system i. I tried generating r12rs uuid from his posted logs and it appears to contain only the last two bytes of the uuid. I failed to reproduce this tried x86 and x Do the tests show a problem on your system? I am trying to use the latest code from git. I am connecting over a vpn using TLS and port with username and server name different. I am unable to connect and pidgin seems to just hang attempting the connect. I am successful in getting Miranda to connect over a vpn with similar connect info.
Are you using vpnc? Because VPNC creates a new device called tun0. May be this is the problem, I use vpnc. Yes, I am using vpnc to connect to the company. I just tried setting my public IP to the one assigned to tun0, but still have basically the same sip conversation flow in debug.
I have IPv6 disabled entirely on my system. I disabled all other protocols I am using and then just check-mark enabled the LCS protocol connection I have defined. I get that same debug flow and the "connection" icon just rotates like it is trying.
But by then the connection is done from the servers perspective. Has anyone gotten this to build against mignw32? I have been building the plugin on my linux server, and the latest release works great on OCS , but I would like to build a windows DLL to distribute for testing. I also don't see the reason to initialize activity to 'available'. If you has never used the Microsoft Office Communicator aka the official Windows Client for OCS they never could see you online only you to them.
But if you login in the that official client at least one time, all works fine. It was my case but after I connected with this Windows client inclusive I saved the Options settings I can everything. My contacs can see me online, and they can write messages like me. Yes, I was. Also, the below part was because I sometimes I got another value different to 'busy','away','avalaible', then pidgin doesn't put a correct status to the almost all contacts inclusive doesn't put the 'avalaible' , may be OCS has another status I got a number I think I don't remember fine.
Now, I'm working in the last problem I found: after some minutes may be hours pidgin lost the SSL connection and crash. I always get it. Also, the below part was because I sometimes I got another value different to 'busy','away','avalaible', then pidgin doesn't put a correct status to the almost all contacts inclusive doesn't put the 'avalaible'.
Are you saying that wasn't happening? Also I do not show up as 'online' to any of my contacts until I send a message to one of them. Your fix of logging in with OCS in windows doesnt seem to fix the problem for me :. Passing NULL to a printf-style function can crash in a number of instances when glib's wrappers are in use, and will definitely crash on Windows, since internally we use glib's functions.
Glib has a bug that has yet to be fixed where a number of the printf family functions use Glib's internal implementation, which crashes on NULL input. You need to protect against that or you'll get complaints when someone finally gets around to testing this on Windows because it'll crash all the time. I am testing the last Mob Commint on Fedora 9 version: pidgin Is anyone working on supporting conversation invitations, etc having a 3-way conversation for example?
Also I fixed the group parsing so it's no longer hardcoded to only support 10 groups. I'm getting a segfault when connecting using the latest commit. I'm able to connect over TLS fetching contact status still doesnt work , segfault happens as soon as I hit 'send' on a message to a contact.
This was causing the header to be not found. I changed the code to be case insensitive for headers. Correction here: The buddy at the other end receive the invite. I can see the messages he send me but it is not working in the other way from me to others. Yes, I have some changes little bit.
Please be patient, I don't have a lot time to work my free time is a little bit. But I have some changes ready about Presence. I hope to commit them tonight. I'm trying to be standard with my changes to avoid another OCS versions lose compatibility. If pidgin initiates the chat, then it is able to send messages out. I'm working on this problem now. Just committed support for saving buddy aliases to the server and loading them properly from the server when we log in.
Other than that, everything works as expected. The connection closes but pidgin crash with a segfault. It was fixed. I will continue with my Presence changes.
This appears to have fixed the segfaults I was getting. State of the Bird Q3 2. GSoC Retrospective 2. Pidginchat libgnt 2. Edit this page. Linux We do not provide pre-built packages for Linux and Unix distributions.
0コメント