Ubuntu-fr

titi38

Re : synaptic derrière un proxy

Acquire::http::Proxy "http://user:password@proxy:8080";

il faut mettre alors un nom utilisateur et password correct.

---

Il n'y a pas de problème. Le plus dur étant de trouver une solution.

gianfrancolr

Re : synaptic derrière un proxy

Salut tltl38, avec mon colegue on fais une conection directe pour eviter de passer pour le proxy, la mise à jour c'est bien passé...
Je pense pas qu'on etais loing de la solution, merci pour tout

LoneStar

Re : synaptic derrière un proxy

chez moi, ça fonctionne sans problème...
tu as des caractères spéciaux dans ton utilisateur ou ton mot de passe ?

Est-ce que les majuscules sont considérées comme "caractères spéciaux"?  J'ai des majuscules dans mon mot de passe. 

Le proxy fonctionne bien pour Firefox, mais pas pour apt-get, wget et Synaptic (même après avoir modifié les fichiers correspondants).

Patou-epita

Re : synaptic derrière un proxy

Bonjour,

J'ai le meme probleme, mais mon mot de passe possede un "/"
J'ai essaye plusieurs facons de l'echappe : \/ // %2F \\/
J'ai plus d'idee !!!

merci pour la reponse

vieurou

Re : synaptic derrière un proxy

salut

peut etre que le serveur de ton boulot est un serveur ms isa, qui fait que pour passer ton system doit envoyer son idntifiant de session windows , tom mot de passe de session windows , le nom de la machine , du reseau , etc etc , ce qui fait que ni apt-get ni synaptic ni rien qui viens du terminal ne passe
mais il y a une solution , il faut utiliser ntlmaps, un proxy logiciel ecris sous python qui redirige ce que tu demande pour que tout passe
http://ntlmaps.sourceforge.net/

avec ubuntu et Kubuntu  6.10, tout  allez bien pour moi , mais vendredi dernier jai installer la 7.04 , et oh malheur , ben ça marche plus

j'expose mon probleme :

je suis a l'afpa de roubaix et ils ont un serveur isa (...quel idée..). Du coup j'arrive plus a faire d'apt-get .

j'ai pourtant installer ntlm, derniere version , j'ai bien ( à mon avis ) configuré le fichier serveur.cfg, mais pour autant ça ne fonctionne pas , pourtant dans le terminal , là ou j'ai lancé  "python main.py" j'ai :

    vieurou@vieurou-desktop:~/ntlmaps-0.9.9.0.1$ ./main.py
    NTLM authorization Proxy Server v0.9.9.0.1
    Copyright (C) 2001-2004 by Dmitry Rozmanov and others.
    Now listening at vieurou-desktop on port 8080
    Connected from 127.0.0.1:51018
    Connected from 127.0.0.1:51019
    Connected from 127.0.0.1:51020
    Connected from 127.0.0.1:51021
    Connected from 127.0.0.1:51022
    Connected from 127.0.0.1:51023
    Connected from 127.0.0.1:51024
    ....

