[Savannah-hackers-public] [task #16469] can't upload to download area by scp or sftp
URL: <https://savannah.nongnu.org/task/?16469> Summary: can't upload to download area by scp or sftp Group: Savannah Administration Submitter: jkraehemann Submitted: Wed 13 Dec 2023 01:44:20 PM CET Should Start On: Wed 13 Dec 2023 12:00:00 AM CET Should be Finished on: Wed 13 Dec 2023 12:00:00 AM CET Category: None Priority: 5 - Normal Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any ___ Follow-up Comments: --- Date: Wed 13 Dec 2023 01:44:20 PM CET By: Joël Krähemann Hi, This is what I get while connecting to savannah: $ scp -r 6.2.x jkraehem...@dl.sv.nongnu.org:/releases/gsequencer/ scp: Connection closed Or by sftp: $ sftp -o User=jkraehemann dl.sv.nongnu.org Connection closed. Connection closed regards, Joël ___ Reply to this item at: <https://savannah.nongnu.org/task/?16469> ___ Message sent via Savannah https://savannah.nongnu.org/
[Savannah-hackers-public] scp asks for password on savannah nongnu.org
Hi, `scp` asks for password while connecting, I think this shouldn't happen. regards, Joël
Re: [Savannah-hackers-public] Aim to be a real free software engineer
Hi, I think you have good intentions. What stops you from contributing? And what are your preferences? I am always looking for some help with GSequencer. https://savannah.nongnu.org/projects/gsequencer/ Things really need to be done for almost every project: * documentation * translation * functional integration tests Or just benefiting from providing feedback or reviews. And for sure spread the word! regards, Joël On Thu, Jan 28, 2021 at 3:18 PM Aisuko LI wrote: > > To Whom It May Concern: > > My name is Aisuko and the real name is BowenLi, I'm a open-source software > engineer. And I read a few blogs on GNU.org. And I believe that people > should know the operator system name should be `GNU/Linux`, and I have to > consider my motivation. Why do I want to be an open source projects > contributor? and are modern open source projects really for freedom? > > So, I want to be a geek, although the way is difficult and boring. But I'm > a really boring guy too.And I keep trying to find the lightweight operating > systems. > > About my experiences, I'm working on many open-source projects, including > my Gihtub address. https://github.com/Aisuko. I have little development > experience on rancherOS(python, golang) due to my job, and am familiar with > community management and project maintenance, remote collaboration is easy > to me. And the development experiences much more on python, golang, C#, > industry in Cloud-native like Docker,Kubernetes and Service-mesh. > > Finally, I'm going back to the college school this year, and I'd like to > write more articles to spread out GNU/Linux and freedom software. > > Sincerely > > *Aisuko*
Re: [Savannah-hackers-public] Group keyrings
Hi Ineiev, Then you need to educate about the new settings ... Would be nice to have grained permissions, might be for every single input field. By using CSS class names may be, then you could just visit the appropriate page, inspect the HTML and then apply the desired permission: * read * write These all supporting user, group and others. Just like POSIX access control lists: https://www.usenix.org/legacy/publications/library/proceedings/usenix03/tech/freenix03/full_papers/gruenbacher/gruenbacher_html/main.html regards, Joël On Thu, Jan 28, 2021 at 8:38 PM Ineiev wrote: > > Currently, Savannah serves all GPG keys registered in accounts > of group's members as the keyring of the respective group, > like [0]. > > This keyring doesn't work very well as a source of signing > keys of group's releases, because the group may have many more > members than persons who actually sign releases: any member can > carelessly register new keys without thinking about the impact > on the security of released files, and team's admins have to > but monitor the aggregated keyring---I don't believe anyone actually > does (also, people may have one key for getting encrypted personal > emails and another key for signing tarballs). > > In particular, the set of keys registered by members of 'emacs' > has quite a few very old keys, and one of them is dsa768; as far > as I understand, such keys aren't considered adequate these days. > if the bad ones crack such a key and replace files on a mirror > (I think it would be easier to setup a mirror and register it > on Savannah than to crack the key), they'll be able to get round > the signature verification for those who are unfortunate enough > to pick that mirror. > > Probably, it would be better if each group had a public area > where its admins (rather than every member) could post only keys > used for releases, like GnuPG does [1]. I've just pushed a patch > for it to the group-keyring branch [2]. > > What do people think? > > [0] https://savannah.gnu.org/project/memberlist-gpgkeys.php?group=emacs > [1] https://www.gnupg.org/signature_key.html > [2] > https://git.savannah.gnu.org/cgit/administration/savane.git/log/?h=group-keyring
Re: [Savannah-hackers-public] Joining your team
Hi again, If you are looking for some specific project containing some RPC, gsequencer would be such a project. If you are curious about look the functional integration tests: #1 is a XMLRPC server doing basic HTTP authentication http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/test/server/ags_functional_server_test.c #2 is an OSC application server providing remote control of GSequencer http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/test/audio/osc/ags_functional_osc_xmlrpc_server_test.c You could extend the functional integration tests and if you find a buffer-overflow or alike please tell me. GSequencer is an application writting in GNU C99 the GNU extensions to the ANSI C99 programming language. = Build the tests = ./configure --enable-run-functional-tests make -j8 make -j8 ags_functional_server_test ags_functional_osc_xmlrpc_server_test = Run the tests = ./ags_functional_server_test ./ags_functional_osc_xmlrpc_server_test The -j8 flag to make tells to run parallel build using 8 threads. regards, Joël On Fri, Mar 6, 2020 at 10:21 PM Joël Krähemann wrote: > > Hi Jamaal, > > Is it more about hacking or ethics? > > I would say learn to hack can't be a bad idea, then. > > Where would you love to start? On projects or savannah itself? > > Best regards, > Joël > > On Fri, Mar 6, 2020 at 3:28 PM jamaaldeen via Discussions among > Savannah Hackers, open subscription > wrote: > > > > Hello team > > Am a student > > I would want to be a member > > Am learning Cyber security (Ethic.Hacking) > > Thank you > > > > Sent from ProtonMail mobile
Re: [Savannah-hackers-public] Joining your team
Hi Jamaal, Is it more about hacking or ethics? I would say learn to hack can't be a bad idea, then. Where would you love to start? On projects or savannah itself? Best regards, Joël On Fri, Mar 6, 2020 at 3:28 PM jamaaldeen via Discussions among Savannah Hackers, open subscription wrote: > > Hello team > Am a student > I would want to be a member > Am learning Cyber security (Ethic.Hacking) > Thank you > > Sent from ProtonMail mobile
[Savannah-hackers-public] problems using news on savannah
Hi,
The original news submission is in the attachment.
My new was just truncated to:
AgsFunction shall give you a fronted to solve linear equation systems.
Like functions with one or more variables.
The involved objects are:
AgsSolverMatrix
AgsSolverVector
AgsSolverPolynom
I am still working on the very basics, like parsing expressions in
ags/lib/ags_math_util.[ch]
The function ags_math_util_split_polynom() has just been implemented
and is able to split your polynomial into following components:
coefficient
symbols
exponent
The coefficient can be either numeric or constants like ℯ,
AgsFunction shall give you a fronted to solve linear equation systems. Like
functions with one or more variables.
The involved objects are:
0 AgsSolverMatrix
0 AgsSolverVector
0 AgsSolverPolynom
I am still working on the very basics, like parsing expressions in
_ags/lib/ags_math_util.[ch]_
The function *ags_math_util_split_polynom()* has just been implemented and is
able to split your polynomial into following components:
* coefficient
* symbols
* exponent
The coefficient can be either numeric or constants like ℯ, 𝜋 and 𝑖.
The symbols usually take the form of a letter with optional numeric suffix like
x0, x1 ...
The exponent is just extracted from exponent operator ^ and following
parenthesis (), no arithmetic rewrite or anything else applied.
Input polynomial:
+verbatim+
-2 * a^(-2 * ℯ * 𝑖) * b^(0.25 * 𝜋)
-verbatim-
Output factors:
+verbatim+
factor = {"-2", "a", "b", NULL}
-verbatim-
Output factor exponents:
+verbatim+
factor_exponent = {"1", "-2 * ℯ * 𝑖", "0.25 * 𝜋", NULL}
-verbatim-
by Joël
Re: [Savannah-hackers-public] I'd like to import history of previous repository
Hi I'm sorry for doing that. By the way, I don't work on master I use branches. Since all the history is imported now it won't happen anymore. This rewrite includes the Subversion repository, later github repository and for sure the new savannah history. The tags were preserved this way at least for those of savannah. I didn't integrate the branches of github repository, yet. I think this can be done without conflict and history rewrite. github branch is 0.7.0 whereas on savannah it is 0.7.x. Do you think it would be good to checkout those branches and put it on savannah? https://github.com/gsequencer/gsequencer/branches/stale Cheers, Joël On Wed, Jan 11, 2017 at 8:52 AM, Bob Proulx wrote: > Hello Joël, > > Joël Krähemann wrote: >> I just recognized my efforts to push my rewritten history is not possible. > > As a daily use matter that is true. Because primarily our task as > Savannah helpers is as curators of Free Software. We want to make > sure that the software is not damaged by malicious users. Because it > is unfortunate but it has happened that at times people have tried to > remove source code that has already been given to the community. > Therefore in daily usage we must have security restrictions. > >> I have rewritten github.com/gsequencer/gsequencer.git history and did >> some cleanse. >> >> Then I did: >> >> git fetch -p ../gsequencer.old >> git replace --graft "f417a247f812239f27532a4e9674550e193c9e20" >> "b2fb5b9ddfcac5698d9881605727d21cd1342809" > > Could you say a few more words about what it is that you are trying to > do? I am sorry but I am not familiar with your project. The above > replacement graft command doesn't hold any obvious meaning to me. > > Normally your users will not be happy if you rewrite history. It will > invalidate any clone of the repository that has been made. Normally > the master branch should only ever be "fast-forwarded" and not > rewritten. If you could say why you want to rewrite history and what > you are attempting that would be very useful. > >> I tried to push but didn't work. Please enable temporary >> non-fast-forward commits. > > At the risk of me getting in trouble for going past my authority I am > going to assume that you are operating in good faith and open up the > repository for you. I have made a backup copy of the repository just > in case. In the meantime I have opened up non-fastforward uploads. > > Bob
[Savannah-hackers-public] I'd like to import history of previous repository
Hi all I just recognized my efforts to push my rewritten history is not possible. I have rewritten github.com/gsequencer/gsequencer.git history and did some cleanse. Then I did: git fetch -p ../gsequencer.old git replace --graft "f417a247f812239f27532a4e9674550e193c9e20" "b2fb5b9ddfcac5698d9881605727d21cd1342809" I tried to push but didn't work. Please enable temporary non-fast-forward commits. bests, Joël
Re: [Savannah-hackers-public] I'd like to import history of previous repository
Hi Seems to work with: git pull --allow-unrelate-histories cheers, Joël On Wed, Jan 11, 2017 at 3:07 AM, Joël Krähemann wrote: > Hi all > > I just recognized my efforts to push my rewritten history is not possible. > > I have rewritten github.com/gsequencer/gsequencer.git history and did > some cleanse. > > Then I did: > > git fetch -p ../gsequencer.old > git replace --graft "f417a247f812239f27532a4e9674550e193c9e20" > "b2fb5b9ddfcac5698d9881605727d21cd1342809" > > I tried to push but didn't work. Please enable temporary > non-fast-forward commits. > > bests, > Joël
