http://permalink.gmane.org/gmane.comp.gnu.shishi.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.gnu.shishi.general/513 _______________________________________________ Help-shishi mailing list Help-shishi< at >gnu.org http://lists.gnu.org/mailman/listinfo/help-shishi Simon Josefsson 2008-11-17T10:36:42 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/512 _______________________________________________ Help-shishi mailing list Help-shishi< at >gnu.org http://lists.gnu.org/mailman/listinfo/help-shishi Simon Josefsson 2008-11-10T08:08:02 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/511 All, I plan to release libtasn1 v2.0 in a few days. Please test this daily build for problems: http://daily.josefsson.org/libtasn1/libtasn1-20081105.tar.gz btw, I've created a Redmine instance to track bugs, plan releases, wiki pages, and more, see: http://redmine.josefsson.org/wiki/libtasn1 /Simon Simon Josefsson 2008-11-05T13:49:24 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/510 Hi Russ. I am building new Shishi/GSS packages (don't worry, I won't upload to unstable until after lenny has been released) and ran into: I: libgss0: no-symbols-control-file usr/lib/libgss.so.0.0.24 N: N: Although the package includes a shared library, the package does not N: have a symbols control file. N: N: dpkg can use symbols files in order to generate more accurate library N: dependencies for applications, based on the symbols from the library N: that are actually used by the application. N: N: Refer to the dpkg-gensymbols(1) manual page for details. N: N: Severity: wishlist; Certainty: certain N: I tried to read up about this... I am able to generate a symbols list using 'dpkg-gensymbols -plibgss0 -Ofoo': libgss.so.0 libgss0 #MINVER# GSS_C_NT_ANONYMOUS< at >Base 0.0.24-1 GSS_C_NT_ANONYMOUS_static< at >Base 0.0.24-1 GSS_C_NT_EXPORT_NAME< at >Base 0.0.24-1 GSS_C_NT_EXPORT_NAME_static< at >Base 0.0.24-1 GSS_C_NT_HOSTBASED_SERVICE< at >Base 0.0.24-1 ... However, I haven't found a simple to under Simon Josefsson 2008-10-07T19:41:41 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/509 FYI: The status of the shishi source package in Debian's testing distribution has changed. Previous version: 0.0.36-2 Current version: 0.0.37-1 Debian testing watch 2008-07-09T16:39:16 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/508 Hi! Do you have libgcrypt installed? Which version of Shishi are you using? /Simon vishal <vicky_recw< at >yahoo.com> writes: Simon Josefsson 2008-06-30T09:22:54 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/507 _______________________________________________ Help-shishi mailing list Help-shishi< at >gnu.org http://lists.gnu.org/mailman/listinfo/help-shishi vishal 2008-06-29T08:30:16 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/506 Accepted: libpam-shishi_0.0.37-1_i386.deb to pool/main/s/shishi/libpam-shishi_0.0.37-1_i386.deb libshisa-dev_0.0.37-1_i386.deb to pool/main/s/shishi/libshisa-dev_0.0.37-1_i386.deb libshisa0_0.0.37-1_i386.deb to pool/main/s/shishi/libshisa0_0.0.37-1_i386.deb libshishi-dev_0.0.37-1_i386.deb to pool/main/s/shishi/libshishi-dev_0.0.37-1_i386.deb libshishi0_0.0.37-1_i386.deb to pool/main/s/shishi/libshishi0_0.0.37-1_i386.deb shisa_0.0.37-1_i386.deb to pool/main/s/shishi/shisa_0.0.37-1_i386.deb shishi-common_0.0.37-1_all.deb to pool/main/s/shishi/shishi-common_0.0.37-1_all.deb shishi-dbg_0.0.37-1_i386.deb to pool/main/s/shishi/shishi-dbg_0.0.37-1_i386.deb shishi-doc_0.0.37-1_all.deb to pool/main/s/shishi/shishi-doc_0.0.37-1_all.deb shishi-kdc_0.0.37-1_i386.deb to pool/main/s/shishi/shishi-kdc_0.0.37-1_i386.deb shishi_0.0.37-1.diff.gz to pool/main/s/shishi/shishi_0.0.37-1.diff.gz shishi_0.0.37-1.dsc to pool/main/s/shishi/shishi_0.0.37-1.dsc shishi_0.0.37-1_i386.deb to pool/main/s/shishi/s Debian Installer 2008-06-25T09:17:26 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/505 Uploaded. /Simon Archive Administrator <dak< at >ftp-master.debian.org> writes: Simon Josefsson 2008-06-25T08:35:06 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/504 shishi_0.0.37-1_i386.changes uploaded successfully to localhost along with the files: shishi_0.0.37-1.dsc shishi_0.0.37.orig.tar.gz shishi_0.0.37-1.diff.gz shishi-common_0.0.37-1_all.deb shishi-doc_0.0.37-1_all.deb libshishi0_0.0.37-1_i386.deb libshisa0_0.0.37-1_i386.deb shishi_0.0.37-1_i386.deb shishi-dbg_0.0.37-1_i386.deb libshishi-dev_0.0.37-1_i386.deb shisa_0.0.37-1_i386.deb libshisa-dev_0.0.37-1_i386.deb shishi-kdc_0.0.37-1_i386.deb libpam-shishi_0.0.37-1_i386.deb Greetings, Your Debian queue daemon Archive Administrator 2008-06-25T07:49:08 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/503 Shishi 0.0.37 has been released, and I'd like to see it in lenny. I know the timing is tight because libraries should be freezed by the end of June, but the changes since the last version are small (mostly generated code from gnulib and updated translations) and the debian package changes are minimal. Thoughts? I'll upload tomorrow if I don't hear anything else. /Simon Simon Josefsson 2008-06-24T11:52:37 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/502 _______________________________________________ Help-shishi mailing list Help-shishi< at >gnu.org http://lists.gnu.org/mailman/listinfo/help-shishi Simon Josefsson 2008-06-24T11:35:29 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/501 Hello Graham, sorry for the slow response. Graham Shaw <gdshaw< at >riscpkg.org> writes: Thanks for discussion. Implementing both was rather straight forward, so I did it. Could you please test an updated daily snapshot? http://daily.josefsson.org/shishi/shishi-20080619.tar.gz I'll release 0.0.37 within a day or so unless you find any problem. Thanks, Simon Simon Josefsson 2008-06-19T15:12:43 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/500 In article <87ej8v60gg.fsf< at >mocca.josefsson.org>, Simon Josefsson <simon< at >josefsson.org> wrote: Either would fully solve my current problem, so from a personal POV I don't have any preference. The first would be marginally easier to use, but I think the difference is small. You could narrow the gap by implementing the non-interactive version of the callback as part of the library, so that the user doesn't have to - that way it would be one line of code either way. (If you did that then I don't think there would be any advantage in having the flag too, because it would be so easy to achieve the same effect with the callback.) The second looks like the more general solution. I'm not sure it lets you do anything that you couldn't by calling the first one twice, but it probably has the edge in terms of elegance and efficiency. The second solution imposes a small cost on everyone by increasing the size of the hints structure. Probably negligible, because I can't imagine why you ever need more than on Graham Shaw 2008-04-25T03:26:11 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/499 Ok. I can think of two easy solutions: 1) Add a new Shishi_tkts_hintflags flag such as SHISHI_TKTSHINTFLAGS_NON_INTERACTIVE which inhibits all password queries. We probably need a new error code to signal that the command failed for this reason. 2) Add a callback interface for dealing with password queries. This allows you to get a callback when a password is needed. The callback could fail (which presumably it would in a non-interactive situation). We probably need to add the same error code here as well. Can you think of something else that would solve your problem better? Which do you prefer? I could implement both, they both seem useful. Thanks, /Simon Simon Josefsson 2008-04-24T09:55:59 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/498 Thanks, it should be distributed, and I've fixed this in git master. We probably never noticed this because it is only used if you modify the source code, something users rarely do with released packages. /Simon Simon Josefsson 2008-04-24T09:52:24 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/497 When I try to build Shishi from the distribution tarball it fails due to the absence of the file gdoc-error. This file is present in the git repository, but absent from the tarball (both the releases and the daily snapshots). Copying the file out of git and into the tarball appears to cure the problem. I can't see any mechanism for generating the file at build time, so presumably it ought to be distributed. Graham Shaw 2008-04-24T02:42:30 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/496 Correct. Thanks - that appears to work perfectly. That isn't quite the functionality I'm looking for: - if the client doesn't already have a service ticket then I do want it to request one from the KDC using the TGT, however - if the client doesn't have a TGT then I don't want it to prompt for a password. (The former is OK because it's an entirely non-interactive process, whereas the latter takes input from the user so is something I need to avoid.) Yours, Graham Shaw 2008-04-23T19:02:02 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/495 Hi. Thanks for your interest. Which API are you using? I'm assuming you are using the shishi_tkts_* interface to get tickets, which is the recommended high-level interface. Regarding 1), you can supply a password to be used by using a Shishi_tkts_hint structure and set the 'passwd' field in it. It will be used when getting a TGT when decrypting the AS-REP. Something like: Shishi_tkt *tkt; Shishi_tkts_hint hint; int rc; memset (&hint, 0, sizeof (hint)); hint.passwd = "mypasswd"; hint.client = (char *) "jas"; hint.server = (char *) "imap.domain.org"; tkt = shishi_tkts_get (shishi_tkts_default (h), &hint); if (!tkt) { printf ("cannot find ticket for \"%s\"\n", sname); return NULL; } I see now that if the server requires pre-authentication (using a password) I see now that the code will not use the provided password, but instead will prompt for a new password. I have fixed this, see: http://git.savannah.gnu.org/gitweb/?p=shishi.git;a=commitdiff;h=bdf277a51182c49 Simon Josefsson 2008-04-23T11:26:40 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/494 A question. I'm trying to find a way to prevent the Shishi library from prompting for a password. Specifically: 1. When obtaining an initial TGT I want to supply a password to be tried, and if that doesn't work I want it to give up. 2. When obtaining a service ticket I want it to give up if there is no suitable TGT available. I have a workaround but it involves modifying the library. (Either that or driving it through stdin/stdout, which apart from being fragile would be awkward to implement on the platform I'm developing for.) Is there an approved method for achieving the above? With thanks, Graham Shaw 2008-04-23T05:03:49 http://permalink.gmane.org/gmane.comp.gnu.shishi.general/493 Processing commands for control< at >bugs.debian.org: Bug#423944: /usr/bin/inetutils-telnet: Complains about ~/.shishi/tickets and creates ~/.shishi, for all connections Bug reassigned from package `libshishi0' to `inetutils-telnet'. Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) Debian Bug Tracking System 2008-04-07T11:30:08 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnu.shishi.general