ainsi de suite mais pas de donné qui arrive ( normalement , y a des petit points qui apparraissent pour signaller l'arriver de données)

je  joint un copier coller de mon fichier server.cfg :

   

#========================================================================
    [GENERAL]
   
    LISTEN_PORT:8080
   
    # If you want APS to authenticate you at WWW servers using NTLM then just leave this
    # value blank like PARENT_PROXY: and APS will connect to web servers directly.
    # You can specify more than one proxy by leaving a space between each one, and
    # APS will detect when one fails and automatically fail-over to the next. EG:
    #PARENT_PROXY:first_proxy second_proxy third_proxy
    # And NOTE that NTLM cannot pass through another proxy server.
    PARENT_PROXY:isa.afpa-roubaix.local
   
    PARENT_PROXY_PORT:8080
   
    # APS will poll the upstream proxy and attempt to fail-over to a new one if it doesn't
    # get a response within an appropriate time frame.  The amount of time that it will
    # wait for a response before attempting fail-over is specified, in seconds, below:
    PARENT_PROXY_TIMEOUT:30
   
    # Set to 1 if you want to grant this authorization service to clients from other computers.
    # NOTE: all the users from other hosts that will be using you copy of APS for authentication
    # will be using your credentials in NTLM auth at the remote host.
    ALLOW_EXTERNAL_CLIENTS:0
   
    # If you want to allow some other but not all computers to use your proxy for authorization,
    # just set ALLOW_EXTERNAL_CLIENTS:0 and put friendly IP addresses here.
    # Use space as a delimiter.
    # NOTE that special addesses don't work here (192.168.3.0 for example).
    FRIENDLY_IPS:0
   
    # Requested URLs are written to "url.log" file. May be useful.
    URL_LOG:0
   
    # When a network service listens for connections, there is a maximum number of connection
    # attempts to that service that the underlying OS will allow to backlog waiting for a response
    # before the OS will start dropping new connection attempts with 'Connection refused'.  The
    # standard method of determining the maximum number of backlogged connections is to use the
    # SOMAXCONN constant, which is supposed to represent the maximum number that an OS will support
    # (for example, 5 on Windows 2000 Pro, and 200 on Windows 2000 server).  However, because this
    # is a statically compiled value in a Python distribution, usually this instead represents the
    # the most conservative value (5 on all Windows platforms, and 128 on the GNU/Linux variant I
    # tried).  So if you are running (for example) a massively threaded/parallel download manager,
    # the default value of, say, 5, or whatever SOMAXCONN happens to be set to, may be too low and
    # cause some connections to fail.  The value below can be set to any integer (it seems that
    # Python just silently caps values above the hard limit for the underlying platform), or it can
    # be set to the special value of SOMAXCONN (i.e. MAX_CONNECTION_BACKLOG:SOMAXCONN), to use
    # whatever this value happens to be set to in your Python build.  Setting this higher than
    # necessary may cause APS to consume more memory than you needed to.
    MAX_CONNECTION_BACKLOG:5
   
    #========================================================================
    [CLIENT_HEADER]
   
    # This section describes what and how the server should change in the clients headers.
    # Made in order to prevent parent proxy from seeing that you are using wget instead of IE5.5
   
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */*
    #User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
   
    # for windows 2000 emulation wink
    User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT5)
   
    # You can uncomment these chages in client's header to mimic IE5+ better, but in this case
    # you may expirience problems with *.html if your client does not really handle compression.
    Accept-Encoding: gzip, deflate
   
    #========================================================================
    [NTLM_AUTH]
   
    # Optional value, if leaved blank then APS will use gethostname() to determine
    # host's name.
    # NOTE1: If you Linux host name differs from Windows host name then it may be that
    #        MS server wont recognize you host at all and wont grant you access
    #        to resources requested. Then you have to use this option and APS will use
    #        this name in NTLM negotiations.
    # NOTE2: There are several reports that you can successfully use "foreign" host name
    #        here. Say, if user may access a resource from 'host1' and may not from 'host2'
    #        then there is a chance that APS running on 'host2' with NT_HOSTNAME:host1 will
    #        be able to be granted access to the restricted resource. However use this on
    #        you own risk as such a trick may be considered as a hack or something.
    NT_HOSTNAME: C008-pc-5216491.afpa-roubaix.local
   
    # Windows Domain.
    # NOTE: it is not full qualified internet domain, but windows network domain.
    NT_DOMAIN: afpa-roubaix.local
   
    # What user's name to use during authorization. It may differ form real current username.
    # If you enable NTLM_TO_BASIC, below, you can either leave this blank or simply
    # hash it out.
    USER: mon username
   
    # Password. Just leave it blank here and server will request it at the start time,
    # or, if you enable NTLM_TO_BASIC, below, you can either leave this blank or simply
    # hash it out, and you *won't* be prompted for a password at start time.
    PASSWORD: mon password
   
    # These two options replace old FULL_NTLM option.
    # NTLM authentication consists virtually of two parts: LM and NT. Windows95/98 use
    # only LM part, WindowsNT/2000 can use NT and LM or just NT part.
    # Almost always using just LM part will be enough. I had several reports
    # about LM and NT requirement and no about just NT.
    # So try to setup 1, 1 only if you have enough reasons to do so and when you understand
    # what you are doing.
    # 0, 0 is an illegal combination
    # NOTE: if you change these options then you have to setup flag option accordingly.
    LM_PART:1
    NT_PART:0
   
    # Highly experimental option. See research.txt for details.
    # LM - 06820000
    # NT - 05820000
    # LM + NT - 07820000
    NTLM_FLAGS: 06820000
   
    # This option makes APS try to translate NTLM authentication to very usual "Basic"
    # scheme. Almost all http clients know it. With this option set to 1 user will be requested
    # by his browser to enter his credentials and these username and password will be used by
    # APS for NTLM authentication at MS Proxy server or Web server.
    # In such a case different users can use one runnig APS with their own credentials.
    # NOTE1: currently translation works so it allows only one try for entering
    #        username/password. If you make a mistake you will have to restart you browser.
    # NOTE2: With debug:1 basic username/password will be written in log file in clear
    #        text format. I could try hide it, but the basic scheme is so weak that anybody
    #        who had access to APS would be able to get it.
    NTLM_TO_BASIC:0
   
    #========================================================================
    [DEBUG]
   
    # Set this to 1 if you want to see debug info in many log files. One per connection.
    DEBUG:0
   
    # Set this to 1 to get even more debug info.
    BIN_DEBUG:0
   
    # Set this to 1 to see some strange activity on screen. Actually you won't want it.
    SCR_DEBUG:1
   
    # Not actually a debug option but gives you some details on authentication process
    # into *.auth logs. Also see research.txt.
    AUTH_DEBUG:0

j'ai aussi editer le fichier  /etc/apt/apt.conf pour y ajouter :

   

ACQUIRE {
    http::proxy "http://127.0.0.1:8080/"
    }

cela ne fonctionne pas non plus

Ce qui m'ettonne c'est qu'avec kubuntu 6.10, le tout fonctionné avec ntlmaps098, mais aujourd'hui , lorsque je lance le main.py j'ai :

   

 Traceback (most recent call last):
    File "./main.py", line 26, in <module>
    import server, logger
    File "lib/server.py", line 21, in <module>
    import proxy_client, www_client
    File "lib/proxy_client.py", line 22, in <module>
    import ntlm_auth, basic_auth
    File "lib/ntlm_auth.py", line 21, in <module>
    import ntlm_messages, utils, ntlm_procs
    File "lib/ntlm_messages.py", line 20, in <module>
    import ntlm_procs, utils
    File "lib/ntlm_procs.py", line 21, in <module>
    import des, md4, utils
    File "lib/des.py", line 20, in <module>
    import des_c, utils
    File "lib/des_c.py", line 22
    SyntaxError: Non-ASCII character '\xd7' in file lib/des_c.py on line 22, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

alors que ça fonctionner tres bien avec ubuntu 6.10, et tout est pareil car j'ai garder mon /home , je n'ai reinstaller que le  /
----> ce message d'erreur est resolu, j'ai ajouter dans les source en premiere ou deuxieme ligne

# -*- coding: utf-8 -*-

donc maintenant le 0.9.8 ou version plus recente me donne le meme message et probleme  que detailler tout en haut ....

j'ai lancé aussi dans le treminal

export http_proxy=http://127.0.0.1:8080

mais toujours pareil
j'ai ensuite testé avec

export http_proxy=http://mon_id:mon_pass@127.0.0.1:8080

mais inutile puisque pass et id son preciser dans ntlm, et puis ça marche pas non plus

une suggestion ????

si quelqu'un  peut m'aider , ça me ferait super plaisir parceque là je bloque

merci d'avance

Dernière modification par vieurou (Le 10/05/2007, à 13:24)

Pedro

Re : synaptic derrière un proxy

Salut a tous!

Bon alors j'ai le même problème que vous,

avant j'utilisé:

export http_proxy=http://login:pass@ipproxy:port

le tout sans ntlm

mais il semble que cela ne marche plus, je pense que le problème vient que le système n'envoie pas les informations d'authentification, puisque l'erreur est la même si je remplace par:

export http_proxy=http://proxy:port

Le tout est de savoir pourquoi??

Dernière modification par Pedro (Le 14/06/2007, à 11:38)

Pedro

Re : synaptic derrière un proxy

Mon problème est résolue!!

En fait la base de mot de passe squid ne prend pas en compte la casse, j'ai enlevé les majuscules du pass et ca remarche comme avant!! pas besoin de ntlmaps, juste de rajouter

http_proxy=http://login:pass_sans_majuscules@ipproxy:port