5 ms·
The viewpoint you were espousing was, if I understand correctly: I should replace all my existing services with Go/Rust equivalents, unless they handle packets
by dsr_ 11y ago
The viewpoint you were espousing was, if I understand correctly: I should replace all my existing services with Go/Rust equivalents, unless they handle packets directly.
My objection is that you are advocating this in the same narrow-focused way that people advocate node with npm, python with pip, ruby with gem: little or no cooperation with the whole system is available yet. This is perfectly fine from the point of view of a group which does one thing, but not from my point of view, running large numbers of diverse systems.
When libfoo gets updated, all N packages on the system which use it via dynamic linking gets the benefit as soon as the packages restart. This is highly desirable.
If Go-libfoo is updated, each of those N packages needs to be rebuilt, but I don't have a programmatic way of finding out.
If there are N teams developing those packages, some of them will be faster off the mark than others, and now I have a window of vulnerability that is larger than the one I had when I could update libfoo on day 1.
You have multiplied my workload. I won't do that without a really good reason.
- nickpsecurity 11y agoHe gave you a really good reason: knocking out most severe, low-level errors in high-usage, critical services. You'll put work in for the risky ones. Why not the low-risk alternatives...
- pjmlp 11y agoStatic linking is also a thing in C. Apparently gcc seems to be the only C compiler lacking this capability, thanks to glibc. Also, you can use dynamic linking in Go since version 1.5.
- baq 11y agoi don't know if it counts, but there's musl-gcc, right?
- bogomipz 11y agocurious, is there no glibc solution? Its just the libnss* that requires dynamic linking?
- steveklabnik 11y agohttps://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked...
- vbernat 11y agogcc has no problem with static linking. glibc can be statically linked (with gcc or clang) except the pluggable parts, which is NSS. How would you reconcile static linking and plugins?
- pjmlp 11y agoBy making use of plugin selection at compile time, like we used to do when dynamic linking wasn't available in mainstream OSes.
- vbernat 11y agoThe whole idea of NSS is to be pluggable to let the local administrator chooses what they need.
- pjmlp 11y agoBack in the day when UNIX only had static linking that type of plugability was achieved via configuration files and UNIX IPC. Dynamic linking just makes it easy to program for the same scenario.
- fpoling 11y agoAs a result of that good intention glibc must now be compiled into each and every program that wants to allow a customization complicating life for anybody who writes system software in anything but C/C++. I would rather preferred for NSS to never happen and instead Linux defined a set of services available over unix sockets for things like DNS resolution or user/group databases.
- tptacek 11y agoIf the Debian people don't want to include Go for some logistical or religious or religiously logistical reason, that's fine with me. I don't think people should run critical infrastructure from Debian releases --- when things go wrong, you want to be prepared to patch source on a moment's notice, rather than waiting for the upstream synchronization dance --- but hardly anyone seems to agree with me on that, either. But I notice you didn't respond to my SNMP point, which is disappointing, because I was hoping that at least some fake Internet points might accrue to my otherwise fruitless efforts at implementing SNMP from scratch three separate fucking times. Can I at least be rewarded for that by winning a dumb message board argument!? There's even a cool trick to implementing BER encoders I could have talked about! Instead, it looks like the thread is going to be about dynamic versus static linkinnzzzzzzzzzzzzzzzzzz.
- pests 11y agoWhat is the cool trick to implementing BER?
- tptacek 11y agoyou encode it back-to-front i don't even care anymore.
- signa11 11y ago> you encode it back-to-front sorry, but i still don't grok it. for example, if you take a person 'object' defined as : Person { name string (or equivalent asn.1 type-name, with type-identifier == 1) age int (or equivalent asn.1 type-name, with type-identifier == 2) } since b.e.r is basically a tlv (type-length-value) encoding, a person with name "james" with age '10' i.e. james_person = Person(name = 'james', age = 10) gets hex-encoded as : "james" : 01 05 6a 61 6d 65 73 "10" : 02 01 0A so the whole thing looks like this: "01 05 6a 61 6d 65 73 02 0A". ofcourse this would be prepended with appropriate type-number for 'Person' with corresponding length. if we assume that 'Person' gets a type-identifier == 3, then 'james_person' instance would be encoded as: "03 06 01 05 6a 61 6d 65 73 02 0A" where '06' == total length (6 bytes) of this instance of person object. may you please elucidate your trick with the above example ? thanks for your insights !
- solidsnack9000 11y agoActually, Rust would support updates for your SSL, ASN.1 and other libraries; because native bindings are widely accepted and used with Rust.
- saturn_vk 11y agoYou can always use gccgo, which supports dynamic linking of the go stdlib